You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by ri...@multi-support.com on 2008/02/19 09:18:23 UTC
MTOM endpoint backward compatibility with SwA
Hi,
Is it possible to create an endpoint operation that can respond either MTOM
or SwA depending on the request?
I read the Attachments/MTOM guide and first I understood it as MTOM was
already backward compatible with SwA.
But if I enable MTOM for my endpoint it always returns a xop:include (mtom)
no matter how i call the service.
And if I enable SwA instead of MTOM for the endpoint it still returns a
xop:include but with an empty attachment.
Afterwards I read the following article "http://wso2.org/library/1675" and
I could then see the implementation for
SwA was different from MTOM. You manually add your attachment to the
outgoing MessageContext where as MTOM
uses OMText on OMFactory.
Can I conclude that it isn't possible to create an MTOM endpoint operation
that is backward compatible with SwA?
Regards
Multi-Support A/S
Torben Riis
--------------------------------------------------------------------
Phone +45 96 600 600, Fax +45 96 600 601
E-mail: riis@multi-support.com
http://www.multi-support.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: MTOM endpoint backward compatibility with SwA
Posted by ri...@multi-support.com.
Hi Thilina
Thank you for answering.
I didn't know that there wasn't defined any standard for binding the
attachment to the xml content for SwA.
I thought the "href="cid:urn:uuid...." in SwA was a standard like
xop:include. :-)
Regards
Multi-Support A/S
Torben Riis
--------------------------------------------------------------------
Phone +45 96 600 600, Fax +45 96 600 601
E-mail: riis@multi-support.com
http://www.multi-support.com
"Thilina
Gunarathne"
<csethil@gmail.co To
m> axis-user@ws.apache.org
cc
19-02-2008 14:58
Subject
Re: MTOM endpoint backward
Please respond to compatibility with SwA
axis-user@ws.apac
he.org
> Okey, but if I generate a .net client without WSE3 (.net should by
standard
> understand SwA), it complains about it couldn't parse the <xop:include>
> tag.
Interoperability is not in the WSDL level... On the other hand, AFAIK
there isn't a standard universal accepted way to define SwA
attachments in the WSDL..
> By good reason since the wsdl doesn't define any xop:include elements.
> Actually I thought it was MTOM that knew xop:include tags shouldn't be
> parsed and handled special.
yes,.it is.. The special case I was talking about is the wire level..
SwA does not define a standard element like <xop:include> to bind the
attachments to the XML content of the message. People are free to
embed the content-id of Attachment in any way they like.. Hence it is
application specific. But MTOM introduced the standardized
<xop:include> element to bind the attachment content to the Xml
content in the appropriate location. That's y I called MTOM as a
special case of SwA..
If you need to receive MTOM messages in a SwA client together with a
WSDL, make sure to define th <xop:include> explicitly..
>
> Have I totally missed it? ;-)
>
> Do you know how other wsdl2java tools works if they only support SwA and
> not MTOM.
> Would they just ignore the returned xop:include and find the attachments
> anyway?
I thought we are talking about web service engines and message level
support.. AFAIK not many wsdl2java tools support SwA..
thanks,
Thilina
>
>
> Regards
> Multi-Support A/S
>
> Torben Riis
> --------------------------------------------------------------------
> Phone +45 96 600 600, Fax +45 96 600 601
> E-mail: riis@multi-support.com
> http://www.multi-support.com
>
>
>
> "Thilina
> Gunarathne"
> <csethil@gmail.co
To
> m> axis-user@ws.apache.org
>
cc
> 19-02-2008 13:34
>
Subject
> Re: MTOM endpoint backward
> Please respond to compatibility with SwA
> axis-user@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
> Hi,
> It's not in the way you create the message. It is how the message
> looks like in the wire.. MTOM can be considered as a special case of
> SwA.. Even though MTOM includes <xop:include> tags, it is possible to
> extract the attachment using SwA enabled web service processor.
>
> See here[1] too..
>
> thanks,
> Thilina
>
> [1]http://ws.apache.org/axis2/1_3/mtom-guide.html#33
>
> On Feb 19, 2008 3:18 AM, <ri...@multi-support.com> wrote:
> >
> > Hi,
> >
> > Is it possible to create an endpoint operation that can respond either
> MTOM
> > or SwA depending on the request?
> >
> > I read the Attachments/MTOM guide and first I understood it as MTOM was
> > already backward compatible with SwA.
> > But if I enable MTOM for my endpoint it always returns a xop:include
> (mtom)
> > no matter how i call the service.
> > And if I enable SwA instead of MTOM for the endpoint it still returns a
> > xop:include but with an empty attachment.
> >
> > Afterwards I read the following article "http://wso2.org/library/1675"
> and
> > I could then see the implementation for
> > SwA was different from MTOM. You manually add your attachment to the
> > outgoing MessageContext where as MTOM
> > uses OMText on OMFactory.
> >
> > Can I conclude that it isn't possible to create an MTOM endpoint
> operation
> > that is backward compatible with SwA?
> >
> > Regards
> > Multi-Support A/S
> >
> > Torben Riis
> > --------------------------------------------------------------------
> > Phone +45 96 600 600, Fax +45 96 600 601
> > E-mail: riis@multi-support.com
> > http://www.multi-support.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: MTOM endpoint backward compatibility with SwA
Posted by Thilina Gunarathne <cs...@gmail.com>.
> Okey, but if I generate a .net client without WSE3 (.net should by standard
> understand SwA), it complains about it couldn't parse the <xop:include>
> tag.
Interoperability is not in the WSDL level... On the other hand, AFAIK
there isn't a standard universal accepted way to define SwA
attachments in the WSDL..
> By good reason since the wsdl doesn't define any xop:include elements.
> Actually I thought it was MTOM that knew xop:include tags shouldn't be
> parsed and handled special.
yes,.it is.. The special case I was talking about is the wire level..
SwA does not define a standard element like <xop:include> to bind the
attachments to the XML content of the message. People are free to
embed the content-id of Attachment in any way they like.. Hence it is
application specific. But MTOM introduced the standardized
<xop:include> element to bind the attachment content to the Xml
content in the appropriate location. That's y I called MTOM as a
special case of SwA..
If you need to receive MTOM messages in a SwA client together with a
WSDL, make sure to define th <xop:include> explicitly..
>
> Have I totally missed it? ;-)
>
> Do you know how other wsdl2java tools works if they only support SwA and
> not MTOM.
> Would they just ignore the returned xop:include and find the attachments
> anyway?
I thought we are talking about web service engines and message level
support.. AFAIK not many wsdl2java tools support SwA..
thanks,
Thilina
>
>
> Regards
> Multi-Support A/S
>
> Torben Riis
> --------------------------------------------------------------------
> Phone +45 96 600 600, Fax +45 96 600 601
> E-mail: riis@multi-support.com
> http://www.multi-support.com
>
>
>
> "Thilina
> Gunarathne"
> <csethil@gmail.co To
> m> axis-user@ws.apache.org
> cc
> 19-02-2008 13:34
> Subject
> Re: MTOM endpoint backward
> Please respond to compatibility with SwA
> axis-user@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
> Hi,
> It's not in the way you create the message. It is how the message
> looks like in the wire.. MTOM can be considered as a special case of
> SwA.. Even though MTOM includes <xop:include> tags, it is possible to
> extract the attachment using SwA enabled web service processor.
>
> See here[1] too..
>
> thanks,
> Thilina
>
> [1]http://ws.apache.org/axis2/1_3/mtom-guide.html#33
>
> On Feb 19, 2008 3:18 AM, <ri...@multi-support.com> wrote:
> >
> > Hi,
> >
> > Is it possible to create an endpoint operation that can respond either
> MTOM
> > or SwA depending on the request?
> >
> > I read the Attachments/MTOM guide and first I understood it as MTOM was
> > already backward compatible with SwA.
> > But if I enable MTOM for my endpoint it always returns a xop:include
> (mtom)
> > no matter how i call the service.
> > And if I enable SwA instead of MTOM for the endpoint it still returns a
> > xop:include but with an empty attachment.
> >
> > Afterwards I read the following article "http://wso2.org/library/1675"
> and
> > I could then see the implementation for
> > SwA was different from MTOM. You manually add your attachment to the
> > outgoing MessageContext where as MTOM
> > uses OMText on OMFactory.
> >
> > Can I conclude that it isn't possible to create an MTOM endpoint
> operation
> > that is backward compatible with SwA?
> >
> > Regards
> > Multi-Support A/S
> >
> > Torben Riis
> > --------------------------------------------------------------------
> > Phone +45 96 600 600, Fax +45 96 600 601
> > E-mail: riis@multi-support.com
> > http://www.multi-support.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: MTOM endpoint backward compatibility with SwA
Posted by ri...@multi-support.com.
Hi,
Okey, but if I generate a .net client without WSE3 (.net should by standard
understand SwA), it complains about it couldn't parse the <xop:include>
tag.
By good reason since the wsdl doesn't define any xop:include elements.
Actually I thought it was MTOM that knew xop:include tags shouldn't be
parsed and handled special.
Have I totally missed it? ;-)
Do you know how other wsdl2java tools works if they only support SwA and
not MTOM.
Would they just ignore the returned xop:include and find the attachments
anyway?
Regards
Multi-Support A/S
Torben Riis
--------------------------------------------------------------------
Phone +45 96 600 600, Fax +45 96 600 601
E-mail: riis@multi-support.com
http://www.multi-support.com
"Thilina
Gunarathne"
<csethil@gmail.co To
m> axis-user@ws.apache.org
cc
19-02-2008 13:34
Subject
Re: MTOM endpoint backward
Please respond to compatibility with SwA
axis-user@ws.apac
he.org
Hi,
It's not in the way you create the message. It is how the message
looks like in the wire.. MTOM can be considered as a special case of
SwA.. Even though MTOM includes <xop:include> tags, it is possible to
extract the attachment using SwA enabled web service processor.
See here[1] too..
thanks,
Thilina
[1]http://ws.apache.org/axis2/1_3/mtom-guide.html#33
On Feb 19, 2008 3:18 AM, <ri...@multi-support.com> wrote:
>
> Hi,
>
> Is it possible to create an endpoint operation that can respond either
MTOM
> or SwA depending on the request?
>
> I read the Attachments/MTOM guide and first I understood it as MTOM was
> already backward compatible with SwA.
> But if I enable MTOM for my endpoint it always returns a xop:include
(mtom)
> no matter how i call the service.
> And if I enable SwA instead of MTOM for the endpoint it still returns a
> xop:include but with an empty attachment.
>
> Afterwards I read the following article "http://wso2.org/library/1675"
and
> I could then see the implementation for
> SwA was different from MTOM. You manually add your attachment to the
> outgoing MessageContext where as MTOM
> uses OMText on OMFactory.
>
> Can I conclude that it isn't possible to create an MTOM endpoint
operation
> that is backward compatible with SwA?
>
> Regards
> Multi-Support A/S
>
> Torben Riis
> --------------------------------------------------------------------
> Phone +45 96 600 600, Fax +45 96 600 601
> E-mail: riis@multi-support.com
> http://www.multi-support.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: MTOM endpoint backward compatibility with SwA
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
It's not in the way you create the message. It is how the message
looks like in the wire.. MTOM can be considered as a special case of
SwA.. Even though MTOM includes <xop:include> tags, it is possible to
extract the attachment using SwA enabled web service processor.
See here[1] too..
thanks,
Thilina
[1]http://ws.apache.org/axis2/1_3/mtom-guide.html#33
On Feb 19, 2008 3:18 AM, <ri...@multi-support.com> wrote:
>
> Hi,
>
> Is it possible to create an endpoint operation that can respond either MTOM
> or SwA depending on the request?
>
> I read the Attachments/MTOM guide and first I understood it as MTOM was
> already backward compatible with SwA.
> But if I enable MTOM for my endpoint it always returns a xop:include (mtom)
> no matter how i call the service.
> And if I enable SwA instead of MTOM for the endpoint it still returns a
> xop:include but with an empty attachment.
>
> Afterwards I read the following article "http://wso2.org/library/1675" and
> I could then see the implementation for
> SwA was different from MTOM. You manually add your attachment to the
> outgoing MessageContext where as MTOM
> uses OMText on OMFactory.
>
> Can I conclude that it isn't possible to create an MTOM endpoint operation
> that is backward compatible with SwA?
>
> Regards
> Multi-Support A/S
>
> Torben Riis
> --------------------------------------------------------------------
> Phone +45 96 600 600, Fax +45 96 600 601
> E-mail: riis@multi-support.com
> http://www.multi-support.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org