axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <andreas.veit...@gmail.com>
Subject Re: Axiom not caching Datahandler after toString()
Date Tue, 16 Jun 2009 07:27:39 GMT
Where does the InputStreamDataSource class come from?

Andreas

On Tue, Jun 16, 2009 at 08:55, Srinath Perera<hemapani@gmail.com> wrote:
> Hi All;
>
> If we create a OM Element that do have a OMText which includes binary
> content represented as a "DataHandler", that binary content disappear
> after someone do a toString() on the OM Element. Following code
> recreate the problem. Could someone help me figuring out the problem?
>
> Thanks very much
> Srinath
>
> SOAPFactory factory = OMAbstractFactory.getSOAP11Factory();
> OMNamespace ns =
> factory.createOMNamespace(ExpandingMessageFormatter.BINARY_CONTENT_QNAME.getNamespaceURI(),
> "ns");
> OMElement omEle =
> factory.createOMElement(ExpandingMessageFormatter.BINARY_CONTENT_QNAME.getLocalPart(),
> ns);
>
> InputStreamDataSource ds = new InputStreamDataSource(in);
> DataHandler dataHandler = new DataHandler(ds);
>
> //create an OMText node with the above DataHandler and set optimized to true
> OMText textData = factory.createOMText(dataHandler, true);
> textData.setBinary(true);
> omEle.addChild(textData);
>
> System.out.println(omEle.toString());
> System.out.println(omEle);
>
> --
> ============================
> Srinath Perera:
>   WSO2 Inc. http://wso2.com
>   Blog: http://srinathsview.blogspot.com/
>

Mime
View raw message