al Message-
From: Dimuthu Leelarathne [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2003 2:14 AM
To: [EMAIL PROTECTED]
Subject: RE: How to define document/literal service with multiple operatio
ns
Hi Ranjith,
>call.setOperationName(new javax.xml.namespace.QName("urn:eprofile
Hi Ranjith,
>call.setOperationName(new javax.xml.namespace.QName("urn:eprofile",
>"updateProfile"));
I have experienced that the above line has no effect whatso ever on the
SOAP message (it should not have any effect on the SOAP body, in the
doc\lit services method name is not send on the SOAP me
Hi Anne, Dimuthu,
I would like to try this.
Do you know what method do I need to call at Axis Client to set this QName?.
My method name is updateProfile and in my server-config.wsdd, I have this
entry for my service
http://xml.apache.org/xml-soap"; >
http://xml.apache.org/xml-soap"/>
Thompson, Eugene wrote:
Is it that Axis provides a communication style (message) that isn't part of
the specs?
Yes, the Axis Message style is not part of JAX-RPC. However, there is a lot of
confusion about exactly what "message-style" means.
The WSDL spec defines "document-style" operations as
e Basic Profile.
Regards,
Mike
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Friday, November 14, 2003 8:42 AM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple
operatio ns
According to the WS-I Basic Profile, a Doc/
> One of the reasons standards exist is to avoid vendor lock-in.
> It is a good architecture goal to avoid vendor lock-in and
> write code to
> the specs/standard apis.
Absolutely. For the implementation, I would agree whole-heartedly. I guess
where I'm missing the point is where you say ...
t I dont think anyone recommends that.
>>
>>
>>Keith
>>
>>-----Original Message-
>>From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent:
>>Thursday, November 13, 2003 5:35 PM
>>To: [EMAIL PROTECTED]
>>Subject: Re: How to define docum
guess one way to avoid all of this is to have one document/literal web
service per operation but I dont think anyone recommends that.
Keith
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED] Sent:
Thursday, November 13, 2003 5:35 PM
To: [EMAIL PROTECTED]
Subject: Re: How
> Also, I'd like to keep my web services portable to different JAX-RPC
> implementations, so I try to avoid Axis-specific features
> (e.g., Message-style
> services.)
>
Just curious, but why? Are you constructing a service that you are planning
to sell or that will need to be installed in man
ichael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 5:35 PM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple
operatio ns
Hi, Ranjith. What you are suggesting is basically an rpc-literal
operation.
Several postings to this list have mentione
Hi, Ranjith.
If I am right, wrapper element around your actual document is not specific
to Axis. That is the way Weblogic also works, Weblogic determines which
method to invoke, based on this wrapper element (root element of your xml
payload).
You're right, but it would nice to have an alternati
: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 5:35 PM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple
operatio ns
Hi, Ranjith. What you are suggesting is basically an rpc-literal
operation.
Several postings to this list ha
ment name for successful invocation of web service methods.
Thanks,
Ranjith Pillai.
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 2:35 PM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple operatio
ns
Hi
cument/literal web
service per operation but I dont think anyone recommends that.
Keith
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 5:35 PM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple
Hi Mike,
If I am right, wrapper element around your actual document is not specific
to Axis. That is the way Weblogic also works, Weblogic determines which
method to invoke, based on this wrapper element (root element of your xml
payload).
Thanks,
Ranjith Pillai.
-Original Message-
ailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 2:35 PM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple operatio
ns
Hi, Ranjith. What you are suggesting is basically an rpc-literal operation.
Several postings to this list have mentioned that rpc-li
Hi, Ranjith. What you are suggesting is basically an rpc-literal operation.
Several postings to this list have mentioned that rpc-literal is not (yet)
supported by all Web service implementations (even though it is recommended in
the WS-I Basic Profile), so I'd prefer to avoid rpc-literal for in
Hi Michael,
I hope you are using Message style service here.
I don't how to add this to axis client. But u can edit your SOAP message
directly if you are using tcpmon. So in tcpmon add another element(your
operation name)directly under soap body. For some reason axis client is not
doing this(if yo
18 matches
Mail list logo
