Re: [axis2] move axiom to ws-commons

[Dennis Sosnoski <dm...@sosnoski.com>]

I agree with the wider usefulness of AXIOM - it's a very clean model for 
many different types of processing. +1 on the move.

  - Dennis

Paul Fremantle wrote:

> I think there is more benefit to this than just the WS-Policy.
>
> For example, AXIOM could be used by any of a number of projects that 
> need a lazily-built tree. In Synapse, we use AXIOM extensively just to 
> parse our config. And also, although Synapse has a heavy dependency on 
> Axis2, the core model of Synapse was built to only depend on AXIOM. So 
> I think this is worth doing now.
>
> It also seems to me that Axiom is pretty stable, which motivates it.
>
> But I agree, Dims, if that was the only reason, then it would be 
> simple to fix. But the circular dependency is just an outcome of AXIOM 
> getting wider usage as an XML model
>
> Paul
>
> On 1/30/06, *Davanum Srinivas* <davanum@gmail.com 
> <ma...@gmail.com>> wrote:
>
>     Sanjiva,
>
>     I have no problem doing it. I did not see a *strong* need from a code
>     dependency point of view. If we just want do it, because we want to do
>     it, then it's fine :)
>
>     I was just pointing out that "circular dependency" is not an issue
>     :) :)
>
>     -- dims
>
>     On 1/30/06, Sanjiva Weerawarana <sanjiva@opensource.lk
>     <ma...@opensource.lk>> wrote:
>     > On Mon, 2006-01-30 at 13:50 -0500, Davanum Srinivas wrote:
>     > > 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.
>     >
>     > But this is the wrong thing to do from the point of view of the
>     policy
>     > model project.
>     >
>     > What's the reason for deferring the surgery? Its a relatively minor
>     > surgery; easily outpatient care! ;-)
>     >
>     > Sanjiva.
>     >
>     >
>     >
>
>
>     --
>     Davanum Srinivas : http://wso2.com/blogs/
>
>
>
>
> -- 
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle 
> <http://bloglines.com/blog/paulfremantle>
> paul@wso2.com <ma...@wso2.com>
>
> "Oxygenating the Web Service Platform", www.wso2.com <http://www.wso2.com>

Re: [axis2] move axiom to ws-commons

[Eran Chinthaka <ch...@opensource.lk>]

Ok, the move is completed now.

AXIOM is now settled in its new home in WS-Commons.

How abt the issues filled against AXIOM ? I think we need to move them
to WS-Commons JIRA. (later ;))

-- Chinthaka

Dennis Sosnoski wrote:

> I agree with the wider usefulness of AXIOM - it's a very clean model
> for many different types of processing. +1 on the move.
>
>  - Dennis
>
> Paul Fremantle wrote:
>
>> I think there is more benefit to this than just the WS-Policy.
>>
>> For example, AXIOM could be used by any of a number of projects that
>> need a lazily-built tree. In Synapse, we use AXIOM extensively just
>> to parse our config. And also, although Synapse has a heavy
>> dependency on Axis2, the core model of Synapse was built to only
>> depend on AXIOM. So I think this is worth doing now.
>>
>> It also seems to me that Axiom is pretty stable, which motivates it.
>>
>> But I agree, Dims, if that was the only reason, then it would be
>> simple to fix. But the circular dependency is just an outcome of
>> AXIOM getting wider usage as an XML model
>>
>> Paul
>>
>> On 1/30/06, *Davanum Srinivas* <davanum@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>>     Sanjiva,
>>
>>     I have no problem doing it. I did not see a *strong* need from a
>> code
>>     dependency point of view. If we just want do it, because we want
>> to do
>>     it, then it's fine :)
>>
>>     I was just pointing out that "circular dependency" is not an issue
>>     :) :)
>>
>>     -- dims
>>
>>     On 1/30/06, Sanjiva Weerawarana <sanjiva@opensource.lk
>>     <ma...@opensource.lk>> wrote:
>>     > On Mon, 2006-01-30 at 13:50 -0500, Davanum Srinivas wrote:
>>     > > 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.
>>     >
>>     > But this is the wrong thing to do from the point of view of the
>>     policy
>>     > model project.
>>     >
>>     > What's the reason for deferring the surgery? Its a relatively
>> minor
>>     > surgery; easily outpatient care! ;-)
>>     >
>>     > Sanjiva.
>>     >
>>     >
>>     >
>>
>>
>>     --
>>     Davanum Srinivas : http://wso2.com/blogs/
>>
>>
>>
>>
>> -- 
>> Paul Fremantle
>> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>>
>> http://bloglines.com/blog/paulfremantle
>> <http://bloglines.com/blog/paulfremantle>
>> paul@wso2.com <ma...@wso2.com>
>>
>> "Oxygenating the Web Service Platform", www.wso2.com
>> <http://www.wso2.com>
>
>
>