snip... > > TUSCANY-2167 was caused by the base policy modules including WS binding > policy and dragging in some WS dependencies wasn't it? So thats fixed now > and isn't any issue with merging binding-ws-axis2-policy in the > binding-ws-axis2 module is it? > > ...ant > >
I made most of these changes and, at the time, the reason was two fold. - relate binding specific polices to those bindings. Hence binding-ws-axis2-policy which has axis2 specific code in but used to be something like policy-ws which wasn't particularly obvious. - allow policy jars to be deployed independently of the binding (or implementation) runtime jars which they affect. In this way a user who wants to change the default behaviour has a clear place to go to make the change rather than messing about inside the runtime jar. Simon
