You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Eran Chinthaka <ch...@opensource.lk> on 2006/07/31 14:47:11 UTC
Re: [AXIS2] soap header
David Illsley wrote:
> Fabien,
> If you want access to the SOAPHeader, you can get it through the
> MessageContext. You can get this by adding the following method to
> your skeleton (I think this works for all MessageReceivers):
>
No it doesn't happen for all the message receivers. I think the code gen
templates should be modified to implement the Service interface by the
skeleton and the generated message receiver to invoke the
setOperationContext method.
What do others think about this?
(If agreed I'd like to implement this as an exercise to get in to code
gen module :) )
-- Chinthaka
Re: [AXIS2] soap header
Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me Eran
-- dims
On 7/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> David Illsley wrote:
> > Fabien,
> > If you want access to the SOAPHeader, you can get it through the
> > MessageContext. You can get this by adding the following method to
> > your skeleton (I think this works for all MessageReceivers):
> >
>
> No it doesn't happen for all the message receivers. I think the code gen
> templates should be modified to implement the Service interface by the
> skeleton and the generated message receiver to invoke the
> setOperationContext method.
>
> What do others think about this?
>
> (If agreed I'd like to implement this as an exercise to get in to code
> gen module :) )
>
> -- Chinthaka
>
>
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [AXIS2] soap header
Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me Eran
-- dims
On 7/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> David Illsley wrote:
> > Fabien,
> > If you want access to the SOAPHeader, you can get it through the
> > MessageContext. You can get this by adding the following method to
> > your skeleton (I think this works for all MessageReceivers):
> >
>
> No it doesn't happen for all the message receivers. I think the code gen
> templates should be modified to implement the Service interface by the
> skeleton and the generated message receiver to invoke the
> setOperationContext method.
>
> What do others think about this?
>
> (If agreed I'd like to implement this as an exercise to get in to code
> gen module :) )
>
> -- Chinthaka
>
>
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] soap header
Posted by Paul Fremantle <pz...@gmail.com>.
I would rather it wasn't a switch. I think the code should check (*and
cache*) whether the skeleton implements the right method, and then
call if it does.
It seems to me it should always do it, and if you don't want that then
delete the method from the skeleton.
Paul
On 8/1/06, Ajith Ranabahu <aj...@gmail.com> wrote:
> Hi,
> Great ! I guess this could be a switch for the code generator and as a
> helpful hint the change can be fully implemented by modifying the
> MessageReceiverTemplate,SkeletonTemplate and the
> SkeletonIntefaceTemplate :)
>
> Ajith
>
> On 7/31/06, Paul Fremantle <pz...@gmail.com> wrote:
> > Chinthaka
> >
> > Sounds like a great idea.
> >
> > Paul
> >
> > On 7/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> > > David Illsley wrote:
> > > > Fabien,
> > > > If you want access to the SOAPHeader, you can get it through the
> > > > MessageContext. You can get this by adding the following method to
> > > > your skeleton (I think this works for all MessageReceivers):
> > > >
> > >
> > > No it doesn't happen for all the message receivers. I think the code gen
> > > templates should be modified to implement the Service interface by the
> > > skeleton and the generated message receiver to invoke the
> > > setOperationContext method.
> > >
> > > What do others think about this?
> > >
> > > (If agreed I'd like to implement this as an exercise to get in to code
> > > gen module :) )
> > >
> > > -- Chinthaka
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Paul Fremantle
> > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Ajith Ranabahu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] soap header
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
Great ! I guess this could be a switch for the code generator and as a
helpful hint the change can be fully implemented by modifying the
MessageReceiverTemplate,SkeletonTemplate and the
SkeletonIntefaceTemplate :)
Ajith
On 7/31/06, Paul Fremantle <pz...@gmail.com> wrote:
> Chinthaka
>
> Sounds like a great idea.
>
> Paul
>
> On 7/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> > David Illsley wrote:
> > > Fabien,
> > > If you want access to the SOAPHeader, you can get it through the
> > > MessageContext. You can get this by adding the following method to
> > > your skeleton (I think this works for all MessageReceivers):
> > >
> >
> > No it doesn't happen for all the message receivers. I think the code gen
> > templates should be modified to implement the Service interface by the
> > skeleton and the generated message receiver to invoke the
> > setOperationContext method.
> >
> > What do others think about this?
> >
> > (If agreed I'd like to implement this as an exercise to get in to code
> > gen module :) )
> >
> > -- Chinthaka
> >
> >
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] soap header
Posted by Paul Fremantle <pz...@gmail.com>.
Chinthaka
Sounds like a great idea.
Paul
On 7/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> David Illsley wrote:
> > Fabien,
> > If you want access to the SOAPHeader, you can get it through the
> > MessageContext. You can get this by adding the following method to
> > your skeleton (I think this works for all MessageReceivers):
> >
>
> No it doesn't happen for all the message receivers. I think the code gen
> templates should be modified to implement the Service interface by the
> skeleton and the generated message receiver to invoke the
> setOperationContext method.
>
> What do others think about this?
>
> (If agreed I'd like to implement this as an exercise to get in to code
> gen module :) )
>
> -- Chinthaka
>
>
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] soap header
Posted by Paul Fremantle <pz...@gmail.com>.
Chinthaka
Sounds like a great idea.
Paul
On 7/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> David Illsley wrote:
> > Fabien,
> > If you want access to the SOAPHeader, you can get it through the
> > MessageContext. You can get this by adding the following method to
> > your skeleton (I think this works for all MessageReceivers):
> >
>
> No it doesn't happen for all the message receivers. I think the code gen
> templates should be modified to implement the Service interface by the
> skeleton and the generated message receiver to invoke the
> setOperationContext method.
>
> What do others think about this?
>
> (If agreed I'd like to implement this as an exercise to get in to code
> gen module :) )
>
> -- Chinthaka
>
>
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org