Doh! Sorry. Well at least I figured out what happens when one reports a
bug...

Thanks to all who helped...

Any ideas when the new release might be available?

Geoff

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf Of 
> Magnus Rydin
> Sent: Wednesday, 16 January, 2002 8:26 PM
> To: Orion-Interest
> Subject: SV: IronFlare bug fixing policy
> 
> 
> Hi Geoff,
> 
> your bug report 695 seems to be a copy of bug 670 which has 
> already been fixed (not released though).
> 
> WR
> Magnus Rydin
> 
> > -----Ursprungligt meddelande-----
> > Från: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]För Geoff Soutter
> > Skickat: den 16 januari 2002 07:06
> > Till: Orion-Interest
> > Kopia: Orion Interest List
> > Ämne: RE: IronFlare bug fixing policy
> >
> >
> > Hi there EW,
> >
> > Thanks for the response.
> >
> > The one I've reported (so far) is 695 
> > (http://bugzilla.orionserver.com/bugzilla/show_bug.cgi?id=695).
> >
> > It doesn't include an .ear file or anything, but it seems to be it 
> > would be pretty trivial to track it down _if you had access to the 
> > source code_ - since I included the buggy portion of the generated 
> > wrapper it's clear to see where the bug is.
> >
> > In fact, I just did a search on the class files and I found 
> the likely 
> > location of the bug. It's probably in _ql.class, since it's 
> the only 
> > class which contains "response.iterator()" and it's this 
> line which is 
> > throwing the NullPointerException. Grrr - closed source 
> things annoy 
> > me!!
> >
> > So, seems like you're saying theres not much propect of bugs being 
> > fixed till the refactoring is over? Did they mention when this is 
> > likely to be? RSN I suppose :-)
> >
> > Cheers,
> >
> > Geoff
> >
> > BTW, seems like bugzilla is down at the moment?
> >
> > > -----Original Message-----
> > > From: The elephantwalker [mailto:[EMAIL PROTECTED]]
> > > Sent: Wednesday, 16 January, 2002 4:03 PM
> > > To: Orion-Interest; [EMAIL PROTECTED]
> > > Subject: RE: IronFlare bug fixing policy
> > >
> > >
> > > Geoff,
> > >
> > > Magnus Rydin told me that what they need are good 
> examples for each 
> > > bug so that they are absolutely reproducible. If you look 
> at some of 
> > > the bugs that are still open, these bugs don't have iron clad 
> > > examples that are reproducible.
> > >
> > > So each of these bugs needs to be cleared...which means Magnus R. 
> > > has to work on reproducing them (if they aren't immediately 
> > > reproducible), which of course takes time.
> > >
> > > What he didn't say but reported on the list is a major 
> refactoring 
> > > going on now in Orion to bring it into compliance with j2ee 1.3. 
> > > This includes EJB 2.0, Servlet 2.3 (not just the draft), and JSP 
> > > 1.2, Connections, etc.
> > >
> > > As we all know, fixing bugs which are going to disappear in a 
> > > refactoring is a bit of a waste of time. Of course, if its a bug 
> > > that affects you directly, you may feel differently.
> > >
> > > Which bug numbers did you report?
> > >
> > > regards,
> > >
> > > the elephantwalker
> > > www.elephantwalker.com
> > >
> > >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Geoff 
> > > Soutter
> > > Sent: Tuesday, January 15, 2002 4:55 PM
> > > To: Orion-Interest
> > > Subject: IronFlare bug fixing policy
> > >
> > >
> > > Hi there,
> > >
> > > I reported a bug on BugZilla a few days back. It's reasonably 
> > > serious - basically the generated wrapper for the finder 
> method of 
> > > an EJB is throwing NullPointerException when the EJB throws an 
> > > exception, hiding the real cause of the problem. (And I 
> just found 
> > > another bug - ServletExceptions constructed with (string, 
> exception) 
> > > are reported without the String originally passed.)
> > >
> > > I haven't heard anything and the bug has not been touched 
> > > apparently.
> > >
> > > Does anyone know what IronFlare's policy is regards 
> fixing bugs? Do 
> > > they tend to fix them quickly, or are they likely to just 
> ignore bug 
> > > reports?
> > >
> > >
> > > The reason I ask is that I'm happy to use something without much 
> > > support, but if they refuse to fix bugs then I think I'll have to 
> > > give up and try elsewhere...
> > >
> > > Cheers
> > >
> > > Geoff
> > >
> > >
> >
> 
> 


Reply via email to