gt; > -jeff
> >
> >
> >
> > -Original Message-
> > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, September 12, 2007 2:06 PM
> > To: axis-user@ws.apache.org; [EMAIL PROTECTED]
> > Subject: Re: axis 1 - message style se
EMAIL 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 diff
]
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.
u get to play with the Java object 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@
bject 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
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 that I have been attempting to understand myself. I
am developing a wrapped style service that publishe
Mark,
If the request contains:
someArg
Then a WS-I compliant server will use the yourNamespace}submitDocument
element as the message signature and dispatch it accordingly.
If you have defined the contents of the element to be
a choice or a substitution group, then it will not quali
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
someArg my service
sees the requestA element
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
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 needs
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 overh
Oliver,
Your WSDL message definition is not valid.
It should be:
Alternatively, you might want to define a wrapper element for your
message content, in which case you would define the message thus:
and you would also have to define the operationA element in your
section:
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 <[EM
Hi y'all,
I am having trouble to get to work a setup that seems to be rare, but
which for me is rather practical:
1) I have a wsdl, that defines a schema for the input of a message, i.e.
I want the content of the soap body to of that schema. This wsdl is used
to communicate with the users of
14 matches
Mail list logo
