Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
Yep, I agree with Joe. Also, make sure to update the JAXB API and the implementation. Also, we should run full TCK to make sure everything is still ok (or to determine what needs to be fixed). Jarek On Thu, Apr 10, 2008 at 10:43 AM, Joe Bohn <[EMAIL PROTECTED]> wrote: > Vasily Zakharov wrote: > > > Kevan, > > > > Do you mean we could switch the trunk to jaxb-impl 2.1.6 right now? > > > > I could prepare a patch and put it to GERONIMO-3951. > > > > Vasily > > > > IMO it would be a good idea to understand the current state of the tck in > trunk prior to attempting this so that we understand which issues are linked > to this change and which are not. > > Joe > > > > > > > > > > > On Fri, Apr 4, 2008 at 8:35 PM, Kevan Miller <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > > On Apr 4, 2008, at 1:13 PM, Vasily Zakharov wrote: > > > Hi, all, > > > > > > I see Geronimo still uses jaxb-impl version 2.0.5, while 2.1.6 is the > > > latest stable release. > > > Is there any particular reason for that? > > > What do you people think about switching to 2.1.x? > > > > > > I was recently investigating a nasty intermittent failure of > > > org.apache.geronimo.cxf.CXFHandlerResolverTest test on Harmony > > > (HARMONY-5625) and it seems the problem is in JAXB implementation. The > > > problem occurs on jaxb-impl-2.1.3 and earlier and doesn't occur on > > > jaxb-impl-2.1.4 and later. I suspect JAXB issue 383 [1] is the cause. > > > > > > In other words, bugs in jaxb-impl 2.0.5 are affecting Geronimo > > > operation, at least on Harmony, and that looks like a reason for > > > switching to a newer release. > > > > > > Vasily > > > > > > [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=383 > > > > > > Hi Vasily, > > > Thanks for the info. JAXB 2.1 presents Java EE 5 TCK issues for us. > We're > > > working to learn from Sun how to pass the TCK w/ JAXB/JAXWS 2.1. Not > > > something that i'd anticipate for a near-term, 2.0/2.1 release. However, > > > don't see why we shouldn't start exploring this on our dev trunk (e.g. > > > 2.2-SNAPSHOT). > > > > > > --kevan > > > > > > > > > > > > > > >
Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
Vasily Zakharov wrote: Kevan, Do you mean we could switch the trunk to jaxb-impl 2.1.6 right now? I could prepare a patch and put it to GERONIMO-3951. Vasily IMO it would be a good idea to understand the current state of the tck in trunk prior to attempting this so that we understand which issues are linked to this change and which are not. Joe On Fri, Apr 4, 2008 at 8:35 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: On Apr 4, 2008, at 1:13 PM, Vasily Zakharov wrote: Hi, all, I see Geronimo still uses jaxb-impl version 2.0.5, while 2.1.6 is the latest stable release. Is there any particular reason for that? What do you people think about switching to 2.1.x? I was recently investigating a nasty intermittent failure of org.apache.geronimo.cxf.CXFHandlerResolverTest test on Harmony (HARMONY-5625) and it seems the problem is in JAXB implementation. The problem occurs on jaxb-impl-2.1.3 and earlier and doesn't occur on jaxb-impl-2.1.4 and later. I suspect JAXB issue 383 [1] is the cause. In other words, bugs in jaxb-impl 2.0.5 are affecting Geronimo operation, at least on Harmony, and that looks like a reason for switching to a newer release. Vasily [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=383 Hi Vasily, Thanks for the info. JAXB 2.1 presents Java EE 5 TCK issues for us. We're working to learn from Sun how to pass the TCK w/ JAXB/JAXWS 2.1. Not something that i'd anticipate for a near-term, 2.0/2.1 release. However, don't see why we shouldn't start exploring this on our dev trunk (e.g. 2.2-SNAPSHOT). --kevan
Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
Kevan, Do you mean we could switch the trunk to jaxb-impl 2.1.6 right now? I could prepare a patch and put it to GERONIMO-3951. Vasily On Fri, Apr 4, 2008 at 8:35 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: > > > > On Apr 4, 2008, at 1:13 PM, Vasily Zakharov wrote: > Hi, all, > > I see Geronimo still uses jaxb-impl version 2.0.5, while 2.1.6 is the > latest stable release. > Is there any particular reason for that? > What do you people think about switching to 2.1.x? > > I was recently investigating a nasty intermittent failure of > org.apache.geronimo.cxf.CXFHandlerResolverTest test on Harmony > (HARMONY-5625) and it seems the problem is in JAXB implementation. The > problem occurs on jaxb-impl-2.1.3 and earlier and doesn't occur on > jaxb-impl-2.1.4 and later. I suspect JAXB issue 383 [1] is the cause. > > In other words, bugs in jaxb-impl 2.0.5 are affecting Geronimo > operation, at least on Harmony, and that looks like a reason for > switching to a newer release. > > Vasily > > [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=383 > > Hi Vasily, > Thanks for the info. JAXB 2.1 presents Java EE 5 TCK issues for us. We're > working to learn from Sun how to pass the TCK w/ JAXB/JAXWS 2.1. Not > something that i'd anticipate for a near-term, 2.0/2.1 release. However, > don't see why we shouldn't start exploring this on our dev trunk (e.g. > 2.2-SNAPSHOT). > > --kevan > >
Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
On Fri, Apr 4, 2008 at 10:35 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: > Heh. Vasily did -- https://issues.apache.org/jira/browse/GERONIMO-3951 Whoops, I noticed it right after I had sent the email of mine. Sorry. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
> On Apr 4, 2008, at 4:28 PM, Jacek Laskowski wrote: > On Fri, Apr 4, 2008 at 7:13 PM, Vasily Zakharov <[EMAIL PROTECTED]> wrote: > > I see Geronimo still uses jaxb-impl version 2.0.5, while 2.1.6 is the > latest stable release. > Is there any particular reason for that? > What do you people think about switching to 2.1.x? > > Could you report an issue in Geronimo JIRA so it won't fall through the > cracks? > > Heh. Vasily did -- https://issues.apache.org/jira/browse/GERONIMO-3951 Yep, sorry for not mentioning that. Vasily
Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
On Apr 4, 2008, at 4:28 PM, Jacek Laskowski wrote: On Fri, Apr 4, 2008 at 7:13 PM, Vasily Zakharov <[EMAIL PROTECTED]> wrote: I see Geronimo still uses jaxb-impl version 2.0.5, while 2.1.6 is the latest stable release. Is there any particular reason for that? What do you people think about switching to 2.1.x? Could you report an issue in Geronimo JIRA so it won't fall through the cracks? Heh. Vasily did -- https://issues.apache.org/jira/browse/GERONIMO-3951 --kevan
Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
On Fri, Apr 4, 2008 at 7:13 PM, Vasily Zakharov <[EMAIL PROTECTED]> wrote: > I see Geronimo still uses jaxb-impl version 2.0.5, while 2.1.6 is the > latest stable release. > Is there any particular reason for that? > What do you people think about switching to 2.1.x? Could you report an issue in Geronimo JIRA so it won't fall through the cracks? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
On Apr 4, 2008, at 1:13 PM, Vasily Zakharov wrote: Hi, all, I see Geronimo still uses jaxb-impl version 2.0.5, while 2.1.6 is the latest stable release. Is there any particular reason for that? What do you people think about switching to 2.1.x? I was recently investigating a nasty intermittent failure of org.apache.geronimo.cxf.CXFHandlerResolverTest test on Harmony (HARMONY-5625) and it seems the problem is in JAXB implementation. The problem occurs on jaxb-impl-2.1.3 and earlier and doesn't occur on jaxb-impl-2.1.4 and later. I suspect JAXB issue 383 [1] is the cause. In other words, bugs in jaxb-impl 2.0.5 are affecting Geronimo operation, at least on Harmony, and that looks like a reason for switching to a newer release. Vasily [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=383 Hi Vasily, Thanks for the info. JAXB 2.1 presents Java EE 5 TCK issues for us. We're working to learn from Sun how to pass the TCK w/ JAXB/JAXWS 2.1. Not something that i'd anticipate for a near-term, 2.0/2.1 release. However, don't see why we shouldn't start exploring this on our dev trunk (e.g. 2.2-SNAPSHOT). --kevan
