Hopefully I'm just missing something simple on this:
Using the SOAPMessage.writeto method (thanks for the tip elsewhere on that one), I see that my response is missing the outermost element in the payload (i.e. my outermost application-functionality element, not any of the SOAP elements):
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><TxInfo xmlns="http://www.myapp.com"><StatCd>N</StatCd>...
This SHOULD have contained the outer wrapper element, like this:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><GetCitationLstRs xmlns="http://www.myapp.com"><TxInfo><StatCd>N</StatCd>...
I've used the airline sample as a pattern for a web service, and it (the airline sample) correctly returns the outer wrappering xml element.
I use JAXB and extend my endpoint class from AbstractMarshallingPayloadEndpoint, same as the airline sample. When I break inside AbstractMarshallingPayloadEndpoint, the requestObject and the responseObject both look reasonable, i.e. contain the outer wrapping element, so I'm thinking the problem is in the marshaller itself...or maybe there is some subtlety to the WSLD or xsd syntax.
I say "subtlety" coz my WSDL and .xsd validate in Eclipse and I've looked them over carefully. They look reasonable to me.
Tomcat log shows no errors.
Has anyone else encountered this problem? Thoughts on where I might look next?