Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of jgawor@gmail.com designates
 74.125.46.29 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=TME19LBWpplzkPoGaeqnan0ynU/jiQXGCEErgXenESD6xRkjqH0/XZ+PRSvFxOiWnZaPcfpFPxejTqGcKOOeB+wWCv71JfaYiLNXCmVquEc+8jw3Ff6JTnOR31YTXyDwHVImMzavh3M3lrhQ8iC9I/gBG+vjiEuRdFnHeVAWqDU=
Message-ID: <5eb405c70804100749q4dd6aa8ci14dce81dac94700@mail.gmail.com>
Date: Thu, 10 Apr 2008 10:49:59 -0400
From: "Jarek Gawor" <jgawor@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: Upgrading jaxb-impl 2.0.5 to 2.1.6 ?
In-Reply-To: <47FE2790.5010303@earthlink.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <bd849a5d0804041013i5aebf94bu5dae761e650f18d1@mail.gmail.com>
	 <3C82B1AA-9128-4D87-9FB9-D93675832803@gmail.com>
	 <bd849a5d0804100703o133b2f44vd4cdcc1e36a2b146@mail.gmail.com>
	 <47FE2790.5010303@earthlink.net>

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 <joe.bohn@earthlink.net> 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 <kevan.miller@gmail.com>
> 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
> > >
> > >
> > >
> >
> >
>
>