You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Justin Schoeman <ju...@expertron.co.za> on 2007/01/09 15:17:26 UTC
SOAPAction required?
I am busy testing an application at the moment (against the 9 January
snapshot).
When I test with an AXIS2 generated client, all works fine, but when
testing with a .Net client, I get an 'The endpoint reference (EPR) for
the Operation not found is
http://192.168.1.10:8080/axis2/services/XMLVendService2.0 and the WSA
Action = ' error.
Reading the SOAP documentation on the SOAPAction/action parameter:
"The presence and content of the action parameter MAY be used by
servers such as firewalls to appropriately filter SOAP messages and it
may be used by servers to facilitate dispatching of SOAP messages to
internal message handlers etc. It SHOULD NOT be used as an insecure form
of access authorization.
Use of the action parameter is OPTIONAL. SOAP Receivers MAY use it as a
hint to optimize processing, but SHOULD NOT require its presence in
order to operate."
It seems as though it should be acceptable to send the request with
SOAPAction "", but it seems not to be allowed by AXIS2. Or am I doing
something wrong?
WSDL file is provided by a commercial organisation, and is claimed to be
correct:
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: SOAPAction required?
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
Continuing down this trail... one positive note for document-literal
bindings is that it appears header params can be ignored when routing
based on just the message.
4.7.6 Operation Signatures
Definition: operation signature
The profile defines the "operation signature" to be the fully qualified
name of the child element of SOAP body of the SOAP input message described
by an operation in a WSDL binding.
In the case of rpc-literal binding, the operation name is used as a
wrapper for the part accessors. In the document-literal case, since a
wrapper with the operation name is not present, the message signatures
must be correctly designed so that they meet this requirement.
An endpoint that supports multiple operations must unambiguously identify
the operation being invoked based on the input message that it receives.
This is only possible if all the operations specified in the wsdl:binding
associated with an endpoint have a unique operation signature.
R2710 The operations in a wsdl:binding in a DESCRIPTION MUST result in
operation signatures that are different from one another.
Nicholas Gallardo
WebSphere - WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016
Nicholas L Gallardo/Austin/IBM@IBMUS
01/11/2007 02:15 PM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: SOAPAction required?
I agree with Wolfgang's statement and would like to one thing.
In the WS-I Basic Profile 1.1, rule R1127 [1] states: "A RECEIVER MUST
NOT rely on the value of the SOAPAction HTTP header to correctly process
the message. "
So, even in the case of a document/literal (wrapped or not) message, we
must be able to route without the SOAP Action. I believe this works in
Axis and should work in Axis2 as well.
[1] -
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#SOAPAction_HTTP_Header
Nicholas Gallardo
WebSphere - WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016
WJ Krpelan <kr...@yahoo.com>
01/10/2007 06:51 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: SOAPAction required?
dear all,
pls don't create a new bug.
SOAPACTION is REQUIRED for HTTP-Transport (empty or
otherwise) and it is PROHIBITED for every other
transport other than HTTP.
Noone is required to USE it, but there is some
standard-usage within .NET.
Cheers,
Wolfgang Krpelan
--- Amila Suriarachchi <am...@gmail.com>
wrote:
> On 1/10/07, Justin Schoeman <ju...@expertron.co.za>
> wrote:
> >
> > OK - Appending the operation name to the URL does
> work, but I am not
> > sure if .Net does this (I do not have .Net, just
> some recorded
> > messages). From what I can read on the web,
> routing is supposed to
> > occur via the first tag in the SOAP body (in this
> case a
> > confirmCustomerReq message).
>
>
> Yes. This is the case if you have rpc/literal as
> your soap binding style.
> In rpc style it is supposed to wrap the input
> message from an element of
> which name equals to operation name. (see the WSDL
> spec). hence it is
> possible to determine the operation using the
> message.
> but in document/literal style (in this case) input
> message is directly send
> in the soapbody. And also it is possible to have the
> same input message for
> two different operations. Therefore it is not
> possible to determine the
> operation from the first element.
>
>
> I realise this is a bit more complex, but it seems
> to be how it is
> > supposed to be done, although the documentation is
> extremely vague on
> > this point...
> >
> >
> > >
> > > --
> > > Amila Suriarachchi,
> > > WSO2 Inc.
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: SOAPAction required?
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
I agree with Wolfgang's statement and would like to one thing.
In the WS-I Basic Profile 1.1, rule R1127 [1] states: "A RECEIVER MUST
NOT rely on the value of the SOAPAction HTTP header to correctly process
the message. "
So, even in the case of a document/literal (wrapped or not) message, we
must be able to route without the SOAP Action. I believe this works in
Axis and should work in Axis2 as well.
[1] -
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#SOAPAction_HTTP_Header
Nicholas Gallardo
WebSphere - WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016
WJ Krpelan <kr...@yahoo.com>
01/10/2007 06:51 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: SOAPAction required?
dear all,
pls don't create a new bug.
SOAPACTION is REQUIRED for HTTP-Transport (empty or
otherwise) and it is PROHIBITED for every other
transport other than HTTP.
Noone is required to USE it, but there is some
standard-usage within .NET.
Cheers,
Wolfgang Krpelan
--- Amila Suriarachchi <am...@gmail.com>
wrote:
> On 1/10/07, Justin Schoeman <ju...@expertron.co.za>
> wrote:
> >
> > OK - Appending the operation name to the URL does
> work, but I am not
> > sure if .Net does this (I do not have .Net, just
> some recorded
> > messages). From what I can read on the web,
> routing is supposed to
> > occur via the first tag in the SOAP body (in this
> case a
> > confirmCustomerReq message).
>
>
> Yes. This is the case if you have rpc/literal as
> your soap binding style.
> In rpc style it is supposed to wrap the input
> message from an element of
> which name equals to operation name. (see the WSDL
> spec). hence it is
> possible to determine the operation using the
> message.
> but in document/literal style (in this case) input
> message is directly send
> in the soapbody. And also it is possible to have the
> same input message for
> two different operations. Therefore it is not
> possible to determine the
> operation from the first element.
>
>
> I realise this is a bit more complex, but it seems
> to be how it is
> > supposed to be done, although the documentation is
> extremely vague on
> > this point...
> >
> >
> > >
> > > --
> > > Amila Suriarachchi,
> > > WSO2 Inc.
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: SOAPAction required?
Posted by WJ Krpelan <kr...@yahoo.com>.
dear all,
pls don't create a new bug.
SOAPACTION is REQUIRED for HTTP-Transport (empty or
otherwise) and it is PROHIBITED for every other
transport other than HTTP.
Noone is required to USE it, but there is some
standard-usage within .NET.
Cheers,
Wolfgang Krpelan
--- Amila Suriarachchi <am...@gmail.com>
wrote:
> On 1/10/07, Justin Schoeman <ju...@expertron.co.za>
> wrote:
> >
> > OK - Appending the operation name to the URL does
> work, but I am not
> > sure if .Net does this (I do not have .Net, just
> some recorded
> > messages). From what I can read on the web,
> routing is supposed to
> > occur via the first tag in the SOAP body (in this
> case a
> > confirmCustomerReq message).
>
>
> Yes. This is the case if you have rpc/literal as
> your soap binding style.
> In rpc style it is supposed to wrap the input
> message from an element of
> which name equals to operation name. (see the WSDL
> spec). hence it is
> possible to determine the operation using the
> message.
> but in document/literal style (in this case) input
> message is directly send
> in the soapbody. And also it is possible to have the
> same input message for
> two different operations. Therefore it is not
> possible to determine the
> operation from the first element.
>
>
> I realise this is a bit more complex, but it seems
> to be how it is
> > supposed to be done, although the documentation is
> extremely vague on
> > this point...
> >
> >
> > >
> > > --
> > > Amila Suriarachchi,
> > > WSO2 Inc.
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: SOAPAction required?
Posted by Justin Schoeman <ju...@expertron.co.za>.
Amila Suriarachchi wrote:
>
>
> On 1/10/07, *Justin Schoeman* <justin@expertron.co.za
> <ma...@expertron.co.za>> wrote:
>
> OK - Appending the operation name to the URL does work, but I am not
> sure if .Net does this (I do not have .Net, just some recorded
> messages). From what I can read on the web, routing is supposed to
> occur via the first tag in the SOAP body (in this case a
> confirmCustomerReq message).
>
>
> Yes. This is the case if you have rpc/literal as your soap binding
> style. In rpc style it is supposed to wrap the input message from an
> element of which name equals to operation name. (see the WSDL spec).
> hence it is possible to determine the operation using the message.
> but in document/literal style (in this case) input message is directly
> send in the soapbody. And also it is possible to have the same input
> message for two different operations. Therefore it is not possible to
> determine the operation from the first element.
Thanks - I will be testing with real .Net clients next week - I hope
they follow the spec correctly!
-justin
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: SOAPAction required?
Posted by Amila Suriarachchi <am...@gmail.com>.
On 1/10/07, Justin Schoeman <ju...@expertron.co.za> wrote:
>
> OK - Appending the operation name to the URL does work, but I am not
> sure if .Net does this (I do not have .Net, just some recorded
> messages). From what I can read on the web, routing is supposed to
> occur via the first tag in the SOAP body (in this case a
> confirmCustomerReq message).
Yes. This is the case if you have rpc/literal as your soap binding style.
In rpc style it is supposed to wrap the input message from an element of
which name equals to operation name. (see the WSDL spec). hence it is
possible to determine the operation using the message.
but in document/literal style (in this case) input message is directly send
in the soapbody. And also it is possible to have the same input message for
two different operations. Therefore it is not possible to determine the
operation from the first element.
I realise this is a bit more complex, but it seems to be how it is
> supposed to be done, although the documentation is extremely vague on
> this point...
>
>
> >
> > --
> > Amila Suriarachchi,
> > WSO2 Inc.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: SOAPAction required?
Posted by Justin Schoeman <ju...@expertron.co.za>.
OK - Appending the operation name to the URL does work, but I am not
sure if .Net does this (I do not have .Net, just some recorded
messages). From what I can read on the web, routing is supposed to
occur via the first tag in the SOAP body (in this case a
confirmCustomerReq message).
I realise this is a bit more complex, but it seems to be how it is
supposed to be done, although the documentation is extremely vague on
this point...
-justin
Amila Suriarachchi wrote:
> It seems that the Axis2 Client generating an dummy soap action when the
> soapaction is empty.
>
> In following lines of code in CommonsHttpTransportSender.java
>
> if ((soapActionString == null) || (soapActionString.length () == 0)) {
> // now let's try to get WSA action
> soapActionString = messageContext.getWSAAction();
> if (messageContext.getAxisOperation() != null &&
> ((soapActionString == null) || ( soapActionString.length() == 0))) {
> // last option is to get it from the axis operation
> soapActionString =
> messageContext.getAxisOperation().getInputAction();
> }
> }
>
> sets a soap action.
> I think this is wrong and Please log a jira.
>
> Actually if the soapbindig style is document/literal and the soapaction
> is empty. then only possible way of dispatching is to use the URL
> dispatching.
> Use the EPR as follows
> http://localhost:8081/axis2/services/XMLVendService2.0/ConfirmCustomerRequest
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: SOAPAction required?
Posted by Amila Suriarachchi <am...@gmail.com>.
It seems that the Axis2 Client generating an dummy soap action when the
soapaction is empty.
In following lines of code in CommonsHttpTransportSender.java
if ((soapActionString == null) || (soapActionString.length() == 0)) {
// now let's try to get WSA action
soapActionString = messageContext.getWSAAction();
if (messageContext.getAxisOperation() != null &&
((soapActionString == null) || (soapActionString.length() == 0))) {
// last option is to get it from the axis operation
soapActionString = messageContext.getAxisOperation
().getInputAction();
}
}
sets a soap action.
I think this is wrong and Please log a jira.
Actually if the soapbindig style is document/literal and the soapaction is
empty. then only possible way of dispatching is to use the URL dispatching.
Use the EPR as follows
http://localhost:8081/axis2/services/XMLVendService2.0/ConfirmCustomerRequest
--
Amila Suriarachchi,
WSO2 Inc.
Re: SOAPAction required?
Posted by Justin Schoeman <ju...@expertron.co.za>.
From what I can understand, the empty string is deliberate. The
service is supposed to call the correct operation for the supplied
message. The SOAP documentation lists SOAPAction as required, but may be
"" if no additional message routing information is required.
wsdl file:
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl
xsd files:
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/Schema/xmlvend-base-2.0.xsd
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/Schema/xmlvend-revenue-2.0.xsd
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/Schema/xmlvend-meter-2.0.xsd
Example request message:
(attached in t.pl)
Thanks,
Justin
Amila Suriarachchi wrote:
> I think here the problem is that this wsdl
> (http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl
> <http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl>)
> has an empty string as soapaction (i.e. soapaction = "")
> and it is document type.
>
> Can you attached the two requests generated by the axis2 and .net client?
>
> I could not generate the client/server since I could not find the
> location for the .xsd files.
>
> Thanks
> Amila
>
> On 1/10/07, *Deepal Jayasinghe* <deepal@opensource.lk
> <ma...@opensource.lk>> wrote:
>
> Hi Justin ;
>
> Yes if you are using SOAP 1.2 , then the SOAP action is optional. Anyway
> please send us the wsdl file so that we can try to find the issue.
>
> Thanks
> Deepal
>
> > I am busy testing an application at the moment (against the 9
> January
> > snapshot).
> >
> > When I test with an AXIS2 generated client, all works fine, but when
> > testing with a .Net client, I get an 'The endpoint reference
> (EPR) for
> > the Operation not found is
> > http://192.168.1.10:8080/axis2/services/XMLVendService2.0 and the WSA
> > Action = ' error.
> >
> > Reading the SOAP documentation on the SOAPAction/action parameter:
> > "The presence and content of the action parameter MAY be used by
> > servers such as firewalls to appropriately filter SOAP messages
> and it
> > may be used by servers to facilitate dispatching of SOAP messages to
> > internal message handlers etc. It SHOULD NOT be used as an insecure
> > form of access authorization.
> >
> > Use of the action parameter is OPTIONAL. SOAP Receivers MAY use it as
> > a hint to optimize processing, but SHOULD NOT require its
> presence in
> > order to operate."
> >
> > It seems as though it should be acceptable to send the request with
> > SOAPAction "", but it seems not to be allowed by AXIS2. Or am I doing
> > something wrong?
> >
> > WSDL file is provided by a commercial organisation, and is claimed to
> > be correct:
> >
> http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl
> <http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl>
> >
> >
> > Thanks,
> > Justin
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> >
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
Re: SOAPAction required?
Posted by Amila Suriarachchi <am...@gmail.com>.
I think here the problem is that this wsdl (
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl)
has an empty string as soapaction (i.e. soapaction = "")
and it is document type.
Can you attached the two requests generated by the axis2 and .net client?
I could not generate the client/server since I could not find the location
for the .xsd files.
Thanks
Amila
On 1/10/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
> Hi Justin ;
>
> Yes if you are using SOAP 1.2 , then the SOAP action is optional. Anyway
> please send us the wsdl file so that we can try to find the issue.
>
> Thanks
> Deepal
>
> > I am busy testing an application at the moment (against the 9 January
> > snapshot).
> >
> > When I test with an AXIS2 generated client, all works fine, but when
> > testing with a .Net client, I get an 'The endpoint reference (EPR) for
> > the Operation not found is
> > http://192.168.1.10:8080/axis2/services/XMLVendService2.0 and the WSA
> > Action = ' error.
> >
> > Reading the SOAP documentation on the SOAPAction/action parameter:
> > "The presence and content of the action parameter MAY be used by
> > servers such as firewalls to appropriately filter SOAP messages and it
> > may be used by servers to facilitate dispatching of SOAP messages to
> > internal message handlers etc. It SHOULD NOT be used as an insecure
> > form of access authorization.
> >
> > Use of the action parameter is OPTIONAL. SOAP Receivers MAY use it as
> > a hint to optimize processing, but SHOULD NOT require its presence in
> > order to operate."
> >
> > It seems as though it should be acceptable to send the request with
> > SOAPAction "", but it seems not to be allowed by AXIS2. Or am I doing
> > something wrong?
> >
> > WSDL file is provided by a commercial organisation, and is claimed to
> > be correct:
> >
> http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl
> >
> >
> > Thanks,
> > Justin
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: SOAPAction required?
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Justin ;
Yes if you are using SOAP 1.2 , then the SOAP action is optional. Anyway
please send us the wsdl file so that we can try to find the issue.
Thanks
Deepal
> I am busy testing an application at the moment (against the 9 January
> snapshot).
>
> When I test with an AXIS2 generated client, all works fine, but when
> testing with a .Net client, I get an 'The endpoint reference (EPR) for
> the Operation not found is
> http://192.168.1.10:8080/axis2/services/XMLVendService2.0 and the WSA
> Action = ' error.
>
> Reading the SOAP documentation on the SOAPAction/action parameter:
> "The presence and content of the action parameter MAY be used by
> servers such as firewalls to appropriately filter SOAP messages and it
> may be used by servers to facilitate dispatching of SOAP messages to
> internal message handlers etc. It SHOULD NOT be used as an insecure
> form of access authorization.
>
> Use of the action parameter is OPTIONAL. SOAP Receivers MAY use it as
> a hint to optimize processing, but SHOULD NOT require its presence in
> order to operate."
>
> It seems as though it should be acceptable to send the request with
> SOAPAction "", but it seems not to be allowed by AXIS2. Or am I doing
> something wrong?
>
> WSDL file is provided by a commercial organisation, and is claimed to
> be correct:
> http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl
>
>
> Thanks,
> Justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org