Hi,
This is something that I have been attempting to understand myself. I
am developing a wrapped style service that publishes one operation, but
this operation looks at the wrapped element to determine what to do.
For example if the request is
Mark,
If the request contains:
s:Body xmlns:s=[soapNamespace]
submitDocument xmlns=[yourNamespace]
requestAsomeArg/requestA
/submitDocument
/s:Body
Then a WS-I compliant server will use the yourNamespace}submitDocument
element as the message signature and dispatch it accordingly.
If
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 12, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: axis 1 - message style service and custom wsdl file
Hi,
This is something that I have been attempting to understand myself. I
am developing a wrapped style service that publishes one
you
expected, after you cast it down, of course.
-jeff
-Original Message-
From: Mark Airey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 12, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: axis 1 - message style service and custom wsdl file
Hi,
This is something
PROTECTED]
Sent: Wednesday, September 12, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: axis 1 - message style service and custom wsdl file
Hi,
This is something that I have been attempting to understand myself. I
am developing a wrapped style service that publishes one
]
Sent: Wednesday, September 12, 2007 2:06 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: axis 1 - message style service and custom wsdl file
The SOAP spec doesn't specify how to deal with substitution groups;
therefore, different frameworks handle them in different ways. (i.e
PROTECTED]
Sent: Wednesday, September 12, 2007 2:06 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: axis 1 - message style service and custom wsdl file
The SOAP spec doesn't specify how to deal with substitution groups;
therefore, different frameworks handle them in different ways
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: axis 1 - message style service and custom wsdl file
The SOAP spec doesn't specify how to deal with substitution groups;
therefore, different frameworks handle them in different ways. (i.e.,
interoperability problems).
But I also
thanks Anne for your comments.
re. 2 - : is that a standard? I see, that axis generates a wsdl with a
wrapper tag for each operation in the service (in case of a message
style implementation). But is that a documented must do? I understand
the advantages, but still think this is a little
Oliver,
The WS-I Basic Profile specifies that each operation must have a
unique signature. (The SOAP and WSDL specifications don't address this
issue, therefore it's unspecified.) On a practical level, the SOAP
engine requires some means to determine how to dispatch the request,
therefore it
got it. thanks a lot!
:oliver
---
oliver charlet
software development
11-041 Olsztyn, Poland
[EMAIL PROTECTED]
---
Anne Thomas Manes schrieb:
Oliver,
The WS-I Basic Profile specifies that each operation must have a
unique signature. (The SOAP and
Some more guidance on this:
There are a couple of reasons why you might have to use a wrapper element:
1- If you want to send more than one root element in a single SOAP message
2- If you want your service to expose more than one operation
Hope this helps,
Anne
On 9/7/07, Anne Thomas Manes
Oliver,
Your WSDL message definition is not valid.
It should be:
message name=operationA
part name=content element=xsd:any/
/message
Alternatively, you might want to define a wrapper element for your
message content, in which case you would define the message thus:
message name=operationA
13 matches
Mail list logo
