I'd like to get this one fixed for 1.2.1, too:
https://issues.apache.org/jira/browse/AXIS2-2669
Can anyone give a target date for the 1.2.1 release? I'm planning to
have this fixed within two days, but want to make sure I don't miss the
release window.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com -
http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Thilina Gunarathne wrote:
> +1 for the 1.2.1 ..
> It would be great if AXIS2-2663-"Class loading issues when the
> libraries are placed in the service archive" can be fixed in the
> 1.2.1..
>
> Thanks,
> Thilina
>
>
> On 5/14/07, Deepal Jayasinghe <
deepal@open...> wrote:
>> Hi Sathija ,
>> I will make them as blockers for next release so that we will fix them
>> b4 1.2.1
>>
>> Thanks
>> Deepal
>>
>> > <!-- DIV {margin:0px;} -->
>> > Would also be great if the updated patch that addresses bugs 2055 and
>> 1899 was applied in the 1.2.1 release.
>> > Provides support for POJO inheritence.
>> >
>> > - Sathija.
>> >
>> >
>> > ----- Original Message ----
>> > From: Davanum Srinivas <
davanum@gmai...>
>> > To:
axis-dev@ws.a...
>> > Sent: Saturday, May 12, 2007 1:56:03 AM
>> > Subject: Re: [Axis2] What's next - 1.2.1 or 1.3?
>> >
>> > No new features :) Only critical bugs should be addressed in 1.2.1 the
>> > CLOSE_WAIT problem was very serious and made multi threaded
>> > ServiceClient async calls totally unusable.
>> >
>> > -- dims
>> >
>> > On 5/12/07, Eran Chinthaka <
chinthaka@open...> wrote:
>> > I added a new property for Option to allow the user to give a custom
>> > socket factory, while working with https. If this can also go in to
>> the
>> > release it would be great. But if this makes the list longer you can
>> > forget it.
>> >
>> > Thanks,
>> > Chinthaka
>> >
>> > Davanum Srinivas wrote:
>> > > Folks,
>> >
>> > > Can we make a case for a 1.2.1? (Real soon?) I guess we should
>> cut it
>> > > from the 1.2 branch. It should have absolutely minimal changes from
>> > > 1.2. For example the unwrapping changes for ADB that Amila
>> checked in
>> > > today comes to mind. If Michele confirms the fix for the
>> > > AUTO_RELEASE_CONNECTION related changes that can be ported as well.
>> > > What else do we absolutely need to fix? If the list grows too
>> long, it
>> > > may be better to just stick to trunk and do a 1.3 very soon (but not
>> > > as fast as we can cut 1.2.1). Anyways, what do you all think? Are
>> > > there changes needed by Rampart and/or Sandesha and/or Synapse
>> and/or
>> > > Tuscany etc that dictate that we should do a quick 1.2.1? WDYT?
>> >
>> > > thanks,
>> > > dims
>> >
>> >
>> > >
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
axis-dev-unsubscribe@ws.a...
>> For additional commands, e-mail:
axis-dev-help@ws.a...
>> > >
>> > >
>>
>> > --
>> > Davanum Srinivas ::
http://davanum.wordpress.com
>>
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
axis-dev-unsubscribe@ws.a...
>> > For additional commands, e-mail:
axis-dev-help@ws.a...
>>
>>
>>
>> > -------------------------
>> > Be a better Globetrotter. Get better travel answers
>> <
http://us.rd.yahoo.com/evt=48254/*
http://answers.yahoo.com/dir/_ylc=X3oDMTI5MGx2aThyBF9TAzIxMTU1MDAzNTIEX3MDMzk2NTQ1MTAzBHNlYwNCQUJwaWxsYXJfTklfMzYwBHNsawNQcm9kdWN0X3F1ZXN0aW9uX3BhZ2U-?link=list&sid=396545469>from
>>
>> someone who knows.
>> > Yahoo! Answers - Check it out.
>>
>> --
>> Thanks,
>> Deepal
>> ................................................................
>> "The highest tower is built one brick at a time"
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
axis-dev-unsubscribe@ws.a...
>> For additional commands, e-mail:
axis-dev-help@ws.a...
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
axis-dev-unsubscribe@ws.a...
For additional commands, e-mail:
axis-dev-help@ws.a...
opensubscriber is not affiliated with the authors of this message nor responsible for its content.