I think one option to solve your problem could be to use soap as an attachemnt feature. There are samples in the jboss source download.
Unfortunately I am note the one who is responsible for the technical specifiaction. The transport should comply with a specified XSD and also various clients and servers (not only the ones I am implementing) should be able to communicate.
Also, the XML elements that are that large actually contains binary documents that the server is not required to understand. They should just be stored in an archive as base64 encoded strings.
I have tried to figure out how to solve this, but there does not seem to exist any implementation to handle streaming webservices with large XML elements. The one parser I have used which can handle this is Woodstox, but jboss does not support this, right? Maybe in the future?
Is the javax.xml.ws.Provider a solution for you? You might want to check the org.jboss.test.ws.jaxws.samples.provider test cases.
I am using the Provider and the server receives a Source. However, it is a DOMSource, which means the entire message is in memory. I would like to receive a StreamSource with an InputStream. Then I can parse it myself with the appropriate tools.
I have tried to disable all my Logical- and SOAPMessageHandlers to avoid parsing by jboss, but it does not seem to help. Is there somthing I can implement or configure to avoid parsing into DOM tree?