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 <
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 <[EMAIL PROTECTED]> wrote:
Chinthaka
Sound
Chinthaka
Sounds like a great idea.
Paul
On 7/31/06, Eran Chinthaka <[EMAIL PROTECTED]> 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 wo
+1 from me Eran
-- dims
On 7/31/06, Eran Chinthaka <[EMAIL PROTECTED]> 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 Messag
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 c
