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 Davanum Srinivas <da...@gmail.com> on 2007/06/28 23:37:09 UTC
[Axis2] Please VOTE for your favorite bug to be fixed.
Dear Axis2 Users,
We are working hard on cleaning up the issues in JIRA. If there is a
bug you definitely want fixed in the forthcoming Axis2 1.3, please add
a comment in the specific bug. Or better still click on the VOTE
button in JIRA and indicate that you would like that bug fixed
quickly.
If you don't see a bug report, please add one and upload whatever you
can that will help with recreating the problem
(wsdl/xsd/request/response/code..). We've marked a lot of items as
blockers. But may end up deciding to downgrade them if there are
workarounds or for other reasons. So it's important to put in your 2
cents in the JIRA via VOTE's/comments.
thanks,
dims
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Amila Suriarachchi <am...@gmail.com>.
Let me put some of my thoughts about blockers and releases.
According to the current rules, we have to have zero blockers to do a
release. So sometimes what we does is downgrade some issue according to
their criticalness. I think this is not a necessity.
As I believe deciding a blocker or not is up to the user. if he do not have
any work around and if he as block due to that issue it is ok to put this as
a blocker. So another person can not change it unless he can give an valid
work around or find an problem with the issue (according to some spaces).
On the other hand as developers we have some limitations. i.e Sometimes we
may unable to fix a blocker (i.e due to technical problems etc..) So there
may be issues which are blockers but won't fix for the release.
What I am basically saying is this.
Lets say after an release (e.g .Axis2 1.2 ) we got 20 blockers and could fix
17 and 3 left.
if the last 3 going to take lot of time are we supposed to hold the release
until all are fixed? So that every one has to wait until everything fixed.
My guess is we should release with the fixed blockers and with the new
features have added to the release. But one thing. For any release we can
not have broken features. i.e. which were worked with the earlier release
but not now.
This does not mean we don't do any thing about the reaming 3 blockers. we
can time to time try to fix this with different ways.
For an example in codegen there were some problems with the xmlbeans and adb
after Axis2 1.2. I could fixed most of adb issues and add lot of new featurs
as well (some issues regarding adb-codegen, codgen, wsdl) . But could not
resolve some critical xmlbeans problems although I tried them. So if someone
suggest to stop adding new features until fix all the xmlbeans problems, I
belive that is not an efficient use of time.
And also Since at close to a release everyone concentrating on fixing
issues, if someone report issues on an RC there is high probability of being
fixed them immediately.
Finally this is what I have to say,
As developers we must try our best to resolve blockers. mean time we have to
add new features to the product as well. otherwise it won't evolve.
Thanks.
Amila.
On 7/4/07, Amila Suriarachchi <am...@gmail.com> wrote:
>
>
>
> On 7/2/07, Kelvin Lin <ke...@yahoo.com> wrote:
> >
> > I am really looking forwards to fixing this one:
> >
> > https://issues.apache.org/jira/browse/AXIS2-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> >
> > Second part of two-part message is ignored by WSDL2Java
> >
> > because in my project doing now, there is a this scenario:
> >
> > <wsdl:message name="createRequest">
> > <wsdl:part name="header" element="abc:header"/>
> > <wsdl:part name="create" element="abcthis:createRequest" />
> > </wsdl:message>
> >
> > It prevent me from using wsdl2c tool.
> >
>
>
> see my comment on this,
> this wsdl is not valid according to the WS basic profile.
> see http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16574232
> R2210
>
> if you use document literal binding you can not have more than one part
> unless you delare one
> in soap boady.
>
> *Ruchith Fernando <ru...@gmail.com>* wrote:
> >
> > Yes .... we will be releasing Rampart along with Axis2 as soon as 1.3goes out!
> >
> > Thanks,
> > Ruchith
> >
> > On 7/2/07, stlecho wrote:
> > >
> > > Is this cleaning up phase also applicable for the Rampart module or
> > only for
> > > the Axis2 framework ?
> > > In other words, can I vote for JIRA issues related to Rampart ?
> > >
> > > Regards, Stefan Lecho.
> > >
> > >
> > > dims wrote:
> > > >
> > > > Dear Axis2 Users,
> > > >
> > > > We are working hard on cleaning up the issues in JIRA.
> > > >
> > >
> > > --
> > > View this message in context:
> > http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423
> > > Sent from the Axis - User mailing list archive at Nabble.com.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > www.ruchith.org
> > www.wso2.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
> > ------------------------------
> > Boardwalk for $500? In 2007? Ha!
> > Play Monopoly Here and Now<http://us.rd.yahoo.com/evt=48223/*http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow>(it's updated for today's economy) at Yahoo! Games.
> >
> >
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
--
Amila Suriarachchi,
WSO2 Inc.
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Kelvin Lin <ke...@yahoo.com>.
Hi Amila,
Thanks a lot. I have modified my wsdl file to following the standard specification, by modifying to:
<wsdlsoap:body parts="create" use="literal" />
Thanks again.
Kelvin
Amila Suriarachchi <am...@gmail.com> wrote:
On 7/2/07, Kelvin Lin <ke...@yahoo.com> wrote: I am really looking forwards to fixing this one:
https://issues.apache.org/jira/browse/AXIS2-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
Second part of two-part message is ignored by WSDL2Java
because in my project doing now, there is a this scenario:
<wsdl:message name="createRequest">
<wsdl:part name="header" element="abc:header"/>
<wsdl:part name="create" element="abcthis:createRequest" />
</wsdl:message>
It prevent me from using wsdl2c tool.
see my comment on this,
this wsdl is not valid according to the WS basic profile.
see http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16574232 R2210
if you use document literal binding you can not have more than one part unless you delare one
in soap boady.
Ruchith Fernando <ru...@gmail.com> wrote:
Yes .... we will be releasing Rampart along with Axis2 as soon as 1.3 goes out!
Thanks,
Ruchith
On 7/2/07, stlecho wrote:
>
> Is this cleaning up phase also applicable for the Rampart module or only for
> the Axis2 framework ?
> In other words, can I vote for JIRA issues related to Rampart ?
>
> Regards, Stefan Lecho.
>
>
> dims wrote:
> >
> > Dear Axis2 Users,
> >
> > We are working hard on cleaning up the issues in JIRA.
> >
>
> --
> View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------
Boardwalk for $500? In 2007? Ha!
Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
--
Amila Suriarachchi,
WSO2 Inc.
---------------------------------
Get the free Yahoo! toolbar and rest assured with the added security of spyware protection.
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Amila Suriarachchi <am...@gmail.com>.
On 7/2/07, Kelvin Lin <ke...@yahoo.com> wrote:
>
> I am really looking forwards to fixing this one:
>
>
> https://issues.apache.org/jira/browse/AXIS2-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>
> Second part of two-part message is ignored by WSDL2Java
>
> because in my project doing now, there is a this scenario:
>
> <wsdl:message name="createRequest">
> <wsdl:part name="header" element="abc:header"/>
> <wsdl:part name="create" element="abcthis:createRequest" />
> </wsdl:message>
>
> It prevent me from using wsdl2c tool.
>
see my comment on this,
this wsdl is not valid according to the WS basic profile.
see
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16574232R2210
if you use document literal binding you can not have more than one part
unless you delare one
in soap boady.
*Ruchith Fernando <ru...@gmail.com>* wrote:
>
> Yes .... we will be releasing Rampart along with Axis2 as soon as 1.3 goes
> out!
>
> Thanks,
> Ruchith
>
> On 7/2/07, stlecho wrote:
> >
> > Is this cleaning up phase also applicable for the Rampart module or only
> for
> > the Axis2 framework ?
> > In other words, can I vote for JIRA issues related to Rampart ?
> >
> > Regards, Stefan Lecho.
> >
> >
> > dims wrote:
> > >
> > > Dear Axis2 Users,
> > >
> > > We are working hard on cleaning up the issues in JIRA.
> > >
> >
> > --
> > View this message in context:
> http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423
> > Sent from the Axis - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> www.ruchith.org
> www.wso2.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
> ------------------------------
> Boardwalk for $500? In 2007? Ha!
> Play Monopoly Here and Now<http://us.rd.yahoo.com/evt=48223/*http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow>(it's updated for today's economy) at Yahoo! Games.
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Kelvin Lin <ke...@yahoo.com>.
I am really looking forwards to fixing this one:
https://issues.apache.org/jira/browse/AXIS2-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
Second part of two-part message is ignored by WSDL2Java
because in my project doing now, there is a this scenario:
<wsdl:message name="createRequest">
<wsdl:part name="header" element="abc:header"/>
<wsdl:part name="create" element="abcthis:createRequest" />
</wsdl:message>
It prevent me from using wsdl2c tool.
Ruchith Fernando <ru...@gmail.com> wrote:
Yes .... we will be releasing Rampart along with Axis2 as soon as 1.3 goes out!
Thanks,
Ruchith
On 7/2/07, stlecho wrote:
>
> Is this cleaning up phase also applicable for the Rampart module or only for
> the Axis2 framework ?
> In other words, can I vote for JIRA issues related to Rampart ?
>
> Regards, Stefan Lecho.
>
>
> dims wrote:
> >
> > Dear Axis2 Users,
> >
> > We are working hard on cleaning up the issues in JIRA.
> >
>
> --
> View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------
Boardwalk for $500? In 2007? Ha!
Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Ruchith Fernando <ru...@gmail.com>.
Yes .... we will be releasing Rampart along with Axis2 as soon as 1.3 goes out!
Thanks,
Ruchith
On 7/2/07, stlecho <st...@gmail.com> wrote:
>
> Is this cleaning up phase also applicable for the Rampart module or only for
> the Axis2 framework ?
> In other words, can I vote for JIRA issues related to Rampart ?
>
> Regards, Stefan Lecho.
>
>
> dims wrote:
> >
> > Dear Axis2 Users,
> >
> > We are working hard on cleaning up the issues in JIRA.
> >
>
> --
> View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Davanum Srinivas <da...@gmail.com>.
yes!
On 7/2/07, stlecho <st...@gmail.com> wrote:
>
> Is this cleaning up phase also applicable for the Rampart module or only for
> the Axis2 framework ?
> In other words, can I vote for JIRA issues related to Rampart ?
>
> Regards, Stefan Lecho.
>
>
> dims wrote:
> >
> > Dear Axis2 Users,
> >
> > We are working hard on cleaning up the issues in JIRA.
> >
>
> --
> View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by stlecho <st...@gmail.com>.
Is this cleaning up phase also applicable for the Rampart module or only for
the Axis2 framework ?
In other words, can I vote for JIRA issues related to Rampart ?
Regards, Stefan Lecho.
dims wrote:
>
> Dear Axis2 Users,
>
> We are working hard on cleaning up the issues in JIRA.
>
--
View this message in context: http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Davanum Srinivas <da...@gmail.com>.
Michele,
We did not under the value of the "Fix Version" and we just kept
marking stuff as blockers. if you see my prev email, there are 2
buckets. first bucket is a blocker which mean stuff is totally broken
with no work around. 2nd is let's try to fix this for 1.3 bucket..
-- dims
On 6/29/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> Dims,
>
> what about postponing the 1.3 release and fixing (at least) all the
> blockers? ;)
>
>
> Michele
>
> On Thu, 2007-06-28 at 17:37 -0400, Davanum Srinivas wrote:
> > Dear Axis2 Users,
> >
> > We are working hard on cleaning up the issues in JIRA. If there is a
> > bug you definitely want fixed in the forthcoming Axis2 1.3, please add
> > a comment in the specific bug. Or better still click on the VOTE
> > button in JIRA and indicate that you would like that bug fixed
> > quickly.
> >
> > If you don't see a bug report, please add one and upload whatever you
> > can that will help with recreating the problem
> > (wsdl/xsd/request/response/code..). We've marked a lot of items as
> > blockers. But may end up deciding to downgrade them if there are
> > workarounds or for other reasons. So it's important to put in your 2
> > cents in the JIRA via VOTE's/comments.
> >
> > thanks,
> > dims
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sorry for hijacking this thread.
Can we please also remove the documentation links for our older releases
from the left tool bar of the site. For me it is irritating to see 0.94
documentation still in Axis2 main page.
Can we please move it to some other place?
Deepal Jayasinghe wrote:
> Hi robert,
>
> good point , I will update the site with the RC this time.
>
> Thanks
> Deepal
>> Lack of getting the RC's being used by end users has I think been one
>> of the main causes for instability. I'd really like to try something
>> new this time around that might get more users using them.
>>
>> I'm all for "Release early and often" - in fact arguably we don't do
>> enough point releases. I realize though that there are lots of deps
>> and its hard to coordinate all the releases.
>>
>> Anyways, IIRC the RC's never got put on the download page. The only
>> announcement is to the list. Other projects have better usage of their
>> RC's and I think it'd be worth exploring what could be done
>> differently to get more RC usage of axis2.
>>
>> I've noticed xmlbeans, for example, has been broken on every release
>> so far. And while I tested svn in the middle of dev, I never did test
>> the RC's so I accept part of the blame. This time around I plan on
>> testing xmlbeans on some of my complex schemas, and the other things I
>> personally use like spring and the soapmonitor.
>>
>> Michele, from what I've seen you're had some of the most advanced use
>> cases of axis2. If you could do some RC testing with some of your use
>> cases I'd think that'd go a long way to making 1.3 the most stable yet.
>>
>> No one uses 100% of axis2, but I'd think that if we got more people
>> using the RC's on _their_ code, it'd help plenty.
>>
>> Robert
>>
>> On 7/2/07, * Davanum Srinivas* <davanum@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> no it doesnt. this is a classic chicken and egg issue. thats why we
>> make so many RC's but still end users dont play enough with RC's as
>> much as we'd like them to :)
>>
>> thx,
>> dims
>>
>> On 7/2/07, Michele Mazzucco < Michele.Mazzucco@ncl.ac.uk
>> <ma...@ncl.ac.uk>> wrote:
>> > Eran,
>> >
>> > On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
>> > > I do agree with you that we need a reliable Axis2, but that
>> doesn't
>> > > mean
>> > > we need to keep on postponing releases "until" we fix everything.
>> >
>> >
>> > there was no insult in my comments. My point, instead, is that
>> if you
>> > want new features you can download the last nightly build. If
>> you want
>> > something which works *properly* you download a release. Does it
>> make
>> > sense to release a new version and then ask to people to
>> download the
>> > next nightly build because the release is "broken"?
>> >
>> >
>> > Michele
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> <ma...@ws.apache.org>
>> >
>> >
>>
>>
>> --
>> Davanum Srinivas :: http://davanum.wordpress.com
>> <http://davanum.wordpress.com>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGjF/TjON2uBzUhh8RAgUdAKCrmwNQ3dUTzlYHVDXTjFUXwheWqQCgmFfk
RfjfwueVngzd2898nHoFits=
=RRmr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi robert,
good point , I will update the site with the RC this time.
Thanks
Deepal
> Lack of getting the RC's being used by end users has I think been one
> of the main causes for instability. I'd really like to try something
> new this time around that might get more users using them.
>
> I'm all for "Release early and often" - in fact arguably we don't do
> enough point releases. I realize though that there are lots of deps
> and its hard to coordinate all the releases.
>
> Anyways, IIRC the RC's never got put on the download page. The only
> announcement is to the list. Other projects have better usage of their
> RC's and I think it'd be worth exploring what could be done
> differently to get more RC usage of axis2.
>
> I've noticed xmlbeans, for example, has been broken on every release
> so far. And while I tested svn in the middle of dev, I never did test
> the RC's so I accept part of the blame. This time around I plan on
> testing xmlbeans on some of my complex schemas, and the other things I
> personally use like spring and the soapmonitor.
>
> Michele, from what I've seen you're had some of the most advanced use
> cases of axis2. If you could do some RC testing with some of your use
> cases I'd think that'd go a long way to making 1.3 the most stable yet.
>
> No one uses 100% of axis2, but I'd think that if we got more people
> using the RC's on _their_ code, it'd help plenty.
>
> Robert
>
> On 7/2/07, * Davanum Srinivas* <davanum@gmail.com
> <ma...@gmail.com>> wrote:
>
> no it doesnt. this is a classic chicken and egg issue. thats why we
> make so many RC's but still end users dont play enough with RC's as
> much as we'd like them to :)
>
> thx,
> dims
>
> On 7/2/07, Michele Mazzucco < Michele.Mazzucco@ncl.ac.uk
> <ma...@ncl.ac.uk>> wrote:
> > Eran,
> >
> > On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
> > > I do agree with you that we need a reliable Axis2, but that
> doesn't
> > > mean
> > > we need to keep on postponing releases "until" we fix everything.
> >
> >
> > there was no insult in my comments. My point, instead, is that
> if you
> > want new features you can download the last nightly build. If
> you want
> > something which works *properly* you download a release. Does it
> make
> > sense to release a new version and then ask to people to
> download the
> > next nightly build because the release is "broken"?
> >
> >
> > Michele
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
> <http://davanum.wordpress.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by robert lazarski <ro...@gmail.com>.
Lack of getting the RC's being used by end users has I think been one of the
main causes for instability. I'd really like to try something new this time
around that might get more users using them.
I'm all for "Release early and often" - in fact arguably we don't do enough
point releases. I realize though that there are lots of deps and its hard to
coordinate all the releases.
Anyways, IIRC the RC's never got put on the download page. The only
announcement is to the list. Other projects have better usage of their RC's
and I think it'd be worth exploring what could be done differently to get
more RC usage of axis2.
I've noticed xmlbeans, for example, has been broken on every release so far.
And while I tested svn in the middle of dev, I never did test the RC's so I
accept part of the blame. This time around I plan on testing xmlbeans on
some of my complex schemas, and the other things I personally use like
spring and the soapmonitor.
Michele, from what I've seen you're had some of the most advanced use cases
of axis2. If you could do some RC testing with some of your use cases I'd
think that'd go a long way to making 1.3 the most stable yet.
No one uses 100% of axis2, but I'd think that if we got more people using
the RC's on _their_ code, it'd help plenty.
Robert
On 7/2/07, Davanum Srinivas <da...@gmail.com> wrote:
>
> no it doesnt. this is a classic chicken and egg issue. thats why we
> make so many RC's but still end users dont play enough with RC's as
> much as we'd like them to :)
>
> thx,
> dims
>
> On 7/2/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> > Eran,
> >
> > On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
> > > I do agree with you that we need a reliable Axis2, but that doesn't
> > > mean
> > > we need to keep on postponing releases "until" we fix everything.
> >
> >
> > there was no insult in my comments. My point, instead, is that if you
> > want new features you can download the last nightly build. If you want
> > something which works *properly* you download a release. Does it make
> > sense to release a new version and then ask to people to download the
> > next nightly build because the release is "broken"?
> >
> >
> > Michele
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Davanum Srinivas <da...@gmail.com>.
no it doesnt. this is a classic chicken and egg issue. thats why we
make so many RC's but still end users dont play enough with RC's as
much as we'd like them to :)
thx,
dims
On 7/2/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> Eran,
>
> On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
> > I do agree with you that we need a reliable Axis2, but that doesn't
> > mean
> > we need to keep on postponing releases "until" we fix everything.
>
>
> there was no insult in my comments. My point, instead, is that if you
> want new features you can download the last nightly build. If you want
> something which works *properly* you download a release. Does it make
> sense to release a new version and then ask to people to download the
> next nightly build because the release is "broken"?
>
>
> Michele
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Eran,
On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
> I do agree with you that we need a reliable Axis2, but that doesn't
> mean
> we need to keep on postponing releases "until" we fix everything.
there was no insult in my comments. My point, instead, is that if you
want new features you can download the last nightly build. If you want
something which works *properly* you download a release. Does it make
sense to release a new version and then ask to people to download the
next nightly build because the release is "broken"?
Michele
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michele Mazzucco wrote:
> Eran,
>
> your point is "let's add new, cool features", my point is "let's build
> something reliable".
I think you didn't get my point. " ..there are significant improvements
over the last release .." doesn't mean they are not only new cool
features. Fault handling was not working properly in the last release
and we fixed it. If you really looked at what we did during the
hackathon then you know how we improved it and how significant was it.
That is what I meant.
I am sorry if my interpretation of "significant improvements" is wrong
coz I know and agree my English is not that good :)
I do agree with you that we need a reliable Axis2, but that doesn't mean
we need to keep on postponing releases "until" we fix everything.
Ok, let's say we postpone the release. How can you help fixing some
blockers to make it more reliable? What is the plan you have? Just
asking to postpone thinking "some one" will fix blockers and "some day"
we will get a more stable one is nothing more than following a mirage
for me.
Thanks,
Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGiCoCjON2uBzUhh8RAgg2AJ9nuKj1XGyTL95b6r/RT9RvK7eaNgCgmuxL
+ZibYf5NirmRu0x5uIlw18c=
=cqzr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Davanum Srinivas <da...@gmail.com>.
Michele,
from prev experience it takes us at least 2-3 RC's and then final.
There is no way we can get thru all that in a couple of days. do you?
:)
-- dims
On 7/1/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> Dims,
>
> I disagree with what Eran says, which is "we have a deadline, so
> probably not all bugs will be fixed for the next release". I think
> people would be much more happy to wait 1 or 2 weeks more to have a
> more reliable release than having an unstable one now. Simply
> lowering bug priorities from blockers to critical (or other) doesn't
> mean the tool is bug free (this is what I understand from previous
> emails). And, of course, adding new features will probably mean
> adding new bugs as well.
>
>
> Michele
>
> On 1 Jul 2007, at 13:09, Davanum Srinivas wrote:
>
> > Michele,
> >
> > Why do you think that? Blockers are Blockers for the release. If the
> > blockers are not addressed, there will not be a release. Isn't that
> > why i sent this email about voting for your bug and adding comments to
> > make stuff blockers?
> >
> > What am i missing here?
> >
> > thanks,
> > dims
> >
> > On 7/1/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> >> Eran,
> >>
> >> your point is "let's add new, cool features", my point is "let's
> >> build something reliable". I think if you want to use a tool in a
> >> production environment the second point is much more important.
> >>
> >>
> >> Michele
> >>
> >> On 1 Jul 2007, at 04:53, Eran Chinthaka wrote:
> >>
> >> > -----BEGIN PGP SIGNED MESSAGE-----
> >> > Hash: SHA1
> >> >
> >> > Michele Mazzucco wrote:
> >> >> Dims,
> >> >>
> >> >> what about postponing the 1.3 release and fixing (at least) all
> >> the
> >> >> blockers? ;)
> >> >
> >> > Michele,
> >> >
> >> > I do not see a point in that. If we have a deadline then
> >> everyone is
> >> > encouraged to work. If just postpone then we will lose the
> >> > momentum. And
> >> > also of there are significant improvements over the last release
> >> > then it
> >> > is the best to think about a release. I think what we need is to
> >> set
> >> > realistic goals with deadlines which is what Dims had done.
> >> >
> >> > Chinthaka
> >> > -----BEGIN PGP SIGNATURE-----
> >> > Version: GnuPG v1.4.3 (GNU/Linux)
> >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >> >
> >> > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
> >> > NT3qeHhTTHvqsM0uzVuo5Xo=
> >> > =QTbK
> >> > -----END PGP SIGNATURE-----
> >> >
> >> >
> >> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas :: http://davanum.wordpress.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Dims,
I disagree with what Eran says, which is "we have a deadline, so
probably not all bugs will be fixed for the next release". I think
people would be much more happy to wait 1 or 2 weeks more to have a
more reliable release than having an unstable one now. Simply
lowering bug priorities from blockers to critical (or other) doesn't
mean the tool is bug free (this is what I understand from previous
emails). And, of course, adding new features will probably mean
adding new bugs as well.
Michele
On 1 Jul 2007, at 13:09, Davanum Srinivas wrote:
> Michele,
>
> Why do you think that? Blockers are Blockers for the release. If the
> blockers are not addressed, there will not be a release. Isn't that
> why i sent this email about voting for your bug and adding comments to
> make stuff blockers?
>
> What am i missing here?
>
> thanks,
> dims
>
> On 7/1/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
>> Eran,
>>
>> your point is "let's add new, cool features", my point is "let's
>> build something reliable". I think if you want to use a tool in a
>> production environment the second point is much more important.
>>
>>
>> Michele
>>
>> On 1 Jul 2007, at 04:53, Eran Chinthaka wrote:
>>
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > Michele Mazzucco wrote:
>> >> Dims,
>> >>
>> >> what about postponing the 1.3 release and fixing (at least) all
>> the
>> >> blockers? ;)
>> >
>> > Michele,
>> >
>> > I do not see a point in that. If we have a deadline then
>> everyone is
>> > encouraged to work. If just postpone then we will lose the
>> > momentum. And
>> > also of there are significant improvements over the last release
>> > then it
>> > is the best to think about a release. I think what we need is to
>> set
>> > realistic goals with deadlines which is what Dims had done.
>> >
>> > Chinthaka
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v1.4.3 (GNU/Linux)
>> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>> >
>> > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
>> > NT3qeHhTTHvqsM0uzVuo5Xo=
>> > =QTbK
>> > -----END PGP SIGNATURE-----
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Davanum Srinivas <da...@gmail.com>.
Michele,
Why do you think that? Blockers are Blockers for the release. If the
blockers are not addressed, there will not be a release. Isn't that
why i sent this email about voting for your bug and adding comments to
make stuff blockers?
What am i missing here?
thanks,
dims
On 7/1/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> Eran,
>
> your point is "let's add new, cool features", my point is "let's
> build something reliable". I think if you want to use a tool in a
> production environment the second point is much more important.
>
>
> Michele
>
> On 1 Jul 2007, at 04:53, Eran Chinthaka wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Michele Mazzucco wrote:
> >> Dims,
> >>
> >> what about postponing the 1.3 release and fixing (at least) all the
> >> blockers? ;)
> >
> > Michele,
> >
> > I do not see a point in that. If we have a deadline then everyone is
> > encouraged to work. If just postpone then we will lose the
> > momentum. And
> > also of there are significant improvements over the last release
> > then it
> > is the best to think about a release. I think what we need is to set
> > realistic goals with deadlines which is what Dims had done.
> >
> > Chinthaka
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.3 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
> > NT3qeHhTTHvqsM0uzVuo5Xo=
> > =QTbK
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Eran,
your point is "let's add new, cool features", my point is "let's
build something reliable". I think if you want to use a tool in a
production environment the second point is much more important.
Michele
On 1 Jul 2007, at 04:53, Eran Chinthaka wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Michele Mazzucco wrote:
>> Dims,
>>
>> what about postponing the 1.3 release and fixing (at least) all the
>> blockers? ;)
>
> Michele,
>
> I do not see a point in that. If we have a deadline then everyone is
> encouraged to work. If just postpone then we will lose the
> momentum. And
> also of there are significant improvements over the last release
> then it
> is the best to think about a release. I think what we need is to set
> realistic goals with deadlines which is what Dims had done.
>
> Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
> NT3qeHhTTHvqsM0uzVuo5Xo=
> =QTbK
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michele Mazzucco wrote:
> Dims,
>
> what about postponing the 1.3 release and fixing (at least) all the
> blockers? ;)
Michele,
I do not see a point in that. If we have a deadline then everyone is
encouraged to work. If just postpone then we will lose the momentum. And
also of there are significant improvements over the last release then it
is the best to think about a release. I think what we need is to set
realistic goals with deadlines which is what Dims had done.
Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
NT3qeHhTTHvqsM0uzVuo5Xo=
=QTbK
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Dims,
what about postponing the 1.3 release and fixing (at least) all the
blockers? ;)
Michele
On Thu, 2007-06-28 at 17:37 -0400, Davanum Srinivas wrote:
> Dear Axis2 Users,
>
> We are working hard on cleaning up the issues in JIRA. If there is a
> bug you definitely want fixed in the forthcoming Axis2 1.3, please add
> a comment in the specific bug. Or better still click on the VOTE
> button in JIRA and indicate that you would like that bug fixed
> quickly.
>
> If you don't see a bug report, please add one and upload whatever you
> can that will help with recreating the problem
> (wsdl/xsd/request/response/code..). We've marked a lot of items as
> blockers. But may end up deciding to downgrade them if there are
> workarounds or for other reasons. So it's important to put in your 2
> cents in the JIRA via VOTE's/comments.
>
> thanks,
> dims
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org