axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <samisa_abeysin...@yahoo.com>
Subject RE: Re:[bug fix progress] Why are we releasing?
Date Wed, 13 Oct 2004 06:37:49 GMT
> WRT AXISCPP-184.... This is something fairly basic that I'd like to see fixed, as it'll
be a
> show stopper for BT.

Done.

Samisa...

--- adrian.p.smith@bt.com wrote:

> I can do some tests for you, but only on a full build as I do not have a build environment.
> 
> WRT AXISCPP-184.... This is something fairly basic that I'd like to see fixed, as it'll
be a
> show stopper for BT.
> 
> Regards,
> 
> Adrian Smith
> BT Group
> 
> -----Original Message-----
> From: Mark Whitlock [mailto:mark_whitlock@uk.ibm.com]
> Sent: 12 October 2004 16:53
> To: axis-c-dev@ws.apache.org
> Cc: axis-c-user@ws.apache.org
> Subject: Fw: Re:[bug fix progress] Why are we releasing?
> 
> 
> 
> 
> 
> 
> Hi,
> Some status on the problems I've been working on and I'm interested in....
> 
> AXISCPP-192 "checkMessage picking up wrong node" - I've returned this as a
> user error
> AXISCPP-193 "Bad characters in complex type when set to null" - I've fixed
> this and would like Adrian P Smith to test it to verify my fix
> AXISCPP-181 "Entry/exit trace performance bad with trace off" - I've fixed
> this
> (No JIRA raised) "Axis2Transport fails on windows" - I've fixed this
> (Axis2Transport::getHTTPHeaders() contains the fix)
> AXISCPP-194 "Inconsistent deserialization error reporting in generated
> code" - Not critical for 1.3 so I'm not working on it unless someone asks
> AXISCPP-184 "Cannot handle '<' and '>' characters in deserializing a
> returned string" - Not critical for 1.3 so I'm not working on it unless
> someone asks
> 
> So I've fixed all the problems that were outstanding against me for 1.3.
> Mark
> Mark Whitlock
> IBM
> 
> ----- Forwarded by Mark Whitlock/UK/IBM on 12/10/2004 16:39 -----
>                                                                            
>              Samisa Abeysinghe                                             
>              <samisa_abeysingh                                             
>              e@yahoo.com>                                               To 
>                                        Apache AXIS C Developers List       
>              12/10/2004 11:39          <axis-c-dev@ws.apache.org>          
>                                                                         cc 
>                                        axis-c-user@ws.apache.org           
>              Please respond to                                     Subject 
>               "Apache AXIS C           Re: [bug fix progress] Why are we   
>              Developers List"          releasing?                          
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
> 
> 
> 
> 
> I managed to solve AXISCPP-96.
> 
> I also closed out few more including 198
> 
> Are there any others that we need to look into (apart from AXISCPP-103 (and
> 89), 192 and 193 which
> are being attended by Sanjaya and Mark) before 1.3 release.
> 
> Samisa...
> 
> 
> --- Samisa Abeysinghe <samisa_abeysinghe@yahoo.com> wrote:
> 
> > Hi All,
> >    We have made good progress with bug fixes.
> >
> >    Today I have closed out:
> >  AXISCPP-95
> >  AXISCPP-94
> >  AXISCPP-64
> >  AXISCPP-57
> >  AXISCPP-65
> >
> >    Accoering to Sanjaya
> >  AXISCPP-103 (and 89)
> >    seems to be OK with new transport.
> >
> >    And we have
> >  AXISCPP-96
> >    pending.
> >
> > Samisa...
> >
> > --- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:
> >
> > >
> > >
> > >
> > >
> > > AXISCPP-103
> > > AXISCPP-96
> > > AXISCPP-95
> > > AXISCPP-94
> > > AXISCPP-64
> > > AXISCPP-57
> > > AXISCPP-65
> > >
> > >
> > > I would agree with most of them but not 65. This may well be fixed
> already
> > > with some of Fred's recent changes and it's not a sev one - just very
> > > annoying !
> > >
> > > OK, if that's decided then I suggest that we make sure that if you are
> > > working on a JIRA problem then you allocate the problem to yourself in
> JIRA
> > > PRIOR to actually finding a fix i.e. make sure everyone knows not to
> waste
> > > their time trying to fix it because you are already working on it.
> > >
> > > I'm offline for a few days (sorry - bad timing!)
> > >
> > >
> > >
> > > John Hawkins
> > >
> > >
> > >
> > >
> > >
> 
> > >              Samisa Abeysinghe
> 
> > >              <samisa_abeysingh
> 
> > >              e@yahoo.com>
> To
> > >                                        Apache AXIS C Developers List
> 
> > >              07/10/2004 14:35          <axis-c-dev@ws.apache.org>
> 
> > >
> cc
> > >
> 
> > >              Please respond to
> Subject
> > >               "Apache AXIS C           Re: Why are we releasing?
> 
> > >              Developers List"
> 
> > >
> 
> > >
> 
> > >
> 
> > >
> 
> > >
> 
> > >
> > >
> > >
> > >
> > > > Any others that we need to prioritise for 1.3?
> > >
> > > The following are worth looking at and fixing:
> > >
> > > AXISCPP-103
> > > AXISCPP-96
> > > AXISCPP-95
> > > AXISCPP-94
> > > AXISCPP-64
> > > AXISCPP-57
> > > AXISCPP-65
> > >
> > > I could look at transport and non-Windows stuff in the given order.
> > >
> > > I need help looking at Windows specific stuff. (because I have a Linux
> > > desktop)
> > >
> > > Samisa...
> > >
> > > --- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:
> > >
> > > >
> > > >
> > > >
> > > >
> > > > OK, well, if there are no dissenters then I think we can say that 1.3
> is
> > > > using the new transport.
> > > > In which case you have no need to tackle the two major defects you
> were
> 
=== message truncated ===



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

Mime
View raw message