Hi glen;
I can not understand the difference between engaging and switch on a module
, as far as module is concern we have two state on that
1. if the module is there in the repository it is available to engage ,
but none of its handler there in any flow
2. Available module can be engaged to any level , then its handlers will
fit into flows depending on configuration.
I agree with you that at any level it should be able to override higher
level module engagement.
If module has engaged globally , a service foo should be able to say that he
does not want that module to be there in that service.
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Glen Daniels" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, October 04, 2005 9:54 AM
Subject: Re: [axis2] turning off WS-A
IMHO, Axis2 should not by default generate WSA headers, though WSA should
be available.
* The addressing module should be engaged, but not "switched on". We
should have a boolean property settable via client side code/config which
enables this (at any level, op/service/engine). On the server side, we
should reply with addressing headers if we get them, but not if we don't.
* If we read an appropriately annotated WSDL (a la
<wsa:UsingAddressing/>), we should definitely generate stuff that does
send the headers (i.e. turns on the switch).
--Glen
