Re: Data in SOAP messages
Demetris
If you have a stub (called stub) and you call:
stub._getServiceClient().addStringHeader(new
QName("http://my/namespace";, "myTagname", "header text");
You will see something like (if you use TCPMON to trace the SOAP messages)
...
http://my/namespace";>header text
...
flowing. If you have more complex headers to send you can do:
stub._getServiceClient().addHeader(omElement);
In the server (assuming its also Axis2) you can implement a method:
public void init(MessageContext msgctx){
// store the message context
}
from msgctx you can access the Envelope and then the SOAPHeaders.
Paul
On 5/30/07, Demetris G <[EMAIL PROTECTED]> wrote:
Hi Paul,
I tend to agree with you so I want to avoid doing so. I am trying to
find
a way to pass information about specialized sockets to the client from the
server so that when the SOAP messages are generated they will have this
information. I am not sure what the best way would be now to do so but
I will need to work on it a bit more to figure that out. Any suggestions
would be more than welcome.
And thanks again for taking the time to help out Paul. Much
appreciated.
Thanks
Paul Fremantle wrote:
> Demetris
>
> I was trying to get across that you *don't* want to add headers into
> the WSDL. Its not a good model. The point is that the body is (mostly)
> strongly-typed and the headers are loosely typed in the sense that you
> may or may not have them. Axis2 doesn't support generating WSDL with
> headers in it. I'm not sure if WSDL2Java has been tested with WSDL
> with headers in either, because its not a common case.
>
> If you want to read more, look at this:
> http://www.ibm.com/developerworks/xml/library/ws-tip-headers.html
>
> Paul
>
> On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote:
>>
>> I did find some information on adding headers on the client side or in
>> the SOAP
>> message. How does one ask the Axis engine on the server side to add
>> headers
>> in the generated WSDL ?
>>
>> Paul Fremantle wrote:
>> > Sure Demetris - that is what headers are for. However, although you
>> > can include headers in the WSDL, most of the time people don't. The
>> > reason is that they like to keep a separation between application
>> > (functional) and non-application logic (non-functional, e.g. QoS,
>> > higher level tracking etc).
>> >
>> > You can add headers inside the client or using a module. You can even
>> > extend the policy languages to define your own headers using a policy.
>> >
>> > Paul
>> >
>> > On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Hey Glen,
>> >>
>> >> I hope this makes a bit of a sense:
>> >>
>> >> Can the server send some network specific information to the
>> client
>> >> by including that
>> >> information in the WSDL file in such a way so that when the client
>> stubs
>> >> generate the
>> >> SOAP calls back to the server, this information can be intercepted
>> and
>> >> utilized in a
>> >> certain manner. In other words, I want to take advantage of the
>> existing
>> >> traffic between
>> >> the client and the server to transport additional information across
>> >> them.
>> >>
>> >> Thanks
>> >>
>> >> Glen Mazza wrote:
>> >> > I am not sure what you asking--can you give us an example of
>> what you
>> >> > might be looking for?
>> >> >
>> >> > Glen
>> >> >
>> >> >
>> >> > Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G:
>> >> >
>> >> >> Hi all,
>> >> >>
>> >> >> does (and if it does where and how ) the SOAP specificaton
>> >> allow to
>> >> >> add proprietary or application specific data
>> >> >> to SOAP messages?
>> >> >>
>> >> >> Thanks
>> >> >>
>> >> >>
>> >> >>
>> -
>> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> -
>> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >> >
>> >> >
>> >> >
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTE
Re: Data in SOAP messages
Hi Paul, I tend to agree with you so I want to avoid doing so. I am trying to find a way to pass information about specialized sockets to the client from the server so that when the SOAP messages are generated they will have this information. I am not sure what the best way would be now to do so but I will need to work on it a bit more to figure that out. Any suggestions would be more than welcome. And thanks again for taking the time to help out Paul. Much appreciated. Thanks Paul Fremantle wrote: Demetris I was trying to get across that you *don't* want to add headers into the WSDL. Its not a good model. The point is that the body is (mostly) strongly-typed and the headers are loosely typed in the sense that you may or may not have them. Axis2 doesn't support generating WSDL with headers in it. I'm not sure if WSDL2Java has been tested with WSDL with headers in either, because its not a common case. If you want to read more, look at this: http://www.ibm.com/developerworks/xml/library/ws-tip-headers.html Paul On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote: I did find some information on adding headers on the client side or in the SOAP message. How does one ask the Axis engine on the server side to add headers in the generated WSDL ? Paul Fremantle wrote: > Sure Demetris - that is what headers are for. However, although you > can include headers in the WSDL, most of the time people don't. The > reason is that they like to keep a separation between application > (functional) and non-application logic (non-functional, e.g. QoS, > higher level tracking etc). > > You can add headers inside the client or using a module. You can even > extend the policy languages to define your own headers using a policy. > > Paul > > On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote: >> >> Hey Glen, >> >> I hope this makes a bit of a sense: >> >> Can the server send some network specific information to the client >> by including that >> information in the WSDL file in such a way so that when the client stubs >> generate the >> SOAP calls back to the server, this information can be intercepted and >> utilized in a >> certain manner. In other words, I want to take advantage of the existing >> traffic between >> the client and the server to transport additional information across >> them. >> >> Thanks >> >> Glen Mazza wrote: >> > I am not sure what you asking--can you give us an example of what you >> > might be looking for? >> > >> > Glen >> > >> > >> > Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G: >> > >> >> Hi all, >> >> >> >> does (and if it does where and how ) the SOAP specificaton >> allow to >> >> add proprietary or application specific data >> >> to SOAP messages? >> >> >> >> Thanks >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Data in SOAP messages
Demetris I was trying to get across that you *don't* want to add headers into the WSDL. Its not a good model. The point is that the body is (mostly) strongly-typed and the headers are loosely typed in the sense that you may or may not have them. Axis2 doesn't support generating WSDL with headers in it. I'm not sure if WSDL2Java has been tested with WSDL with headers in either, because its not a common case. If you want to read more, look at this: http://www.ibm.com/developerworks/xml/library/ws-tip-headers.html Paul On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote: I did find some information on adding headers on the client side or in the SOAP message. How does one ask the Axis engine on the server side to add headers in the generated WSDL ? Paul Fremantle wrote: > Sure Demetris - that is what headers are for. However, although you > can include headers in the WSDL, most of the time people don't. The > reason is that they like to keep a separation between application > (functional) and non-application logic (non-functional, e.g. QoS, > higher level tracking etc). > > You can add headers inside the client or using a module. You can even > extend the policy languages to define your own headers using a policy. > > Paul > > On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote: >> >> Hey Glen, >> >> I hope this makes a bit of a sense: >> >> Can the server send some network specific information to the client >> by including that >> information in the WSDL file in such a way so that when the client stubs >> generate the >> SOAP calls back to the server, this information can be intercepted and >> utilized in a >> certain manner. In other words, I want to take advantage of the existing >> traffic between >> the client and the server to transport additional information across >> them. >> >> Thanks >> >> Glen Mazza wrote: >> > I am not sure what you asking--can you give us an example of what you >> > might be looking for? >> > >> > Glen >> > >> > >> > Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G: >> > >> >> Hi all, >> >> >> >> does (and if it does where and how ) the SOAP specificaton >> allow to >> >> add proprietary or application specific data >> >> to SOAP messages? >> >> >> >> Thanks >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Data in SOAP messages
I did find some information on adding headers on the client side or in the SOAP message. How does one ask the Axis engine on the server side to add headers in the generated WSDL ? Paul Fremantle wrote: Sure Demetris - that is what headers are for. However, although you can include headers in the WSDL, most of the time people don't. The reason is that they like to keep a separation between application (functional) and non-application logic (non-functional, e.g. QoS, higher level tracking etc). You can add headers inside the client or using a module. You can even extend the policy languages to define your own headers using a policy. Paul On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote: Hey Glen, I hope this makes a bit of a sense: Can the server send some network specific information to the client by including that information in the WSDL file in such a way so that when the client stubs generate the SOAP calls back to the server, this information can be intercepted and utilized in a certain manner. In other words, I want to take advantage of the existing traffic between the client and the server to transport additional information across them. Thanks Glen Mazza wrote: > I am not sure what you asking--can you give us an example of what you > might be looking for? > > Glen > > > Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G: > >> Hi all, >> >> does (and if it does where and how ) the SOAP specificaton allow to >> add proprietary or application specific data >> to SOAP messages? >> >> Thanks >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Data in SOAP messages
Or at least point me to the right documentation for this and I will take it from there. Paul Fremantle wrote: Sure Demetris - that is what headers are for. However, although you can include headers in the WSDL, most of the time people don't. The reason is that they like to keep a separation between application (functional) and non-application logic (non-functional, e.g. QoS, higher level tracking etc). You can add headers inside the client or using a module. You can even extend the policy languages to define your own headers using a policy. Paul On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote: Hey Glen, I hope this makes a bit of a sense: Can the server send some network specific information to the client by including that information in the WSDL file in such a way so that when the client stubs generate the SOAP calls back to the server, this information can be intercepted and utilized in a certain manner. In other words, I want to take advantage of the existing traffic between the client and the server to transport additional information across them. Thanks Glen Mazza wrote: > I am not sure what you asking--can you give us an example of what you > might be looking for? > > Glen > > > Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G: > >> Hi all, >> >> does (and if it does where and how ) the SOAP specificaton allow to >> add proprietary or application specific data >> to SOAP messages? >> >> Thanks >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Data in SOAP messages
Hey Paul, that sounds good. Excuse my ignorance on some of the technology details ; would the headers in the WSDL be visible in the SOAP messages that the client stubs emit without me needing to add anything manually ? If yes then this solves my problem and it would make for a happy day :) Thanks again Paul Fremantle wrote: Sure Demetris - that is what headers are for. However, although you can include headers in the WSDL, most of the time people don't. The reason is that they like to keep a separation between application (functional) and non-application logic (non-functional, e.g. QoS, higher level tracking etc). You can add headers inside the client or using a module. You can even extend the policy languages to define your own headers using a policy. Paul On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote: Hey Glen, I hope this makes a bit of a sense: Can the server send some network specific information to the client by including that information in the WSDL file in such a way so that when the client stubs generate the SOAP calls back to the server, this information can be intercepted and utilized in a certain manner. In other words, I want to take advantage of the existing traffic between the client and the server to transport additional information across them. Thanks Glen Mazza wrote: > I am not sure what you asking--can you give us an example of what you > might be looking for? > > Glen > > > Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G: > >> Hi all, >> >> does (and if it does where and how ) the SOAP specificaton allow to >> add proprietary or application specific data >> to SOAP messages? >> >> Thanks >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Data in SOAP messages
Sure Demetris - that is what headers are for. However, although you can include headers in the WSDL, most of the time people don't. The reason is that they like to keep a separation between application (functional) and non-application logic (non-functional, e.g. QoS, higher level tracking etc). You can add headers inside the client or using a module. You can even extend the policy languages to define your own headers using a policy. Paul On 5/29/07, Demetris G <[EMAIL PROTECTED]> wrote: Hey Glen, I hope this makes a bit of a sense: Can the server send some network specific information to the client by including that information in the WSDL file in such a way so that when the client stubs generate the SOAP calls back to the server, this information can be intercepted and utilized in a certain manner. In other words, I want to take advantage of the existing traffic between the client and the server to transport additional information across them. Thanks Glen Mazza wrote: > I am not sure what you asking--can you give us an example of what you > might be looking for? > > Glen > > > Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G: > >> Hi all, >> >> does (and if it does where and how ) the SOAP specificaton allow to >> add proprietary or application specific data >> to SOAP messages? >> >> Thanks >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Data in SOAP messages
Hey Glen, I hope this makes a bit of a sense: Can the server send some network specific information to the client by including that information in the WSDL file in such a way so that when the client stubs generate the SOAP calls back to the server, this information can be intercepted and utilized in a certain manner. In other words, I want to take advantage of the existing traffic between the client and the server to transport additional information across them. Thanks Glen Mazza wrote: I am not sure what you asking--can you give us an example of what you might be looking for? Glen Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G: Hi all, does (and if it does where and how ) the SOAP specificaton allow to add proprietary or application specific data to SOAP messages? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Data in SOAP messages
I am not sure what you asking--can you give us an example of what you might be looking for? Glen Am Montag, den 28.05.2007, 23:07 -0400 schrieb Demetris G: > Hi all, > > does (and if it does where and how ) the SOAP specificaton allow to > add proprietary or application specific data > to SOAP messages? > > Thanks > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Data in SOAP messages
Hi all, does (and if it does where and how ) the SOAP specificaton allow to add proprietary or application specific data to SOAP messages? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
