Joel,
I've run into the exact same issue today...
Good news: I think that this has been fixed some while ago, but not
properly been documented in the bug database. The issue seems to be due
to a bug in the SAAJ 1.3 implementation JAR.
I managed to get rid of this exception by changing the SAAJ
implementation version that I use in my Maven project from 1.3 to
1.3-SNAPSHOT (dated Dec 19, 2006), available from:
https://maven-repository.dev.java.net/repository/com.sun.xml.messaging.saaj/jars/saaj-impl-1.3-SNAPSHOT.jar
instead of the released 1.3 version (dated Jun 12, 2006).
Best regards,
Andreas
--
Andreas Loew
Java Architect
Sun Microsystems (Germany)