I guess I meant can I see it :-)
You have to create the XML payload to match the WSDL - that is what is
going to be the OMElement. The OMElement is a tree structure.
Somewhere in there is going to be the OMText containing the MTOM data.
If we could see the WSDL we might be able to figure it out.
Paul
On 6/8/07, Anil Chukkapalli <[EMAIL PROTECTED]> wrote:
Paul
I do have wsdl for this service, i used it before when i used the wsdl2java
tool to create a stub to test my service.
Thanks
Anil
On 6/8/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> Anil
>
> Do you have a WSDL for this service?
>
> Paul
>
> On 6/8/07, Anil Chukkapalli <[EMAIL PROTECTED]> wrote:
> > Paul
> >
> > I need the operation client cause i need to maintain session between a
.NET
> > client and Java service and vice versa (it was discussed in previous
threads
> > and we could find no other way except using an operation client). I was
not
> > able to accomplish this using either the generated stub or the service
> > client. The issue now that I have is that the since my .NET client sends
the
> > binary data as a byte array, .NET understands this and optimizes it to
MTOM,
> > i am not entirely sure that the java service can understand this xml and
> > decipher the input argument which is OMElement.
> >
> >
> >
> > Service
> > public class MTOMService {
> > public void uploadFileUsingMTOM(OMElement element) throws Exception {
> >
> >
> >
> > ... ...
> > }
> > }
> >
> >
> > .Client
> >
> >
> > OMElement result = sender.sendReceive(payload);
> >
> > The tutorial that you pointed out shows the above code, is payload of
type
> > OMElement.
> >
> >
> > Thank you
> > Anil
> >
> > On 6/8/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> > > Anil
> > >
> > > The OperationClient is designed for pretty complex needs. Its not
> > > recommended except for Axis2 gurus. Most users can support their needs
> > > using ServiceClient.
> > >
> > > >How does axis2 determine that the input arguments need to be
> > > transferred using MTOM? > is it by sendding the argument of type
> > > OMElement.
> > >
> > > No! OMElement is the Axis2 representation of any XML. When you send
> > > binary data in XML it is logically a text node in the XML tree.
> > >
> > > If you are using OMElement to create the XML body of the request you
> > > need to do this.
> > >
> > > // create a text node to hold the data
> > > javax.activation.DataHandler dataHandler = new
> > > javax.activation.DataHandler (new FileDataSource("SomeFile"));
> > >
> > > OMText textData = omFactory.createText(dataHandler, true);
> > > someElement.addChild(textData);
> > >
> > >
> >
serviceClient().getOptions().setProperty("enableMTOM","true");
> > >
> > > Paul
> > >
> > > On 6/8/07, Anil Chukkapalli <[EMAIL PROTECTED]> wrote:
> > > > Hi Paul
> > > >
> > > > I am using an operation client
> > > >
> > > > Thank you
> > > > Anil
> > > >
> > > > On 6/8/07, Paul Fremantle <[EMAIL PROTECTED] > wrote:
> > > > >
> > > > > Anil
> > > > >
> > > > > http://ws.apache.org/axis2/1_2/mtom-guide.html
> > > > >
> > > > > Can you explain whether you are using the ServiceClient or a
generated
> > > > > stub. That would help us explain.
> > > > >
> > > > > Paul
> > > > >
> > > > > On 6/8/07, Anil Chukkapalli <[EMAIL PROTECTED] > wrote:
> > > > > > Hi
> > > > > >
> > > > > > How can an MTOM client send data to an MTOM server, is there a
> > tutorial
> > > > > > that explains how to do this. I can send a data from an MTOM
server
> > to
> > > > an
> > > > > > MTOM client but i am not able to figure out how to do it the
other
> > way
> > > > > > around, do we need to send an OMElement as an argument and does
> > axis2
> > > > > > understands this to be an attachment? If you are unable to
answer
> > this
> > > > > > question can you please point me to a tutorial or another
question.
> > > > > >
> > > > > > Thank you
> > > > > > Anil
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Paul Fremantle
> > > > > Co-Founder and VP of Technical Sales, WSO2
> > > > > OASIS WS-RX TC Co-chair
> > > > >
> > > > > blog: http://pzf.fremantle.org
> > > > > [EMAIL PROTECTED]
> > > > >
> > > > > "Oxygenating the Web Service Platform", www.wso2.com
> > > > >
> > > > >
> > > >
> >
---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > > > [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Paul Fremantle
> > > Co-Founder and VP of Technical Sales, WSO2
> > > OASIS WS-RX TC Co-chair
> > >
> > > blog: http://pzf.fremantle.org
> > > [EMAIL PROTECTED]
> > >
> > > "Oxygenating the Web Service Platform", www.wso2.com
> > >
> > >
> >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
