Re: [AXIS 2] WS-addressing module
Thx Paul I didn't know that... - Original Message - From: Paul Fremantle To: axis-user@ws.apache.org Sent: Monday, July 31, 2006 11:14 AM Subject: Re: [AXIS 2] WS-addressing module FabienWS-Management uses the normal extension point for WS-Addressing, which is the reference parameters. This extension point is ALREADY built in. resource URI ... These can be set using the following Axis2 code:EndpointReference epr; epr.addReferenceParameter(OMElement el);Paul On 7/31/06, Fabien Couble <[EMAIL PROTECTED] > wrote: Hi everybody, I have to adapt the WS-addressing module in order to make it WS-Management compliant. That's why I'd like to have your point of view.In fact, the WS-Management specification adds two attributes to the WS-addressing header.It is the attributes wsman:ResourceURI and wsman:SelectorSet.I have analysed the WS-Addressing Module and I'd like to know if you agree with me.To add these two attributes I have to modify the class org.apache.axis2.client.Options (add the getter/setter).And then modify the two classes: org.apache.axis2.handlers.addressing.AddressingInHandler and org.apache.axis2.handlers.addressing.AddressingOutHandlerIn the first class, I should add a method to extract the two attributes and put them in an Option structure.In the second one, I should add the attributes from the Option structure to the SOAP message. For me, these are only these things to do...Am i right?? Any comment is welcome!Thx for your help!Fabien This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. -- Paul FremantleVP/Technology, WSO2 and OASIS WS-RX TC Co-chairhttp://bloglines.com/blog/paulfremantle [EMAIL PROTECTED]"Oxygenating the Web Service Platform", www.wso2.com This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: [AXIS 2] WS-addressing module
FabienWS-Management uses the normal extension point for WS-Addressing, which is the reference parameters. This extension point is ALREADY built in. resource URI ... These can be set using the following Axis2 code:EndpointReference epr; epr.addReferenceParameter(OMElement el);PaulOn 7/31/06, Fabien Couble <[EMAIL PROTECTED] > wrote: Hi everybody, I have to adapt the WS-addressing module in order to make it WS-Management compliant. That's why I'd like to have your point of view.In fact, the WS-Management specification adds two attributes to the WS-addressing header.It is the attributes wsman:ResourceURI and wsman:SelectorSet.I have analysed the WS-Addressing Module and I'd like to know if you agree with me.To add these two attributes I have to modify the class org.apache.axis2.client.Options (add the getter/setter).And then modify the two classes: org.apache.axis2.handlers.addressing.AddressingInHandler and org.apache.axis2.handlers.addressing.AddressingOutHandlerIn the first class, I should add a method to extract the two attributes and put them in an Option structure.In the second one, I should add the attributes from the Option structure to the SOAP message. For me, these are only these things to do...Am i right?? Any comment is welcome!Thx for your help!Fabien This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. -- Paul FremantleVP/Technology, WSO2 and OASIS WS-RX TC Co-chairhttp://bloglines.com/blog/paulfremantle [EMAIL PROTECTED]"Oxygenating the Web Service Platform", www.wso2.com
Re: [AXIS 2] WS-addressing module
Hi Fabien, I think you got the point, but let me add couple things to this. First, about where to put the code to extracting the two parameters from the message and putting them back to the SOAP message. 1. You can put the code in AddressingHandlers, but with a flag to indicate whether WS-Management is enabled or not. Your code will basically work when the flag is on. But I feel this is kind of not that elegant as this pollutes the WS-A code with some other code. Remember I didn't say I didn't like it :) 2. You can add two handlers one in IN path and the other in the OUT path so that they will do the necessary things once invoked. This approach will make sure you do not pollute the WS-A code. I prefer the second approach if that can be done :). -- Chinthaka Fabien Couble wrote: > > Hi everybody, > > I have to adapt the WS-addressing module in order to make it > WS-Management compliant. That's why I'd like to have your point of view. > In fact, the WS-Management specification adds two attributes to the > WS-addressing header. > It is the attributes wsman:ResourceURI and wsman:SelectorSet. > I have analysed the WS-Addressing Module and I'd like to know if you > agree with me. > To add these two attributes I have to modify the class > org.apache.axis2.client.Options (add the getter/setter). > And then modify the two classes: > org.apache.axis2.handlers.addressing.AddressingInHandler and > org.apache.axis2.handlers.addressing.AddressingOutHandler > In the first class, I should add a method to extract the two attributes > and put them in an Option structure. > In the second one, I should add the attributes from the Option structure > to the SOAP message. > > For me, these are only these things to do... > Am i right?? > Any comment is welcome! > Thx for your help! > Fabien > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, > you are not authorized to read, print, retain, copy, disseminate, > distribute, or use this message or any part thereof. If you receive this > message in error, please notify the sender immediately and delete all > copies of this message. > signature.asc Description: OpenPGP digital signature
[AXIS 2] WS-addressing module
Hi everybody, I have to adapt the WS-addressing module in order to make it WS-Management compliant. That's why I'd like to have your point of view.In fact, the WS-Management specification adds two attributes to the WS-addressing header.It is the attributes wsman:ResourceURI and wsman:SelectorSet.I have analysed the WS-Addressing Module and I'd like to know if you agree with me.To add these two attributes I have to modify the class org.apache.axis2.client.Options (add the getter/setter).And then modify the two classes: org.apache.axis2.handlers.addressing.AddressingInHandler and org.apache.axis2.handlers.addressing.AddressingOutHandlerIn the first class, I should add a method to extract the two attributes and put them in an Option structure.In the second one, I should add the attributes from the Option structure to the SOAP message. For me, these are only these things to do...Am i right?? Any comment is welcome!Thx for your help!Fabien This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
