I've reviewed the code in question, there are exactly 2 files in policy project that uses axiom namely
- OMPolicyReader : OMPolicyReader is loaded on demand (using a class loader) from PolicyFactory.java. So moving it to axis2 core should not be a problem. - PolicyAttachmentUtil : PolicyAttachmentUtil is not even referenced from any other files in policy project. So there should not be a problem moving it to axis2 core. So, we don't have to do this right now. IMHO, We can defer this surgery for later. thanks, dims On 1/30/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > Folks, we currently have a circular dependency between policy and axis2 > projects: axis2 depends on policy and policy depends on axiom from > axis2. I think the right solution is to move axiom out of axis2 and to > ws-commons. I think this makes sense anyway (independent of the circular > dep) as axiom has potentially wider use. > > Thoughts or alternative proposals? > > Sanjiva. > > -- Davanum Srinivas : http://wso2.com/blogs/
