You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Dimuthu Leelaratne <di...@gmail.com> on 2007/01/05 09:52:31 UTC
[AXIS2] MTOM Policy assertion
Hi All,
I am coding MTOM Policy assertion mentioned in
http://blogs.cocoondev.org/dims/archives/003534.html
I coded a builder and the relevant model for the policy assertion. The
problem is where to put the implementation? To which project should
this belong to?
We can put this in "Axis2" or "Neethi".
Thanks,
Dimuthu.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Ruchith Fernando <ru...@gmail.com>.
IMHO we don't need a new project for this ... Can this be a new maven
module within Neethi (I think its just a couple of classes)? And
neethi can have new modules for this sort of assertions in the future.
Now this way one will be able to get the neethi.jar along with jars
what ever other assertions they need out of the neethi project.
thoughts?
Thanks,
Ruchith
On 1/8/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> How about new ws-commons project ?
>
> Thanks
> Deepal
>
> David Illsley wrote:
>
> > IMO this 'feels' like something that could quite possibly be of wider
> > use than Axis2 - i.e. another web services engine which uses neethi
> > which is why I'm all for putting things in neethi (which is imo a more
> > resuable place) when reasonable. Of course, if there's axis2 specific
> > code in there then it can't. I'm happy for the assertion to live in
> > Axis2 for the moment but I'd prefer axis2 doesn't fill up with policy
> > code which has a broader scope.
> >
> > David
> >
> > On 08/01/07, Thilina Gunarathne <cs...@gmail.com> wrote:
> >
> >> I'm +1 for seperating out Savan and to keep the Axis2 core clean.
> >>
> >> But IMHO this is something which is quite different to Savan.. Also
> >> this might need to be coupled with Axis2 more than Savan.. IMO this is
> >> something which we can consider as part of Axis2 core..
> >>
> >> Also I do not think this has the potential to become a seperate project..
> >>
> >> Just my 2 cents..
> >>
> >> ~Thilina
> >>
> >> On 1/8/07, Eran Chinthaka <ch...@opensource.lk> wrote:
>
> > Dimuthu Leelaratne wrote:
> > > Hi,
> >
> > > Then we'll put it in Axis2 tree.
> >
> > +1 from me too, but only for the time being, for Dimuthu to go ahead
> > with development.
> >
> > Seems like it is the time to re-structure Axis2 as well. See we have
> > things like this and Savan, inside Axis2, which are optional. I think we
> > should leave Axis2 project, only with core components and create
> > separate projects to hold modules and extensions. It is just like Apache
> > Server and its module projects.
> >
> > -- Chinthaka
>
> >> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Thilina Gunarathne
> >> WSO2, Inc.; http://www.wso2.com/
> >> Home page: http://webservices.apache.org/~thilina/
> >> Blog: http://thilinag.blogspot.com/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >>
> >>
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Deepal Jayasinghe <de...@opensource.lk>.
How about new ws-commons project ?
Thanks
Deepal
David Illsley wrote:
> IMO this 'feels' like something that could quite possibly be of wider
> use than Axis2 - i.e. another web services engine which uses neethi
> which is why I'm all for putting things in neethi (which is imo a more
> resuable place) when reasonable. Of course, if there's axis2 specific
> code in there then it can't. I'm happy for the assertion to live in
> Axis2 for the moment but I'd prefer axis2 doesn't fill up with policy
> code which has a broader scope.
>
> David
>
> On 08/01/07, Thilina Gunarathne <cs...@gmail.com> wrote:
>
>> I'm +1 for seperating out Savan and to keep the Axis2 core clean.
>>
>> But IMHO this is something which is quite different to Savan.. Also
>> this might need to be coupled with Axis2 more than Savan.. IMO this is
>> something which we can consider as part of Axis2 core..
>>
>> Also I do not think this has the potential to become a seperate project..
>>
>> Just my 2 cents..
>>
>> ~Thilina
>>
>> On 1/8/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> Dimuthu Leelaratne wrote:
> > Hi,
>
> > Then we'll put it in Axis2 tree.
>
> +1 from me too, but only for the time being, for Dimuthu to go ahead
> with development.
>
> Seems like it is the time to re-structure Axis2 as well. See we have
> things like this and Savan, inside Axis2, which are optional. I think we
> should leave Axis2 project, only with core components and create
> separate projects to hold modules and extensions. It is just like Apache
> Server and its module projects.
>
> -- Chinthaka
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >
>> >
>>
>>
>> --
>> Thilina Gunarathne
>> WSO2, Inc.; http://www.wso2.com/
>> Home page: http://webservices.apache.org/~thilina/
>> Blog: http://thilinag.blogspot.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Dimuthu Leelaratne <di...@gmail.com>.
Hi Eran and All,
On 1/9/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dimuthu, if you can brief the way we are thinking of implementing this,
> it would be easier for us to understand where it should go.
>
> IIRC, Ruchith implemented the security policy by just populating policy
> information in to a set of beans. What will be your approach?
There is already the policy framework in place. So I just implemented
the interface "import org.apache.neethi.Assertion" and coded a
MTOMAssertion. Then coded the relevant builder by implementing the
interface "org.apache.neethi.builders.AssertionBuilder".
Usage of these two classes in Axis2 core
========================
Axis2 will MTOM serialize attachments if this Assertion is present in
the policy.
Usage of these two classes in Rampart
======================
Now what I am doing is by using these two classes MTOM serializing the
CipherValue in SOAP envelope. According to Ruchith this implementation
will interop with Microsoft.
I think we should NOT create a seperate project for a couple of classes.
Thanks,
Dimuthu
> David Illsley wrote:
> > IMO this 'feels' like something that could quite possibly be of wider
> > use than Axis2 - i.e. another web services engine which uses neethi
> > which is why I'm all for putting things in neethi (which is imo a more
> > resuable place) when reasonable. Of course, if there's axis2 specific
> > code in there then it can't. I'm happy for the assertion to live in
> > Axis2 for the moment but I'd prefer axis2 doesn't fill up with policy
> > code which has a broader scope.
> >
> > David
> >
> > On 08/01/07, Thilina Gunarathne <cs...@gmail.com> wrote:
> >> I'm +1 for seperating out Savan and to keep the Axis2 core clean.
> >>
> >> But IMHO this is something which is quite different to Savan.. Also
> >> this might need to be coupled with Axis2 more than Savan.. IMO this is
> >> something which we can consider as part of Axis2 core..
> >>
> >> Also I do not think this has the potential to become a seperate project..
> >>
> >> Just my 2 cents..
> >>
> >> ~Thilina
> >>
> >> On 1/8/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> > Dimuthu Leelaratne wrote:
> >> Hi,
> >
> >> Then we'll put it in Axis2 tree.
> >
> > +1 from me too, but only for the time being, for Dimuthu to go ahead
> > with development.
> >
> > Seems like it is the time to re-structure Axis2 as well. See we have
> > things like this and Savan, inside Axis2, which are optional. I
> >>> think we
> > should leave Axis2 project, only with core components and create
> > separate projects to hold modules and extensions. It is just like
> >>> Apache
> > Server and its module projects.
> >
> > -- Chinthaka
> >> >
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Thilina Gunarathne
> >> WSO2, Inc.; http://www.wso2.com/
> >> Home page: http://webservices.apache.org/~thilina/
> >> Blog: http://thilinag.blogspot.com/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >>
> >>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFovuLjON2uBzUhh8RAgeYAKCIvvhwxaUvpUoSu6F/C8+Zqeqn2ACfXYdk
> aFGHZjxNtXwygCZ06weogO0=
> =bOom
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dimuthu, if you can brief the way we are thinking of implementing this,
it would be easier for us to understand where it should go.
IIRC, Ruchith implemented the security policy by just populating policy
information in to a set of beans. What will be your approach?
== Chinthaka
David Illsley wrote:
> IMO this 'feels' like something that could quite possibly be of wider
> use than Axis2 - i.e. another web services engine which uses neethi
> which is why I'm all for putting things in neethi (which is imo a more
> resuable place) when reasonable. Of course, if there's axis2 specific
> code in there then it can't. I'm happy for the assertion to live in
> Axis2 for the moment but I'd prefer axis2 doesn't fill up with policy
> code which has a broader scope.
>
> David
>
> On 08/01/07, Thilina Gunarathne <cs...@gmail.com> wrote:
>> I'm +1 for seperating out Savan and to keep the Axis2 core clean.
>>
>> But IMHO this is something which is quite different to Savan.. Also
>> this might need to be coupled with Axis2 more than Savan.. IMO this is
>> something which we can consider as part of Axis2 core..
>>
>> Also I do not think this has the potential to become a seperate project..
>>
>> Just my 2 cents..
>>
>> ~Thilina
>>
>> On 1/8/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> Dimuthu Leelaratne wrote:
>> Hi,
>
>> Then we'll put it in Axis2 tree.
>
> +1 from me too, but only for the time being, for Dimuthu to go ahead
> with development.
>
> Seems like it is the time to re-structure Axis2 as well. See we have
> things like this and Savan, inside Axis2, which are optional. I
>>> think we
> should leave Axis2 project, only with core components and create
> separate projects to hold modules and extensions. It is just like
>>> Apache
> Server and its module projects.
>
> -- Chinthaka
>> >
- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >
>> >
>>
>>
>> --
>> Thilina Gunarathne
>> WSO2, Inc.; http://www.wso2.com/
>> Home page: http://webservices.apache.org/~thilina/
>> Blog: http://thilinag.blogspot.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFovuLjON2uBzUhh8RAgeYAKCIvvhwxaUvpUoSu6F/C8+Zqeqn2ACfXYdk
aFGHZjxNtXwygCZ06weogO0=
=bOom
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by David Illsley <da...@gmail.com>.
IMO this 'feels' like something that could quite possibly be of wider
use than Axis2 - i.e. another web services engine which uses neethi
which is why I'm all for putting things in neethi (which is imo a more
resuable place) when reasonable. Of course, if there's axis2 specific
code in there then it can't. I'm happy for the assertion to live in
Axis2 for the moment but I'd prefer axis2 doesn't fill up with policy
code which has a broader scope.
David
On 08/01/07, Thilina Gunarathne <cs...@gmail.com> wrote:
> I'm +1 for seperating out Savan and to keep the Axis2 core clean.
>
> But IMHO this is something which is quite different to Savan.. Also
> this might need to be coupled with Axis2 more than Savan.. IMO this is
> something which we can consider as part of Axis2 core..
>
> Also I do not think this has the potential to become a seperate project..
>
> Just my 2 cents..
>
> ~Thilina
>
> On 1/8/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Dimuthu Leelaratne wrote:
> > > Hi,
> > >
> > > Then we'll put it in Axis2 tree.
> >
> > +1 from me too, but only for the time being, for Dimuthu to go ahead
> > with development.
> >
> > Seems like it is the time to re-structure Axis2 as well. See we have
> > things like this and Savan, inside Axis2, which are optional. I think we
> > should leave Axis2 project, only with core components and create
> > separate projects to hold modules and extensions. It is just like Apache
> > Server and its module projects.
> >
> > - -- Chinthaka
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.3 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFFobayjON2uBzUhh8RAo3iAJsEUXWpWqA8BgAkNpmyZvlllv1R6ACcDu6f
> > uy6wq3FGgjepgQumap62Qrs=
> > =06L7
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Thilina Gunarathne
> WSO2, Inc.; http://www.wso2.com/
> Home page: http://webservices.apache.org/~thilina/
> Blog: http://thilinag.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Thilina Gunarathne <cs...@gmail.com>.
I'm +1 for seperating out Savan and to keep the Axis2 core clean.
But IMHO this is something which is quite different to Savan.. Also
this might need to be coupled with Axis2 more than Savan.. IMO this is
something which we can consider as part of Axis2 core..
Also I do not think this has the potential to become a seperate project..
Just my 2 cents..
~Thilina
On 1/8/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dimuthu Leelaratne wrote:
> > Hi,
> >
> > Then we'll put it in Axis2 tree.
>
> +1 from me too, but only for the time being, for Dimuthu to go ahead
> with development.
>
> Seems like it is the time to re-structure Axis2 as well. See we have
> things like this and Savan, inside Axis2, which are optional. I think we
> should leave Axis2 project, only with core components and create
> separate projects to hold modules and extensions. It is just like Apache
> Server and its module projects.
>
> - -- Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFobayjON2uBzUhh8RAo3iAJsEUXWpWqA8BgAkNpmyZvlllv1R6ACcDu6f
> uy6wq3FGgjepgQumap62Qrs=
> =06L7
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dimuthu Leelaratne wrote:
> Hi,
>
> Then we'll put it in Axis2 tree.
+1 from me too, but only for the time being, for Dimuthu to go ahead
with development.
Seems like it is the time to re-structure Axis2 as well. See we have
things like this and Savan, inside Axis2, which are optional. I think we
should leave Axis2 project, only with core components and create
separate projects to hold modules and extensions. It is just like Apache
Server and its module projects.
- -- Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFobayjON2uBzUhh8RAo3iAJsEUXWpWqA8BgAkNpmyZvlllv1R6ACcDu6f
uy6wq3FGgjepgQumap62Qrs=
=06L7
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Dimuthu Leelaratne <di...@gmail.com>.
Hi,
Then we'll put it in Axis2 tree.
Thanks everybody.
Dimuthu
On 1/7/07, Ajith Ranabahu <aj...@gmail.com> wrote:
> I also have to agree with Thilina. This is something like savan ,
> which we can initially put under the Axis2 tree and move out later if
> needed. It is better to leave neethi alone without cluttering it with
> other stuff such as specific policy assertions.
>
> Ajith
>
> On 1/7/07, Sanka Samaranayke <ss...@gmail.com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> > Hi,
> >
> > I agree with Thilina.
> >
> > Apache Neethi provides extension mechanism where
> > domain specific types can be used as assertions. The framework provides
> > processing model to combine and interpret them.
> >
> > IMHO MTOM policy assertions are yet another extension. Therefore
> > it doesn't belong in Neethi rather in Axis2.
> >
> > Best,
> > Sanka
> >
> >
> > Thilina Gunarathne wrote:
> > > AFAIK Neethi is the policy framework.. The concrete implementations
> > > like these stay in the relevant locations.. Ex: sec policy resides in
> > > Axis2 & will get moved with security..
> > >
> > > IMHO this needs to go in to Axis2.
> > >
> > >> It is also used for optimizing encrypted attachments. So should it go
> > >> to Neethi, because it is used both by Rampart and Axis2.
> > > Rampart anyway depends on Axis2.. So i don't see any issue in putting
> > > it to Axis2.
> > >
> > > Thanks,
> > > ~Thilina
> > >
> > > On 1/5/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> > >> It deosn't depend on Axis2.
> > >>
> > >> -Dimuthu
> > >>
> > >> On 1/5/07, David Illsley <da...@gmail.com> wrote:
> > >> > IMO If it doesn't depend on axis2 classes it should go into
> > >> neethi. If
> > >> > it does it should go in Axis2.
> > >> >
> > >> > David
> > >> >
> > >> > On 05/01/07, Dimuthu Leelaratne <di...@gmail.com>
> > >> wrote:
> > >> > > Hi Deepal,
> > >> > > We can argue both ways.
> > >> > >
> > >> > > This policy assertion will be mainly used by Axis2 to optimize
> > >> binary
> > >> > > data. So it should go to Axis2.
> > >> > >
> > >> > > It is also used for optimizing encrypted attachments. So should
> > >> it go
> > >> > > to Neethi, because it is used both by Rampart and Axis2.
> > >> > >
> > >> > > Thanks,
> > >> > > Dimuthu.
> > >> > >
> > >> > > On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > >> > > > Hi Dimuthu ;
> > >> > > >
> > >> > > > If it is Axis2 specific then , it should go to Axis2 .o.w to
> > >> Neethi
> > >> > > >
> > >> > > >
> > >> > > > Thanks
> > >> > > > Deepal
> > >> > > >
> > >> > > >
> > >> > > > > Hi All,
> > >> > > > >
> > >> > > > > I am coding MTOM Policy assertion mentioned in
> > >> > > > > http://blogs.cocoondev.org/dims/archives/003534.html
> > >> > > > >
> > >> > > > >
> > >> > > > > I coded a builder and the relevant model for the policy
> > >> assertion. The
> > >> > > > > problem is where to put the implementation? To which
> > >> project should
> > >> > > > > this belong to?
> > >> > > > >
> > >> > > > > We can put this in "Axis2" or "Neethi".
> > >> > > > >
> > >> > > > > Thanks,
> > >> > > > > Dimuthu.
> > >> > > > >
> > >> > > > >
> > >> ---------------------------------------------------------------------
> > >> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > >> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > > > --
> > >> > > > Thanks,
> > >> > > > Deepal
> > >> > > > ................................................................
> > >> > > > "The highest tower is built one brick at a time"
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> ---------------------------------------------------------------------
> > >> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > >> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> ---------------------------------------------------------------------
> > >> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > >> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >> > --
> > >> > David Illsley - IBM Web Services Development
> > >> >
> > >> >
> > >> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > >> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >> >
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >>
> > >>
> > >
> > >
> >
> >
> > - --
> > Sanka Samaranayake
> > WSO2 Inc.
> >
> > http://sankas.blogspot.com/
> > http://www.wso2.net/
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.2.1 (GNU/Linux)
> >
> > iD8DBQFFoR8N/Hd0ETKdgNIRAireAJ9VFH7Q+80GTvmXlsgtYrZVg/4p2wCfbasn
> > yQDtK3EMIfNJwPFoI4S4O5w=
> > =rhje
> > -----END PGP SIGNATURE-----
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Ajith Ranabahu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Ajith Ranabahu <aj...@gmail.com>.
I also have to agree with Thilina. This is something like savan ,
which we can initially put under the Axis2 tree and move out later if
needed. It is better to leave neethi alone without cluttering it with
other stuff such as specific policy assertions.
Ajith
On 1/7/07, Sanka Samaranayke <ss...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Hi,
>
> I agree with Thilina.
>
> Apache Neethi provides extension mechanism where
> domain specific types can be used as assertions. The framework provides
> processing model to combine and interpret them.
>
> IMHO MTOM policy assertions are yet another extension. Therefore
> it doesn't belong in Neethi rather in Axis2.
>
> Best,
> Sanka
>
>
> Thilina Gunarathne wrote:
> > AFAIK Neethi is the policy framework.. The concrete implementations
> > like these stay in the relevant locations.. Ex: sec policy resides in
> > Axis2 & will get moved with security..
> >
> > IMHO this needs to go in to Axis2.
> >
> >> It is also used for optimizing encrypted attachments. So should it go
> >> to Neethi, because it is used both by Rampart and Axis2.
> > Rampart anyway depends on Axis2.. So i don't see any issue in putting
> > it to Axis2.
> >
> > Thanks,
> > ~Thilina
> >
> > On 1/5/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> >> It deosn't depend on Axis2.
> >>
> >> -Dimuthu
> >>
> >> On 1/5/07, David Illsley <da...@gmail.com> wrote:
> >> > IMO If it doesn't depend on axis2 classes it should go into
> >> neethi. If
> >> > it does it should go in Axis2.
> >> >
> >> > David
> >> >
> >> > On 05/01/07, Dimuthu Leelaratne <di...@gmail.com>
> >> wrote:
> >> > > Hi Deepal,
> >> > > We can argue both ways.
> >> > >
> >> > > This policy assertion will be mainly used by Axis2 to optimize
> >> binary
> >> > > data. So it should go to Axis2.
> >> > >
> >> > > It is also used for optimizing encrypted attachments. So should
> >> it go
> >> > > to Neethi, because it is used both by Rampart and Axis2.
> >> > >
> >> > > Thanks,
> >> > > Dimuthu.
> >> > >
> >> > > On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> >> > > > Hi Dimuthu ;
> >> > > >
> >> > > > If it is Axis2 specific then , it should go to Axis2 .o.w to
> >> Neethi
> >> > > >
> >> > > >
> >> > > > Thanks
> >> > > > Deepal
> >> > > >
> >> > > >
> >> > > > > Hi All,
> >> > > > >
> >> > > > > I am coding MTOM Policy assertion mentioned in
> >> > > > > http://blogs.cocoondev.org/dims/archives/003534.html
> >> > > > >
> >> > > > >
> >> > > > > I coded a builder and the relevant model for the policy
> >> assertion. The
> >> > > > > problem is where to put the implementation? To which
> >> project should
> >> > > > > this belong to?
> >> > > > >
> >> > > > > We can put this in "Axis2" or "Neethi".
> >> > > > >
> >> > > > > Thanks,
> >> > > > > Dimuthu.
> >> > > > >
> >> > > > >
> >> ---------------------------------------------------------------------
> >> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > > --
> >> > > > Thanks,
> >> > > > Deepal
> >> > > > ................................................................
> >> > > > "The highest tower is built one brick at a time"
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >> > >
> >> > >
> >> >
> >> >
> >> > --
> >> > David Illsley - IBM Web Services Development
> >> >
> >> >
> >> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >>
> >>
> >
> >
>
>
> - --
> Sanka Samaranayake
> WSO2 Inc.
>
> http://sankas.blogspot.com/
> http://www.wso2.net/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.1 (GNU/Linux)
>
> iD8DBQFFoR8N/Hd0ETKdgNIRAireAJ9VFH7Q+80GTvmXlsgtYrZVg/4p2wCfbasn
> yQDtK3EMIfNJwPFoI4S4O5w=
> =rhje
> -----END PGP SIGNATURE-----
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Sanka Samaranayke <ss...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I agree with Thilina.
Apache Neethi provides extension mechanism where
domain specific types can be used as assertions. The framework provides
processing model to combine and interpret them.
IMHO MTOM policy assertions are yet another extension. Therefore
it doesn't belong in Neethi rather in Axis2.
Best,
Sanka
Thilina Gunarathne wrote:
> AFAIK Neethi is the policy framework.. The concrete implementations
> like these stay in the relevant locations.. Ex: sec policy resides in
> Axis2 & will get moved with security..
>
> IMHO this needs to go in to Axis2.
>
>> It is also used for optimizing encrypted attachments. So should it go
>> to Neethi, because it is used both by Rampart and Axis2.
> Rampart anyway depends on Axis2.. So i don't see any issue in putting
> it to Axis2.
>
> Thanks,
> ~Thilina
>
> On 1/5/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
>> It deosn't depend on Axis2.
>>
>> -Dimuthu
>>
>> On 1/5/07, David Illsley <da...@gmail.com> wrote:
>> > IMO If it doesn't depend on axis2 classes it should go into
>> neethi. If
>> > it does it should go in Axis2.
>> >
>> > David
>> >
>> > On 05/01/07, Dimuthu Leelaratne <di...@gmail.com>
>> wrote:
>> > > Hi Deepal,
>> > > We can argue both ways.
>> > >
>> > > This policy assertion will be mainly used by Axis2 to optimize
>> binary
>> > > data. So it should go to Axis2.
>> > >
>> > > It is also used for optimizing encrypted attachments. So should
>> it go
>> > > to Neethi, because it is used both by Rampart and Axis2.
>> > >
>> > > Thanks,
>> > > Dimuthu.
>> > >
>> > > On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
>> > > > Hi Dimuthu ;
>> > > >
>> > > > If it is Axis2 specific then , it should go to Axis2 .o.w to
>> Neethi
>> > > >
>> > > >
>> > > > Thanks
>> > > > Deepal
>> > > >
>> > > >
>> > > > > Hi All,
>> > > > >
>> > > > > I am coding MTOM Policy assertion mentioned in
>> > > > > http://blogs.cocoondev.org/dims/archives/003534.html
>> > > > >
>> > > > >
>> > > > > I coded a builder and the relevant model for the policy
>> assertion. The
>> > > > > problem is where to put the implementation? To which
>> project should
>> > > > > this belong to?
>> > > > >
>> > > > > We can put this in "Axis2" or "Neethi".
>> > > > >
>> > > > > Thanks,
>> > > > > Dimuthu.
>> > > > >
>> > > > >
>> ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > Thanks,
>> > > > Deepal
>> > > > ................................................................
>> > > > "The highest tower is built one brick at a time"
>> > > >
>> > > >
>> > > >
>> > > >
>> ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> > > >
>> > > >
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> > >
>> > >
>> >
>> >
>> > --
>> > David Illsley - IBM Web Services Development
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
- --
Sanka Samaranayake
WSO2 Inc.
http://sankas.blogspot.com/
http://www.wso2.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
iD8DBQFFoR8N/Hd0ETKdgNIRAireAJ9VFH7Q+80GTvmXlsgtYrZVg/4p2wCfbasn
yQDtK3EMIfNJwPFoI4S4O5w=
=rhje
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Thilina Gunarathne <cs...@gmail.com>.
AFAIK Neethi is the policy framework.. The concrete implementations
like these stay in the relevant locations.. Ex: sec policy resides in
Axis2 & will get moved with security..
IMHO this needs to go in to Axis2.
>It is also used for optimizing encrypted attachments. So should it go
>to Neethi, because it is used both by Rampart and Axis2.
Rampart anyway depends on Axis2.. So i don't see any issue in putting
it to Axis2.
Thanks,
~Thilina
On 1/5/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> It deosn't depend on Axis2.
>
> -Dimuthu
>
> On 1/5/07, David Illsley <da...@gmail.com> wrote:
> > IMO If it doesn't depend on axis2 classes it should go into neethi. If
> > it does it should go in Axis2.
> >
> > David
> >
> > On 05/01/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> > > Hi Deepal,
> > > We can argue both ways.
> > >
> > > This policy assertion will be mainly used by Axis2 to optimize binary
> > > data. So it should go to Axis2.
> > >
> > > It is also used for optimizing encrypted attachments. So should it go
> > > to Neethi, because it is used both by Rampart and Axis2.
> > >
> > > Thanks,
> > > Dimuthu.
> > >
> > > On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > > > Hi Dimuthu ;
> > > >
> > > > If it is Axis2 specific then , it should go to Axis2 .o.w to Neethi
> > > >
> > > >
> > > > Thanks
> > > > Deepal
> > > >
> > > >
> > > > > Hi All,
> > > > >
> > > > > I am coding MTOM Policy assertion mentioned in
> > > > > http://blogs.cocoondev.org/dims/archives/003534.html
> > > > >
> > > > >
> > > > > I coded a builder and the relevant model for the policy assertion. The
> > > > > problem is where to put the implementation? To which project should
> > > > > this belong to?
> > > > >
> > > > > We can put this in "Axis2" or "Neethi".
> > > > >
> > > > > Thanks,
> > > > > Dimuthu.
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Thanks,
> > > > Deepal
> > > > ................................................................
> > > > "The highest tower is built one brick at a time"
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > David Illsley - IBM Web Services Development
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Davanum Srinivas <da...@gmail.com>.
I guess, i defer to thilina's judgement on this one. plz scratch prev comment.
-- dims
On 1/5/07, Davanum Srinivas <da...@gmail.com> wrote:
> Then put it in neethi :) If we see a need later, then we can move it.
>
> -- dims
>
> On 1/5/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> > It deosn't depend on Axis2.
> >
> > -Dimuthu
> >
> > On 1/5/07, David Illsley <da...@gmail.com> wrote:
> > > IMO If it doesn't depend on axis2 classes it should go into neethi. If
> > > it does it should go in Axis2.
> > >
> > > David
> > >
> > > On 05/01/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> > > > Hi Deepal,
> > > > We can argue both ways.
> > > >
> > > > This policy assertion will be mainly used by Axis2 to optimize binary
> > > > data. So it should go to Axis2.
> > > >
> > > > It is also used for optimizing encrypted attachments. So should it go
> > > > to Neethi, because it is used both by Rampart and Axis2.
> > > >
> > > > Thanks,
> > > > Dimuthu.
> > > >
> > > > On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > > > > Hi Dimuthu ;
> > > > >
> > > > > If it is Axis2 specific then , it should go to Axis2 .o.w to Neethi
> > > > >
> > > > >
> > > > > Thanks
> > > > > Deepal
> > > > >
> > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > I am coding MTOM Policy assertion mentioned in
> > > > > > http://blogs.cocoondev.org/dims/archives/003534.html
> > > > > >
> > > > > >
> > > > > > I coded a builder and the relevant model for the policy assertion. The
> > > > > > problem is where to put the implementation? To which project should
> > > > > > this belong to?
> > > > > >
> > > > > > We can put this in "Axis2" or "Neethi".
> > > > > >
> > > > > > Thanks,
> > > > > > Dimuthu.
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Thanks,
> > > > > Deepal
> > > > > ................................................................
> > > > > "The highest tower is built one brick at a time"
> > > > >
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > David Illsley - IBM Web Services Development
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Davanum Srinivas <da...@gmail.com>.
Then put it in neethi :) If we see a need later, then we can move it.
-- dims
On 1/5/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> It deosn't depend on Axis2.
>
> -Dimuthu
>
> On 1/5/07, David Illsley <da...@gmail.com> wrote:
> > IMO If it doesn't depend on axis2 classes it should go into neethi. If
> > it does it should go in Axis2.
> >
> > David
> >
> > On 05/01/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> > > Hi Deepal,
> > > We can argue both ways.
> > >
> > > This policy assertion will be mainly used by Axis2 to optimize binary
> > > data. So it should go to Axis2.
> > >
> > > It is also used for optimizing encrypted attachments. So should it go
> > > to Neethi, because it is used both by Rampart and Axis2.
> > >
> > > Thanks,
> > > Dimuthu.
> > >
> > > On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > > > Hi Dimuthu ;
> > > >
> > > > If it is Axis2 specific then , it should go to Axis2 .o.w to Neethi
> > > >
> > > >
> > > > Thanks
> > > > Deepal
> > > >
> > > >
> > > > > Hi All,
> > > > >
> > > > > I am coding MTOM Policy assertion mentioned in
> > > > > http://blogs.cocoondev.org/dims/archives/003534.html
> > > > >
> > > > >
> > > > > I coded a builder and the relevant model for the policy assertion. The
> > > > > problem is where to put the implementation? To which project should
> > > > > this belong to?
> > > > >
> > > > > We can put this in "Axis2" or "Neethi".
> > > > >
> > > > > Thanks,
> > > > > Dimuthu.
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Thanks,
> > > > Deepal
> > > > ................................................................
> > > > "The highest tower is built one brick at a time"
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > David Illsley - IBM Web Services Development
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Dimuthu Leelaratne <di...@gmail.com>.
It deosn't depend on Axis2.
-Dimuthu
On 1/5/07, David Illsley <da...@gmail.com> wrote:
> IMO If it doesn't depend on axis2 classes it should go into neethi. If
> it does it should go in Axis2.
>
> David
>
> On 05/01/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> > Hi Deepal,
> > We can argue both ways.
> >
> > This policy assertion will be mainly used by Axis2 to optimize binary
> > data. So it should go to Axis2.
> >
> > It is also used for optimizing encrypted attachments. So should it go
> > to Neethi, because it is used both by Rampart and Axis2.
> >
> > Thanks,
> > Dimuthu.
> >
> > On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > > Hi Dimuthu ;
> > >
> > > If it is Axis2 specific then , it should go to Axis2 .o.w to Neethi
> > >
> > >
> > > Thanks
> > > Deepal
> > >
> > >
> > > > Hi All,
> > > >
> > > > I am coding MTOM Policy assertion mentioned in
> > > > http://blogs.cocoondev.org/dims/archives/003534.html
> > > >
> > > >
> > > > I coded a builder and the relevant model for the policy assertion. The
> > > > problem is where to put the implementation? To which project should
> > > > this belong to?
> > > >
> > > > We can put this in "Axis2" or "Neethi".
> > > >
> > > > Thanks,
> > > > Dimuthu.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > > >
> > > >
> > >
> > > --
> > > Thanks,
> > > Deepal
> > > ................................................................
> > > "The highest tower is built one brick at a time"
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> David Illsley - IBM Web Services Development
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by David Illsley <da...@gmail.com>.
IMO If it doesn't depend on axis2 classes it should go into neethi. If
it does it should go in Axis2.
David
On 05/01/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> Hi Deepal,
> We can argue both ways.
>
> This policy assertion will be mainly used by Axis2 to optimize binary
> data. So it should go to Axis2.
>
> It is also used for optimizing encrypted attachments. So should it go
> to Neethi, because it is used both by Rampart and Axis2.
>
> Thanks,
> Dimuthu.
>
> On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > Hi Dimuthu ;
> >
> > If it is Axis2 specific then , it should go to Axis2 .o.w to Neethi
> >
> >
> > Thanks
> > Deepal
> >
> >
> > > Hi All,
> > >
> > > I am coding MTOM Policy assertion mentioned in
> > > http://blogs.cocoondev.org/dims/archives/003534.html
> > >
> > >
> > > I coded a builder and the relevant model for the policy assertion. The
> > > problem is where to put the implementation? To which project should
> > > this belong to?
> > >
> > > We can put this in "Axis2" or "Neethi".
> > >
> > > Thanks,
> > > Dimuthu.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> > >
> >
> > --
> > Thanks,
> > Deepal
> > ................................................................
> > "The highest tower is built one brick at a time"
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Dimuthu Leelaratne <di...@gmail.com>.
Hi Deepal,
We can argue both ways.
This policy assertion will be mainly used by Axis2 to optimize binary
data. So it should go to Axis2.
It is also used for optimizing encrypted attachments. So should it go
to Neethi, because it is used both by Rampart and Axis2.
Thanks,
Dimuthu.
On 1/5/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> Hi Dimuthu ;
>
> If it is Axis2 specific then , it should go to Axis2 .o.w to Neethi
>
>
> Thanks
> Deepal
>
>
> > Hi All,
> >
> > I am coding MTOM Policy assertion mentioned in
> > http://blogs.cocoondev.org/dims/archives/003534.html
> >
> >
> > I coded a builder and the relevant model for the policy assertion. The
> > problem is where to put the implementation? To which project should
> > this belong to?
> >
> > We can put this in "Axis2" or "Neethi".
> >
> > Thanks,
> > Dimuthu.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [AXIS2] MTOM Policy assertion
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Dimuthu ;
If it is Axis2 specific then , it should go to Axis2 .o.w to Neethi
Thanks
Deepal
> Hi All,
>
> I am coding MTOM Policy assertion mentioned in
> http://blogs.cocoondev.org/dims/archives/003534.html
>
>
> I coded a builder and the relevant model for the policy assertion. The
> problem is where to put the implementation? To which project should
> this belong to?
>
> We can put this in "Axis2" or "Neethi".
>
> Thanks,
> Dimuthu.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org