See, the problem is *IF* you need to secure the soap message, this
will fail since with this hack, you are just writing it to the
outputstream.
-- dims
On 8/16/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
Davanum Srinivas wrote:
> plz see the snippets in JaxmeDatabindingTemplate.xsl
Are you referring to the toOM method? But that's not exactly streaming,
isn't it? It simply converts the SAX drivers output into a (possibly
large) OM tree?
In the meantime, I've found a solution, which I personally do consider
better:
return new OMElementImpl(qName, null, pCommands.getOMFactory()){
protected void internalSerialize(XMLStreamWriter pWriter,
boolean pCache) throws XMLStreamException {
if (pCache) {
throw new IllegalStateException("Caching isn't implemented.");
}
// Fire the SAX drivers output into pWriter here
...
}
};
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
