I ran into this same problem -- it occurs when parsing a SOAP response and
there is an attribute with a URI. The JBoss code that causes the exception is
in the org.jboss.axis.message.SOAPElementAxisImpl at line 724. The 4.0.2 source
code I downloaded shows this (starting with line 712):
| if (uri != null && uri.trim().length() > 0)
| {
| // filterring out the tricky method to differentiate the
null namespace
| // -ware case
| if (uri.equals("intentionalNullURI"))
| {
| uri = null;
| }
|
| if (qname.startsWith("xmlns:") == false &&
qname.startsWith("xsi:") == false)
| qname = "xmlns:" + qname;
|
| Attr attr = doc.createAttributeNS(uri, qname);
| attr.setValue(value);
| domAttributes.setNamedItemNS(attr);
| }
|
What happens is that any attribute with a URI, say for example, "POS:lineTotal"
ends up being passed to the Document.createAttributeNS method as
"xmlns:POS:lineTotal". It seems to be a bug. If I can find some time to create
a test case, I'll submit it to JIRA.
By the way, commenting out lines 721 and 722 (where qname is set to "xmlns:" +
qname) seems to correct the problem for me, but I'm not sure what consequences
that would have in other cases.
Dan
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877512#3877512
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877512
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
