On Wed, Apr 22, 2009 at 9:30 AM, Simon Laws <[email protected]>wrote:
> > these aren't pluggable modules as the -runtime module directly news up > > classes from the -policy module so i can't see any reasons for keeping > the > > code in a separate module now. > > > > ...ant > > > > They should be pluggable and if there are things there that are > explicitly created by the runtime then that's a mistake and needs > fixing. > > Simon > Removing binding-ws-axis2-policy from the build of binding-ws-axis build gives *lots* of compile errors as the runtime code directly uses classes in the policy module. We could change all those to be proper plugable extension points but it seems unnecessary to me as i can't image anyone ever wanting to plug in alternative implementations. Could we at least merge that code thats not pluggable right now into the one module and when/if a pluggable extension point is ever made then move it out? ...ant
