Hi all; Well , I dont think its a good idea to add new methods into module interface class after we have done 1.0 , any way I think changing Module interface wont affect that much. Since implementing Module interface is optional for a module so please go ahead and change , I know this is valid use case and this is the only way to do that.
Sanka Samaranayake wrote: > > Hi, > > I would like to suggest that we add the following two methods to the > Module interface. > > (1) public boolean validate(Policy policy) -- this methods will > validate a specified policy and it will remove any policy alternatives > which module can't support. This method is useful in the case we need > to choose a valid policy alternative for the entire system. Here the > objective is to remove any policy alternative that the module > *understand* and *can't support*. > > (2) public void applyPolicy(Policy policy, AxisDescription > axisDescription) throws AxisFault -- the module should treat the > specified policy as the policy for the specified AxisDescrition which > can be a AxisConfiguration or a AxisService or a .. etc. The module > should derive its configuration based on the specified policy and used > them when it deals with the > %specified AxisDescription. > > Thoughts? > > Sanka --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal ................................................................ ~Future is Open~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
