Associating configuration with clients outside of code

[Paul Fremantle <pz...@gmail.com>]

For a service, we can associate config (e.g. engage modules, set
properties and add policies) by putting these into the services.xml. I
think it would be good to be able to do the same for client code.

Maybe this is already possible for policies by using policy attachment?

Anyway, what I'm thinking is that for situations where I have a
repository or axis2.xml I ought to be able to engage modules, set
properties and add policies without writing code.

One question is how to associate this with a particular client - I'm
guessing that the best way would be by service qname. Policy
attachment certainly comes to mind as the most flexible approach.

Maybe we could even add some local policies for setting properties or
engaging non-policy aware modules and do all three things using policy
attachment.

Paul

-- 
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