Re: [axis2] ServiceClient.disEngageModule question.

[Deepal Jayasinghe]

Hi David;

If you engage a module globally you have to dis-engage the module globally.

The solution to your problem is , rather than engaging addressing
globally engage and dis-engage addressing service level.

I have tested module dis-engagement and it works perfectly :)

David Illsley wrote:

>
> Hi,
> I have an axis2.xml setup to enable the addressing module globally
> which is being picked up in my client code.
> I want to disable the addressing module in the client for some calls
> and thought that calling
> MyStub._getServiceClient().disEngageModule(new QName("addressing"));
> would do this however it doesn't appear to have any effect.
>
> I couldn't find any documentation on this topic so am I wrong to
> expect to ServiceClient.disEngageModule() to disengage a globally
> engaged module? If so is there any way to disengage a globally engaged
> module for a single call or are globally engaged modules invulnerable
> to client code? (I'm aware of the property to disable addressing
> specifically but this is really a more general question).
>
> Thanks,
> David 


-- 
Thanks,
Deepal

~Future is Open~ 

Re: [axis2] ServiceClient.disEngageModule question.

[David Illsley]

Hi Eran, thanks for the reply.

It does however leave me a little confused about what 
ServiceClient.disEngageModule is supposed to do if not dynamically 
disengage a module? ;-)

Thanks,
David

Eran Chinthaka <[EMAIL PROTECTED]> wrote on 11/04/2006 17:34:12:

> Hi David,
> 
> Firstly, Axis2 doesn't support dynamic module dis-engagement, just like
> we do not support hot deployment of modules. This is not a bug and it is
> by design.
> 
> Secondly, once a module is engaged globally, it can not be dis-engaged
> per service/operation basis.
> 
> But for addressing, we have special case this, as you already know.
> 
> -- Eran Chinthaka
> 
> [attachment "signature.asc" deleted by David Illsley/UK/IBM] 

Re: [axis2] ServiceClient.disEngageModule question.

[Eran Chinthaka]

Hi David,

Firstly, Axis2 doesn't support dynamic module dis-engagement, just like
we do not support hot deployment of modules. This is not a bug and it is
by design.

Secondly, once a module is engaged globally, it can not be dis-engaged
per service/operation basis.

But for addressing, we have special case this, as you already know.

-- Eran Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [axis2] ServiceClient.disEngageModule question.

[David Illsley]

Apologies for the HTML mail, with any luck this one isn't!
David

[EMAIL PROTECTED] wrote on 10/04/2006 17:15:02:

> 
> Hi, 
> I have an axis2.xml setup to enable the addressing module globally 
> which is being picked up in my client code. 
> I want to disable the addressing module in the client for some calls
> and thought that calling MyStub._getServiceClient().
> disEngageModule(new QName("addressing")); would do this however it 
> doesn't appear to have any effect. 
> 
> I couldn't find any documentation on this topic so am I wrong to 
> expect to ServiceClient.disEngageModule() to disengage a globally 
> engaged module? If so is there any way to disengage a globally 
> engaged module for a single call or are globally engaged modules 
> invulnerable to client code? (I'm aware of the property to disable 
> addressing specifically but this is really a more general question). 
> 
> Thanks, 
> David

[axis2] ServiceClient.disEngageModule question.

[David Illsley]

Hi,
I have an axis2.xml setup to enable
the addressing module globally which is being picked up in my client code.
I want to disable the addressing module
in the client for some calls and thought that calling MyStub._getServiceClient().disEngageModule(new
QName("addressing")); would do this however it doesn't appear
to have any effect. 

I couldn't find any documentation on
this topic so am I wrong to expect to ServiceClient.disEngageModule() to
disengage a globally engaged module? If so is there any way to disengage
a globally engaged module for a single call or are globally engaged modules
invulnerable to client code? (I'm aware of the property to disable addressing
specifically but this is really a more general question).

Thanks,
David