[
https://jira.jboss.org/browse/JBWS-3147?page=com.atlassian.jira.plugin.sy...
]
Alessio Soldano commented on JBWS-3147:
---------------------------------------
Hi Jason,
first of all please note I do not have access to the link on
visual.force.com. I assume
this is a SAAJ issue, in which case it might be good if you could isolate a smaller
testcase / step-to-reproduce, not involving a spring ws, etc.
In any case, the jbossws-native saaj implementation is known to have an issue related to
how xalan internally deals with nodes, see my last reply here
http://community.jboss.org/thread/101035?tstart=0 .
This said, is there a JBPAPP issue for this given you're on EAP?
Spring SaajSoapMessageFactory missing child nodes.
--------------------------------------------------
Key: JBWS-3147
URL:
https://jira.jboss.org/browse/JBWS-3147
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jbossws-2.0.1.SP2
Environment: Jboss EAP 5.0.1
Spring WS 1.5.9
JDK 1.6.0_18
Reporter: Jason Shepherd
Fix For: jbossws-2.0.1.SP2
Use of the default messageFactory
(org.springframework.ws.soap.saaj.SaajSoapMessageFactory) for spring web services, and an
AbstractDomPayloadEndpoint. Child nodes are not appended to a response.
Switching to a org.springframework.ws.soap.axiom.AxiomSoapMessageFactory means child
nodes are appended correclty.
Various reports are that this does not occur on other Application Servers, only JBoss.
While I have reproduced it using EAP 5.0.1, I have not tested this on other application
servers.
http://www.techinfopad.com/spring/101202435-webservice-response-contains-...
http://forum.springsource.org/showthread.php?t=30725
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira