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 Eran Chinthaka <ch...@opensource.lk> on 2005/11/20 17:47:31 UTC
[Axis2] In searching for a place for DOM impl
Hi all,
As you know Ruchith is doing an implementation of DOM on OM. We have a
small problem in keeping this implementation.
(ns:module= maven module)
It was in the XML module for some time, but later moved to SAAJ module
to resolve a problem with JDK 1.5. But I feel like the DOM impl do not
belong to neither XML module nor SAAJ module.
I think I don't need to explain why it doesn't belong to SAAJ module. If
we put that in SAAJ, it will create a cyclic dependecy as well. And for
XML module, I'd like to have it clean only with the current stuff. I
think DOM impl should not come *in to* that module.
So the option left is to have a new and separate module for DOM
implementation. Its better to settle with something as I know Ruchith is
having an unnecessary headache due to this.
What do you all think ? I like to DOM impl, a separate module, so that
people who need that can use it, whilst others can discard it.
-- Chinthaka
Re: [Axis2] In searching for a place for DOM impl
Posted by Davanum Srinivas <da...@gmail.com>.
Sanjiva,
I think we should hold our horse on the dom stuff? Right now
security.mar will need it and saaj will need it. So having a separate
module is absolutely fine.
dom2/dom3 is a tricky problem. If we make some dom3 classes available
in axis jar itself as is being done now, we will land up in nasty
situations for classloader problems. Since the current use case is the
security.mar, having this code in a separate optional jar that is
loaded by security.mar (and associated classloader) seems to be the
way to go, IMHO.
thanks,
dims
On 11/20/05, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> On Sun, 2005-11-20 at 22:47 +0600, Eran Chinthaka wrote:
> > Hi all,
> >
> > As you know Ruchith is doing an implementation of DOM on OM. We have a
> > small problem in keeping this implementation.
> >
> > (ns:module= maven module)
> >
> > It was in the XML module for some time, but later moved to SAAJ module
> > to resolve a problem with JDK 1.5. But I feel like the DOM impl do not
> > belong to neither XML module nor SAAJ module.
> > I think I don't need to explain why it doesn't belong to SAAJ module. If
> > we put that in SAAJ, it will create a cyclic dependecy as well. And for
> > XML module, I'd like to have it clean only with the current stuff. I
> > think DOM impl should not come *in to* that module.
> > So the option left is to have a new and separate module for DOM
> > implementation. Its better to settle with something as I know Ruchith is
> > having an unnecessary headache due to this.
> > What do you all think ? I like to DOM impl, a separate module, so that
> > people who need that can use it, whilst others can discard it.
>
> What Ruchith is implementing is an *OM* implementation which also
> supports the DOM APIs. As far as a majority of Axis2 is concerned, we'll
> be using it as an OM implementation. Its just the security code that
> needs it to be a DOM implementation as well.
>
> As an OM implementation, we have a clear place to put it in: the XML
> module. We already have 2 OM implementations in there- the LLOM and the
> TableOM.
>
> So, as yet another OM implementation IMO it belongs in the XML module.
> Why would you discriminate against this OM implementation by putting it
> somewhere else?
>
> Note that putting it somewhere else causes difficulty with tests for
> example as all the OM tests are in the OM module. The OM tests should be
> run against both (or all) OM implementations so that we know immediately
> if one of those tests fail for some reason.
>
> Sanjiva.
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] In searching for a place for DOM impl
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Sun, 2005-11-20 at 22:47 +0600, Eran Chinthaka wrote:
> Hi all,
>
> As you know Ruchith is doing an implementation of DOM on OM. We have a
> small problem in keeping this implementation.
>
> (ns:module= maven module)
>
> It was in the XML module for some time, but later moved to SAAJ module
> to resolve a problem with JDK 1.5. But I feel like the DOM impl do not
> belong to neither XML module nor SAAJ module.
> I think I don't need to explain why it doesn't belong to SAAJ module. If
> we put that in SAAJ, it will create a cyclic dependecy as well. And for
> XML module, I'd like to have it clean only with the current stuff. I
> think DOM impl should not come *in to* that module.
> So the option left is to have a new and separate module for DOM
> implementation. Its better to settle with something as I know Ruchith is
> having an unnecessary headache due to this.
> What do you all think ? I like to DOM impl, a separate module, so that
> people who need that can use it, whilst others can discard it.
What Ruchith is implementing is an *OM* implementation which also
supports the DOM APIs. As far as a majority of Axis2 is concerned, we'll
be using it as an OM implementation. Its just the security code that
needs it to be a DOM implementation as well.
As an OM implementation, we have a clear place to put it in: the XML
module. We already have 2 OM implementations in there- the LLOM and the
TableOM.
So, as yet another OM implementation IMO it belongs in the XML module.
Why would you discriminate against this OM implementation by putting it
somewhere else?
Note that putting it somewhere else causes difficulty with tests for
example as all the OM tests are in the OM module. The OM tests should be
run against both (or all) OM implementations so that we know immediately
if one of those tests fail for some reason.
Sanjiva.
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Glen,
Any news about shepherding a release? I've cut a temporary branch for
the geronimo guys to make a snapshot out of (for now).
https://svn.apache.org/repos/asf/webservices/axis/branches/axis-1.4-20051205/
Thanks,
dims
On 11/29/05, Davanum Srinivas <da...@gmail.com> wrote:
> Matt,
>
> Just got word from Glen (he's in Montreal!). We are going to try doing
> cutting a release on thursday night.
>
> thanks,
> dims
>
> On 11/29/05, Matt Hogstrom <ma...@hogstrom.org> wrote:
> > I'd like to follow up our earlier request for a new release of Axis. We are
> > starting testing later this week and would appreciate if a 1.3.1 or a 1.4
> > release can be cut. Please advise as to the possibility of this happening so we
> > can plan accordingly.
> >
> > Cheers,
> >
> > Matt
> >
> > Davanum Srinivas wrote:
> > > Matt,
> > >
> > > It may end up being called 1.4...The snapshots are here (updated hourly):
> > > http://cvs.apache.org/repository/axis/jars/
> > >
> > > thanks,
> > > dims
> > >
> > > On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
> > >
> > >>Matt,
> > >>
> > >>Let's see what we can do. Glen Daniels is the Release Manager and you
> > >>will need his buy-in :)
> > >>
> > >>thanks,
> > >>dims
> > >>
> > >>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> > >>
> > >>>Sorry, after reading this. ApacheCon is December 10th. I meant
> > >>>December 3rd for the cut but the earlier the better. Sorry for the
> > >>>mis-statement.
> > >>>
> > >>>Matt
> > >>>
> > >>>hogstrom wrote:
> > >>>
> > >>>
> > >>>>On behalf of the Geronimo team I'd like to request a new release of
> > >>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> > >>>>(or something like that). We are looking to formally cut our 1.0
> > >>>>release of Geronimo for announcement at ApacheCon coming up in
> > >>>>December. Of primary concern was a patch submitted by Kevan Miller
> > >>>>that identified a memory leak that was incorporated after the 1.3
> > >>>>release of Axis.
> > >>>>
> > >>>>Can you please advise as to when (and if) a new release can be made
> > >>>>available? We would like to start TCK testing of Geronimo around
> > >>>>December 10th but the earlier the better for a new cut of Axis so we
> > >>>>can get as much coverage as possible.
> > >>>>
> > >>>>Thanks for your help.
> > >>>>
> > >>>>Matt
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>--
> > >>Davanum Srinivas : http://wso2.com/blogs/
> > >>
> > >
> > >
> > >
> > > --
> > > Davanum Srinivas : http://wso2.com/blogs/
> > >
> > >
> > >
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Glen,
Any news about shepherding a release? I've cut a temporary branch for
the geronimo guys to make a snapshot out of (for now).
https://svn.apache.org/repos/asf/webservices/axis/branches/axis-1.4-20051205/
Thanks,
dims
On 11/29/05, Davanum Srinivas <da...@gmail.com> wrote:
> Matt,
>
> Just got word from Glen (he's in Montreal!). We are going to try doing
> cutting a release on thursday night.
>
> thanks,
> dims
>
> On 11/29/05, Matt Hogstrom <ma...@hogstrom.org> wrote:
> > I'd like to follow up our earlier request for a new release of Axis. We are
> > starting testing later this week and would appreciate if a 1.3.1 or a 1.4
> > release can be cut. Please advise as to the possibility of this happening so we
> > can plan accordingly.
> >
> > Cheers,
> >
> > Matt
> >
> > Davanum Srinivas wrote:
> > > Matt,
> > >
> > > It may end up being called 1.4...The snapshots are here (updated hourly):
> > > http://cvs.apache.org/repository/axis/jars/
> > >
> > > thanks,
> > > dims
> > >
> > > On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
> > >
> > >>Matt,
> > >>
> > >>Let's see what we can do. Glen Daniels is the Release Manager and you
> > >>will need his buy-in :)
> > >>
> > >>thanks,
> > >>dims
> > >>
> > >>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> > >>
> > >>>Sorry, after reading this. ApacheCon is December 10th. I meant
> > >>>December 3rd for the cut but the earlier the better. Sorry for the
> > >>>mis-statement.
> > >>>
> > >>>Matt
> > >>>
> > >>>hogstrom wrote:
> > >>>
> > >>>
> > >>>>On behalf of the Geronimo team I'd like to request a new release of
> > >>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> > >>>>(or something like that). We are looking to formally cut our 1.0
> > >>>>release of Geronimo for announcement at ApacheCon coming up in
> > >>>>December. Of primary concern was a patch submitted by Kevan Miller
> > >>>>that identified a memory leak that was incorporated after the 1.3
> > >>>>release of Axis.
> > >>>>
> > >>>>Can you please advise as to when (and if) a new release can be made
> > >>>>available? We would like to start TCK testing of Geronimo around
> > >>>>December 10th but the earlier the better for a new cut of Axis so we
> > >>>>can get as much coverage as possible.
> > >>>>
> > >>>>Thanks for your help.
> > >>>>
> > >>>>Matt
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>--
> > >>Davanum Srinivas : http://wso2.com/blogs/
> > >>
> > >
> > >
> > >
> > > --
> > > Davanum Srinivas : http://wso2.com/blogs/
> > >
> > >
> > >
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Matt,
Just got word from Glen (he's in Montreal!). We are going to try doing
cutting a release on thursday night.
thanks,
dims
On 11/29/05, Matt Hogstrom <ma...@hogstrom.org> wrote:
> I'd like to follow up our earlier request for a new release of Axis. We are
> starting testing later this week and would appreciate if a 1.3.1 or a 1.4
> release can be cut. Please advise as to the possibility of this happening so we
> can plan accordingly.
>
> Cheers,
>
> Matt
>
> Davanum Srinivas wrote:
> > Matt,
> >
> > It may end up being called 1.4...The snapshots are here (updated hourly):
> > http://cvs.apache.org/repository/axis/jars/
> >
> > thanks,
> > dims
> >
> > On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
> >
> >>Matt,
> >>
> >>Let's see what we can do. Glen Daniels is the Release Manager and you
> >>will need his buy-in :)
> >>
> >>thanks,
> >>dims
> >>
> >>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> >>
> >>>Sorry, after reading this. ApacheCon is December 10th. I meant
> >>>December 3rd for the cut but the earlier the better. Sorry for the
> >>>mis-statement.
> >>>
> >>>Matt
> >>>
> >>>hogstrom wrote:
> >>>
> >>>
> >>>>On behalf of the Geronimo team I'd like to request a new release of
> >>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> >>>>(or something like that). We are looking to formally cut our 1.0
> >>>>release of Geronimo for announcement at ApacheCon coming up in
> >>>>December. Of primary concern was a patch submitted by Kevan Miller
> >>>>that identified a memory leak that was incorporated after the 1.3
> >>>>release of Axis.
> >>>>
> >>>>Can you please advise as to when (and if) a new release can be made
> >>>>available? We would like to start TCK testing of Geronimo around
> >>>>December 10th but the earlier the better for a new cut of Axis so we
> >>>>can get as much coverage as possible.
> >>>>
> >>>>Thanks for your help.
> >>>>
> >>>>Matt
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>
> >>--
> >>Davanum Srinivas : http://wso2.com/blogs/
> >>
> >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> >
> >
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Matt,
Just got word from Glen (he's in Montreal!). We are going to try doing
cutting a release on thursday night.
thanks,
dims
On 11/29/05, Matt Hogstrom <ma...@hogstrom.org> wrote:
> I'd like to follow up our earlier request for a new release of Axis. We are
> starting testing later this week and would appreciate if a 1.3.1 or a 1.4
> release can be cut. Please advise as to the possibility of this happening so we
> can plan accordingly.
>
> Cheers,
>
> Matt
>
> Davanum Srinivas wrote:
> > Matt,
> >
> > It may end up being called 1.4...The snapshots are here (updated hourly):
> > http://cvs.apache.org/repository/axis/jars/
> >
> > thanks,
> > dims
> >
> > On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
> >
> >>Matt,
> >>
> >>Let's see what we can do. Glen Daniels is the Release Manager and you
> >>will need his buy-in :)
> >>
> >>thanks,
> >>dims
> >>
> >>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> >>
> >>>Sorry, after reading this. ApacheCon is December 10th. I meant
> >>>December 3rd for the cut but the earlier the better. Sorry for the
> >>>mis-statement.
> >>>
> >>>Matt
> >>>
> >>>hogstrom wrote:
> >>>
> >>>
> >>>>On behalf of the Geronimo team I'd like to request a new release of
> >>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> >>>>(or something like that). We are looking to formally cut our 1.0
> >>>>release of Geronimo for announcement at ApacheCon coming up in
> >>>>December. Of primary concern was a patch submitted by Kevan Miller
> >>>>that identified a memory leak that was incorporated after the 1.3
> >>>>release of Axis.
> >>>>
> >>>>Can you please advise as to when (and if) a new release can be made
> >>>>available? We would like to start TCK testing of Geronimo around
> >>>>December 10th but the earlier the better for a new cut of Axis so we
> >>>>can get as much coverage as possible.
> >>>>
> >>>>Thanks for your help.
> >>>>
> >>>>Matt
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>
> >>--
> >>Davanum Srinivas : http://wso2.com/blogs/
> >>
> >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> >
> >
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon
in December
Posted by Matt Hogstrom <ma...@hogstrom.org>.
I'd like to follow up our earlier request for a new release of Axis. We are
starting testing later this week and would appreciate if a 1.3.1 or a 1.4
release can be cut. Please advise as to the possibility of this happening so we
can plan accordingly.
Cheers,
Matt
Davanum Srinivas wrote:
> Matt,
>
> It may end up being called 1.4...The snapshots are here (updated hourly):
> http://cvs.apache.org/repository/axis/jars/
>
> thanks,
> dims
>
> On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
>
>>Matt,
>>
>>Let's see what we can do. Glen Daniels is the Release Manager and you
>>will need his buy-in :)
>>
>>thanks,
>>dims
>>
>>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
>>
>>>Sorry, after reading this. ApacheCon is December 10th. I meant
>>>December 3rd for the cut but the earlier the better. Sorry for the
>>>mis-statement.
>>>
>>>Matt
>>>
>>>hogstrom wrote:
>>>
>>>
>>>>On behalf of the Geronimo team I'd like to request a new release of
>>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
>>>>(or something like that). We are looking to formally cut our 1.0
>>>>release of Geronimo for announcement at ApacheCon coming up in
>>>>December. Of primary concern was a patch submitted by Kevan Miller
>>>>that identified a memory leak that was incorporated after the 1.3
>>>>release of Axis.
>>>>
>>>>Can you please advise as to when (and if) a new release can be made
>>>>available? We would like to start TCK testing of Geronimo around
>>>>December 10th but the earlier the better for a new cut of Axis so we
>>>>can get as much coverage as possible.
>>>>
>>>>Thanks for your help.
>>>>
>>>>Matt
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>--
>>Davanum Srinivas : http://wso2.com/blogs/
>>
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
>
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon
in December
Posted by Matt Hogstrom <ma...@hogstrom.org>.
I'd like to follow up our earlier request for a new release of Axis. We are
starting testing later this week and would appreciate if a 1.3.1 or a 1.4
release can be cut. Please advise as to the possibility of this happening so we
can plan accordingly.
Cheers,
Matt
Davanum Srinivas wrote:
> Matt,
>
> It may end up being called 1.4...The snapshots are here (updated hourly):
> http://cvs.apache.org/repository/axis/jars/
>
> thanks,
> dims
>
> On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
>
>>Matt,
>>
>>Let's see what we can do. Glen Daniels is the Release Manager and you
>>will need his buy-in :)
>>
>>thanks,
>>dims
>>
>>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
>>
>>>Sorry, after reading this. ApacheCon is December 10th. I meant
>>>December 3rd for the cut but the earlier the better. Sorry for the
>>>mis-statement.
>>>
>>>Matt
>>>
>>>hogstrom wrote:
>>>
>>>
>>>>On behalf of the Geronimo team I'd like to request a new release of
>>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
>>>>(or something like that). We are looking to formally cut our 1.0
>>>>release of Geronimo for announcement at ApacheCon coming up in
>>>>December. Of primary concern was a patch submitted by Kevan Miller
>>>>that identified a memory leak that was incorporated after the 1.3
>>>>release of Axis.
>>>>
>>>>Can you please advise as to when (and if) a new release can be made
>>>>available? We would like to start TCK testing of Geronimo around
>>>>December 10th but the earlier the better for a new cut of Axis so we
>>>>can get as much coverage as possible.
>>>>
>>>>Thanks for your help.
>>>>
>>>>Matt
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>--
>>Davanum Srinivas : http://wso2.com/blogs/
>>
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
>
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Please go ahead and do it.
thanks,
dims
On 12/6/05, Matt Hogstrom <ma...@hogstrom.org> wrote:
> 4@hogstrom.org> <19...@mail.gmail.com> <19...@mail.gmail.com>
> In-Reply-To: <19...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> X-MMS-Smtp-Program: Macallan-Mail-Solution; Version 4.6.0.1
> X-MMS-Smtp-Auth: Authenticated As matt@hogstrom.org
> X-MMS-Smtp-Mailer-Program: Macallan-Mail-Solution; Version 4.6.0.1
>
> Dims,
>
> Thanks for doing this. Could you place this in
> /www/cvs.apache.org/repository/axis/jars? I'd be happy to do it but didn't want
> to be presumptious.
>
> Matt
>
> Davanum Srinivas wrote:
> > Glen,
> > Any news about shepherding a release? I've cut a temporary branch for
> > the geronimo guys to make a snapshot out of (for now).
> >
> > https://svn.apache.org/repos/asf/webservices/axis/branches/axis-1.4-20051205/
> >
> > Thanks,
> > dims
> >
> > On 11/29/05, Davanum Srinivas <da...@gmail.com> wrote:
> >
> >>Matt,
> >>
> >>Just got word from Glen (he's in Montreal!). We are going to try doing
> >>cutting a release on thursday night.
> >>
> >>thanks,
> >>dims
> >>
> >>On 11/29/05, Matt Hogstrom <ma...@hogstrom.org> wrote:
> >>
> >>>I'd like to follow up our earlier request for a new release of Axis. We are
> >>>starting testing later this week and would appreciate if a 1.3.1 or a 1.4
> >>>release can be cut. Please advise as to the possibility of this happening so we
> >>>can plan accordingly.
> >>>
> >>>Cheers,
> >>>
> >>>Matt
> >>>
> >>>Davanum Srinivas wrote:
> >>>
> >>>>Matt,
> >>>>
> >>>>It may end up being called 1.4...The snapshots are here (updated hourly):
> >>>>http://cvs.apache.org/repository/axis/jars/
> >>>>
> >>>>thanks,
> >>>>dims
> >>>>
> >>>>On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
> >>>>
> >>>>
> >>>>>Matt,
> >>>>>
> >>>>>Let's see what we can do. Glen Daniels is the Release Manager and you
> >>>>>will need his buy-in :)
> >>>>>
> >>>>>thanks,
> >>>>>dims
> >>>>>
> >>>>>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> >>>>>
> >>>>>
> >>>>>>Sorry, after reading this. ApacheCon is December 10th. I meant
> >>>>>>December 3rd for the cut but the earlier the better. Sorry for the
> >>>>>>mis-statement.
> >>>>>>
> >>>>>>Matt
> >>>>>>
> >>>>>>hogstrom wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>On behalf of the Geronimo team I'd like to request a new release of
> >>>>>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> >>>>>>>(or something like that). We are looking to formally cut our 1.0
> >>>>>>>release of Geronimo for announcement at ApacheCon coming up in
> >>>>>>>December. Of primary concern was a patch submitted by Kevan Miller
> >>>>>>>that identified a memory leak that was incorporated after the 1.3
> >>>>>>>release of Axis.
> >>>>>>>
> >>>>>>>Can you please advise as to when (and if) a new release can be made
> >>>>>>>available? We would like to start TCK testing of Geronimo around
> >>>>>>>December 10th but the earlier the better for a new cut of Axis so we
> >>>>>>>can get as much coverage as possible.
> >>>>>>>
> >>>>>>>Thanks for your help.
> >>>>>>>
> >>>>>>>Matt
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>--
> >>>>>Davanum Srinivas : http://wso2.com/blogs/
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>--
> >>>>Davanum Srinivas : http://wso2.com/blogs/
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>--
> >>Davanum Srinivas : http://wso2.com/blogs/
> >>
> >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> >
> >
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon
in December
Posted by Matt Hogstrom <ma...@hogstrom.org>.
4@hogstrom.org> <19...@mail.gmail.com> <19...@mail.gmail.com>
In-Reply-To: <19...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MMS-Smtp-Program: Macallan-Mail-Solution; Version 4.6.0.1
X-MMS-Smtp-Auth: Authenticated As matt@hogstrom.org
X-MMS-Smtp-Mailer-Program: Macallan-Mail-Solution; Version 4.6.0.1
Dims,
Thanks for doing this. Could you place this in
/www/cvs.apache.org/repository/axis/jars? I'd be happy to do it but didn't want
to be presumptious.
Matt
Davanum Srinivas wrote:
> Glen,
> Any news about shepherding a release? I've cut a temporary branch for
> the geronimo guys to make a snapshot out of (for now).
>
> https://svn.apache.org/repos/asf/webservices/axis/branches/axis-1.4-20051205/
>
> Thanks,
> dims
>
> On 11/29/05, Davanum Srinivas <da...@gmail.com> wrote:
>
>>Matt,
>>
>>Just got word from Glen (he's in Montreal!). We are going to try doing
>>cutting a release on thursday night.
>>
>>thanks,
>>dims
>>
>>On 11/29/05, Matt Hogstrom <ma...@hogstrom.org> wrote:
>>
>>>I'd like to follow up our earlier request for a new release of Axis. We are
>>>starting testing later this week and would appreciate if a 1.3.1 or a 1.4
>>>release can be cut. Please advise as to the possibility of this happening so we
>>>can plan accordingly.
>>>
>>>Cheers,
>>>
>>>Matt
>>>
>>>Davanum Srinivas wrote:
>>>
>>>>Matt,
>>>>
>>>>It may end up being called 1.4...The snapshots are here (updated hourly):
>>>>http://cvs.apache.org/repository/axis/jars/
>>>>
>>>>thanks,
>>>>dims
>>>>
>>>>On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
>>>>
>>>>
>>>>>Matt,
>>>>>
>>>>>Let's see what we can do. Glen Daniels is the Release Manager and you
>>>>>will need his buy-in :)
>>>>>
>>>>>thanks,
>>>>>dims
>>>>>
>>>>>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
>>>>>
>>>>>
>>>>>>Sorry, after reading this. ApacheCon is December 10th. I meant
>>>>>>December 3rd for the cut but the earlier the better. Sorry for the
>>>>>>mis-statement.
>>>>>>
>>>>>>Matt
>>>>>>
>>>>>>hogstrom wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>On behalf of the Geronimo team I'd like to request a new release of
>>>>>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
>>>>>>>(or something like that). We are looking to formally cut our 1.0
>>>>>>>release of Geronimo for announcement at ApacheCon coming up in
>>>>>>>December. Of primary concern was a patch submitted by Kevan Miller
>>>>>>>that identified a memory leak that was incorporated after the 1.3
>>>>>>>release of Axis.
>>>>>>>
>>>>>>>Can you please advise as to when (and if) a new release can be made
>>>>>>>available? We would like to start TCK testing of Geronimo around
>>>>>>>December 10th but the earlier the better for a new cut of Axis so we
>>>>>>>can get as much coverage as possible.
>>>>>>>
>>>>>>>Thanks for your help.
>>>>>>>
>>>>>>>Matt
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>--
>>>>>Davanum Srinivas : http://wso2.com/blogs/
>>>>>
>>>>
>>>>
>>>>
>>>>--
>>>>Davanum Srinivas : http://wso2.com/blogs/
>>>>
>>>>
>>>>
>>>
>>>
>>
>>--
>>Davanum Srinivas : http://wso2.com/blogs/
>>
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
>
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon
in December
Posted by Matt Hogstrom <ma...@hogstrom.org>.
4@hogstrom.org> <19...@mail.gmail.com>
In-Reply-To: <19...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MMS-Smtp-Program: Macallan-Mail-Solution; Version 4.6.0.1
X-MMS-Smtp-Auth: Authenticated As matt@hogstrom.org
X-MMS-Smtp-Mailer-Program: Macallan-Mail-Solution; Version 4.6.0.1
Excellent news Dims...thanks much. Testing with the 1.4-SNAPSHOT today.
Davanum Srinivas wrote:
> Matt,
>
> Just got word from Glen (he's in Montreal!). We are going to try doing
> cutting a release on thursday night.
>
> thanks,
> dims
>
> On 11/29/05, Matt Hogstrom <ma...@hogstrom.org> wrote:
>
>>I'd like to follow up our earlier request for a new release of Axis. We are
>>starting testing later this week and would appreciate if a 1.3.1 or a 1.4
>>release can be cut. Please advise as to the possibility of this happening so we
>>can plan accordingly.
>>
>>Cheers,
>>
>>Matt
>>
>>Davanum Srinivas wrote:
>>
>>>Matt,
>>>
>>>It may end up being called 1.4...The snapshots are here (updated hourly):
>>>http://cvs.apache.org/repository/axis/jars/
>>>
>>>thanks,
>>>dims
>>>
>>>On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
>>>
>>>
>>>>Matt,
>>>>
>>>>Let's see what we can do. Glen Daniels is the Release Manager and you
>>>>will need his buy-in :)
>>>>
>>>>thanks,
>>>>dims
>>>>
>>>>On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
>>>>
>>>>
>>>>>Sorry, after reading this. ApacheCon is December 10th. I meant
>>>>>December 3rd for the cut but the earlier the better. Sorry for the
>>>>>mis-statement.
>>>>>
>>>>>Matt
>>>>>
>>>>>hogstrom wrote:
>>>>>
>>>>>
>>>>>
>>>>>>On behalf of the Geronimo team I'd like to request a new release of
>>>>>>Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
>>>>>>(or something like that). We are looking to formally cut our 1.0
>>>>>>release of Geronimo for announcement at ApacheCon coming up in
>>>>>>December. Of primary concern was a patch submitted by Kevan Miller
>>>>>>that identified a memory leak that was incorporated after the 1.3
>>>>>>release of Axis.
>>>>>>
>>>>>>Can you please advise as to when (and if) a new release can be made
>>>>>>available? We would like to start TCK testing of Geronimo around
>>>>>>December 10th but the earlier the better for a new cut of Axis so we
>>>>>>can get as much coverage as possible.
>>>>>>
>>>>>>Thanks for your help.
>>>>>>
>>>>>>Matt
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>--
>>>>Davanum Srinivas : http://wso2.com/blogs/
>>>>
>>>
>>>
>>>
>>>--
>>>Davanum Srinivas : http://wso2.com/blogs/
>>>
>>>
>>>
>>
>>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
>
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Matt,
It may end up being called 1.4...The snapshots are here (updated hourly):
http://cvs.apache.org/repository/axis/jars/
thanks,
dims
On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
> Matt,
>
> Let's see what we can do. Glen Daniels is the Release Manager and you
> will need his buy-in :)
>
> thanks,
> dims
>
> On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> > Sorry, after reading this. ApacheCon is December 10th. I meant
> > December 3rd for the cut but the earlier the better. Sorry for the
> > mis-statement.
> >
> > Matt
> >
> > hogstrom wrote:
> >
> > > On behalf of the Geronimo team I'd like to request a new release of
> > > Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> > > (or something like that). We are looking to formally cut our 1.0
> > > release of Geronimo for announcement at ApacheCon coming up in
> > > December. Of primary concern was a patch submitted by Kevan Miller
> > > that identified a memory leak that was incorporated after the 1.3
> > > release of Axis.
> > >
> > > Can you please advise as to when (and if) a new release can be made
> > > available? We would like to start TCK testing of Geronimo around
> > > December 10th but the earlier the better for a new cut of Axis so we
> > > can get as much coverage as possible.
> > >
> > > Thanks for your help.
> > >
> > > Matt
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Matt,
It may end up being called 1.4...The snapshots are here (updated hourly):
http://cvs.apache.org/repository/axis/jars/
thanks,
dims
On 11/20/05, Davanum Srinivas <da...@gmail.com> wrote:
> Matt,
>
> Let's see what we can do. Glen Daniels is the Release Manager and you
> will need his buy-in :)
>
> thanks,
> dims
>
> On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> > Sorry, after reading this. ApacheCon is December 10th. I meant
> > December 3rd for the cut but the earlier the better. Sorry for the
> > mis-statement.
> >
> > Matt
> >
> > hogstrom wrote:
> >
> > > On behalf of the Geronimo team I'd like to request a new release of
> > > Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> > > (or something like that). We are looking to formally cut our 1.0
> > > release of Geronimo for announcement at ApacheCon coming up in
> > > December. Of primary concern was a patch submitted by Kevan Miller
> > > that identified a memory leak that was incorporated after the 1.3
> > > release of Axis.
> > >
> > > Can you please advise as to when (and if) a new release can be made
> > > available? We would like to start TCK testing of Geronimo around
> > > December 10th but the earlier the better for a new cut of Axis so we
> > > can get as much coverage as possible.
> > >
> > > Thanks for your help.
> > >
> > > Matt
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Matt,
Let's see what we can do. Glen Daniels is the Release Manager and you
will need his buy-in :)
thanks,
dims
On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> Sorry, after reading this. ApacheCon is December 10th. I meant
> December 3rd for the cut but the earlier the better. Sorry for the
> mis-statement.
>
> Matt
>
> hogstrom wrote:
>
> > On behalf of the Geronimo team I'd like to request a new release of
> > Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> > (or something like that). We are looking to formally cut our 1.0
> > release of Geronimo for announcement at ApacheCon coming up in
> > December. Of primary concern was a patch submitted by Kevan Miller
> > that identified a memory leak that was incorporated after the 1.3
> > release of Axis.
> >
> > Can you please advise as to when (and if) a new release can be made
> > available? We would like to start TCK testing of Geronimo around
> > December 10th but the earlier the better for a new cut of Axis so we
> > can get as much coverage as possible.
> >
> > Thanks for your help.
> >
> > Matt
> >
> >
> >
> >
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon in December
Posted by Davanum Srinivas <da...@gmail.com>.
Matt,
Let's see what we can do. Glen Daniels is the Release Manager and you
will need his buy-in :)
thanks,
dims
On 11/20/05, hogstrom <ma...@hogstrom.org> wrote:
> Sorry, after reading this. ApacheCon is December 10th. I meant
> December 3rd for the cut but the earlier the better. Sorry for the
> mis-statement.
>
> Matt
>
> hogstrom wrote:
>
> > On behalf of the Geronimo team I'd like to request a new release of
> > Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> > (or something like that). We are looking to formally cut our 1.0
> > release of Geronimo for announcement at ApacheCon coming up in
> > December. Of primary concern was a patch submitted by Kevan Miller
> > that identified a memory leak that was incorporated after the 1.3
> > release of Axis.
> >
> > Can you please advise as to when (and if) a new release can be made
> > available? We would like to start TCK testing of Geronimo around
> > December 10th but the earlier the better for a new cut of Axis so we
> > can get as much coverage as possible.
> >
> > Thanks for your help.
> >
> > Matt
> >
> >
> >
> >
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon
in December
Posted by hogstrom <ma...@hogstrom.org>.
Sorry, after reading this. ApacheCon is December 10th. I meant
December 3rd for the cut but the earlier the better. Sorry for the
mis-statement.
Matt
hogstrom wrote:
> On behalf of the Geronimo team I'd like to request a new release of
> Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> (or something like that). We are looking to formally cut our 1.0
> release of Geronimo for announcement at ApacheCon coming up in
> December. Of primary concern was a patch submitted by Kevan Miller
> that identified a memory leak that was incorporated after the 1.3
> release of Axis.
>
> Can you please advise as to when (and if) a new release can be made
> available? We would like to start TCK testing of Geronimo around
> December 10th but the earlier the better for a new cut of Axis so we
> can get as much coverage as possible.
>
> Thanks for your help.
>
> Matt
>
>
>
>
Re: Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon
in December
Posted by hogstrom <ma...@hogstrom.org>.
Sorry, after reading this. ApacheCon is December 10th. I meant
December 3rd for the cut but the earlier the better. Sorry for the
mis-statement.
Matt
hogstrom wrote:
> On behalf of the Geronimo team I'd like to request a new release of
> Axis 1.3 get cut that incorporates all current fixes and is name 1.3.1
> (or something like that). We are looking to formally cut our 1.0
> release of Geronimo for announcement at ApacheCon coming up in
> December. Of primary concern was a patch submitted by Kevan Miller
> that identified a memory leak that was incorporated after the 1.3
> release of Axis.
>
> Can you please advise as to when (and if) a new release can be made
> available? We would like to start TCK testing of Geronimo around
> December 10th but the earlier the better for a new cut of Axis so we
> can get as much coverage as possible.
>
> Thanks for your help.
>
> Matt
>
>
>
>
Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon
in December
Posted by hogstrom <ma...@hogstrom.org>.
On behalf of the Geronimo team I'd like to request a new release of Axis
1.3 get cut that incorporates all current fixes and is name 1.3.1 (or
something like that). We are looking to formally cut our 1.0 release of
Geronimo for announcement at ApacheCon coming up in December. Of
primary concern was a patch submitted by Kevan Miller that identified a
memory leak that was incorporated after the 1.3 release of Axis.
Can you please advise as to when (and if) a new release can be made
available? We would like to start TCK testing of Geronimo around
December 10th but the earlier the better for a new cut of Axis so we can
get as much coverage as possible.
Thanks for your help.
Matt
Request for a 1.3.1 Axis to support Geronimo Verion 1.0 for ApacheCon
in December
Posted by hogstrom <ma...@hogstrom.org>.
On behalf of the Geronimo team I'd like to request a new release of Axis
1.3 get cut that incorporates all current fixes and is name 1.3.1 (or
something like that). We are looking to formally cut our 1.0 release of
Geronimo for announcement at ApacheCon coming up in December. Of
primary concern was a patch submitted by Kevan Miller that identified a
memory leak that was incorporated after the 1.3 release of Axis.
Can you please advise as to when (and if) a new release can be made
available? We would like to start TCK testing of Geronimo around
December 10th but the earlier the better for a new cut of Axis so we can
get as much coverage as possible.
Thanks for your help.
Matt
Re: Question about Axis2 Performance Problem
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Sun, 2005-11-20 at 11:27 -0800, SUVANAN DUTTA wrote:
> Hi,
> I was trying to send few messages in a loop and see
> that there's a significant drop in performance when I
> use dual transport for blocking/non-blocking call. I
> am using Axis2 v0.91.
>
> For 100 messages in a loop,these are the readings,-
> Ping - 1.442sec.
> Echo(Blocking + Single Transport) - 1.732sec.
> Echo(Blocking + Dual Transport) - 10.865sec.
> Echo(Non-Blocking + Dual Transport) - 10.935sec.
>
> I cheked that Axis2 loads the addrssing module only
> once and re-uses it. Then what might be causing this?
> Is this already fixed post-0.91?
Could you please try this with the SVN Head and let us know? The dual
transport stuff is slower but this looks awfully too slow ..
Sanjiva.
Question about Axis2 Performance Problem
Posted by SUVANAN DUTTA <su...@yahoo.com>.
Hi,
I was trying to send few messages in a loop and see
that there's a significant drop in performance when I
use dual transport for blocking/non-blocking call. I
am using Axis2 v0.91.
For 100 messages in a loop,these are the readings,-
Ping - 1.442sec.
Echo(Blocking + Single Transport) - 1.732sec.
Echo(Blocking + Dual Transport) - 10.865sec.
Echo(Non-Blocking + Dual Transport) - 10.935sec.
I cheked that Axis2 loads the addrssing module only
once and re-uses it. Then what might be causing this?
Is this already fixed post-0.91?
- Suvanan.
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
Re: [Axis2] In searching for a place for DOM impl
Posted by Davanum Srinivas <da...@gmail.com>.
Eran,
am debating this right now. +1 to a new module. But we will have to
rip saaj code and build it on top of Ruchith's stuff.
-- dims
On 11/20/05, Eran Chinthaka <ch...@opensource.lk> wrote:
> Hi all,
>
> As you know Ruchith is doing an implementation of DOM on OM. We have a
> small problem in keeping this implementation.
>
> (ns:module= maven module)
>
> It was in the XML module for some time, but later moved to SAAJ module
> to resolve a problem with JDK 1.5. But I feel like the DOM impl do not
> belong to neither XML module nor SAAJ module.
> I think I don't need to explain why it doesn't belong to SAAJ module. If
> we put that in SAAJ, it will create a cyclic dependecy as well. And for
> XML module, I'd like to have it clean only with the current stuff. I
> think DOM impl should not come *in to* that module.
> So the option left is to have a new and separate module for DOM
> implementation. Its better to settle with something as I know Ruchith is
> having an unnecessary headache due to this.
> What do you all think ? I like to DOM impl, a separate module, so that
> people who need that can use it, whilst others can discard it.
>
> -- Chinthaka
>
>
--
Davanum Srinivas : http://wso2.com/blogs/