You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by David Blevins <da...@gmail.com> on 2013/03/02 06:27:56 UTC
Availability of 1.5.2 snapshots
Based on the feedback we got we've created a 1.5.2 branch based on the code from approximately Sat Jan 19.
This includes the following JIRAs that were requested:
- https://issues.apache.org/jira/browse/TOMEE-669
- https://issues.apache.org/jira/browse/TOMEE-668
- https://issues.apache.org/jira/browse/TOMEE-699
- https://issues.apache.org/jira/browse/TOMEE-703
This does not yet include this requested JIRA:
- https://issues.apache.org/jira/browse/TOMEE-779
We will definitely add that.
For those that are planing to use the 1.5.2 rather than the 1.6.0 with the various system rewrites for performance, can you please try the 1.5.2 snapshots and report if anything you need is missing.
Builds available here:
- http://tomee.apache.org/builds.html
If possible, get your feedback in by Friday and we can start rolling potential release candidates.
-David
Re: Availability of 1.5.2 snapshots
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
James, it's best to examine Romain's URLs before/after clicking URL, remove
last few characters of the URL, and press Enter in your browser.
On Mar 3, 2013 2:50 PM, "James Green" <ja...@gmail.com> wrote:
> 404 not found.
>
>
>
> On 3 March 2013 19:46, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > Basically
> >
> >
> http://svn.apache.org/repos/asf/tomee/tomee/tags/tomee-1.5.1/arquillian/arquillian-tomee-tests/arquillian-tomee-jaxrs-tests/src/test/java/org/apache/openejb/arquillian/tests/jaxrs/apppath/AnnotatedApplication.javarelated
> > test was/is passing
> > Le 3 mars 2013 20:28, "Romain Manni-Bucau" <rm...@gmail.com> a
> > écrit :
> >
> > > Hmm, should work on 1.6 and was working for 1.5. I got a weird similar
> > > issue on 1.5 once but was in a particular case.
> > > Le 3 mars 2013 18:12, "James Green" <ja...@gmail.com> a
> écrit :
> > >
> > >> Sorry I'm describing the app incorrectly. From the source this time:
> > >>
> > >> @javax.ws.rs.ApplicationPath("/api")
> > >> public class Activator extends javax.ws.rs.core.Application {
> > >> @Override
> > >> public Set<Class<?>> getClasses() {
> > >> Set<Class<?>> s = new HashSet<Class<?>>();
> > >> s.add(MJActionRest.class);
> > >> return s;
> > >> }
> > >> }
> > >>
> > >> @Stateless
> > >> @Path("mjaction")
> > >> @Consumes({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
> > >> @Produces({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
> > >> public class MJActionRest {
> > >> [ code ]
> > >> }
> > >>
> > >> We get /api/mjaction in glassfish, and /mjaction in tomee.
> > >>
> > >> James
> > >>
> > >>
> > >>
> > >> On 3 March 2013 16:34, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> > >>
> > >> > Isnt it @ApplicationPath?
> > >> >
> > >> > @Path for an Application is not defined IIRC
> > >> > Le 3 mars 2013 16:48, "James Green" <ja...@gmail.com> a
> > écrit
> > >> :
> > >> >
> > >> > > Romain,
> > >> > >
> > >> > > When we deployed our war holding a JAX-RS Application, it has an
> > >> > > @Path("/api"). Thus the classes it returns as resources should end
> > up
> > >> as
> > >> > > /api/resource-class. When deployed into Glassfish this happens.
> > >> > >
> > >> > > When deployed into TomEE, we end up with /resource-class. The /api
> > is
> > >> > > ignored. Is this TomEE too?
> > >> > >
> > >> > > Using 1.6.
> > >> > >
> > >> > >
> > >> > >
> > >> > > On 3 March 2013 12:43, Romain Manni-Bucau <rm...@gmail.com>
> > >> wrote:
> > >> > >
> > >> > > > TomEE is responsible of deployment (so config too) + ee
> > integration
> > >> > > > (cdi+ejb). Here it was a deployment issue.
> > >> > > > Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com>
> a
> > >> > écrit :
> > >> > > >
> > >> > > > > This I must be getting confused.
> > >> > > > >
> > >> > > > > On the home page for the project TomEE is composed as a
> > >> distribution
> > >> > of
> > >> > > > > tomcat plus other apache projects such as CXF.
> > >> > > > >
> > >> > > > > When I see a bug such as this, I read the above and naturally
> > >> assume
> > >> > > that
> > >> > > > > the fault lay with CXF. After all, that's where responsibility
> > for
> > >> > web
> > >> > > > > services lay.
> > >> > > > >
> > >> > > > > So how come the bug is listed as TomEE's fault?
> > >> > > > >
> > >> > > > > Thanks,
> > >> > > > >
> > >> > > > > James
> > >> > > > >
> > >> > > > > Sent from my iPad
> > >> > > > >
> > >> > > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <
> > >> rmannibucau@gmail.com>
> > >> > > > wrote:
> > >> > > > >
> > >> > > > > > Guess you spoke about
> > >> > > https://issues.apache.org/jira/browse/TOMEE-690
> > >> > > > > >
> > >> > > > > > Please take care to not merge any jaxrs fix done since this
> > one
> > >> (or
> > >> > > > 1.5.2
> > >> > > > > > will not be a fixes release)
> > >> > > > > > Le 2 mars 2013 20:12, "David Blevins" <
> > david.blevins@gmail.com>
> > >> a
> > >> > > > écrit
> > >> > > > > :
> > >> > > > > >
> > >> > > > > >> Romain, if you can post the JIRA number that'd be great.
> > >> > > > > >>
> > >> > > > > >>
> > >> > > > > >> -David
> > >> > > > > >>
> > >> > > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> > >> > > rmannibucau@gmail.com
> > >> > > > >
> > >> > > > > >> wrote:
> > >> > > > > >>
> > >> > > > > >>> Hmm, providers were working in last release. The
> deployment
> > is
> > >> > > > > different
> > >> > > > > >>> between both release (so the conf too a bit) but it will
> not
> > >> be
> > >> > > > merged
> > >> > > > > >>> because too different.
> > >> > > > > >>> Le 2 mars 2013 10:16, "James Green" <
> > james.mk.green@gmail.com>
> > >> a
> > >> > > > > écrit :
> > >> > > > > >>>
> > >> > > > > >>>> David,
> > >> > > > > >>>>
> > >> > > > > >>>> Thanks for this. Could someone kindly establish which
> Jira
> > >> > relates
> > >> > > > to
> > >> > > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but
> am
> > >> not
> > >> > > sure
> > >> > > > > if
> > >> > > > > >> it
> > >> > > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6.
> > >> Given
> > >> > it
> > >> > > is
> > >> > > > > in
> > >> > > > > >> the
> > >> > > > > >>>> official spec I might hope for the former...
> > >> > > > > >>>>
> > >> > > > > >>>> James
> > >> > > > > >>>>
> > >> > > > > >>>>
> > >> > > > > >>>> Sent from my iPad
> > >> > > > > >>>>
> > >> > > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <
> > >> david.blevins@gmail.com
> > >> > >
> > >> > > > > wrote:
> > >> > > > > >>>>
> > >> > > > > >>>>> Based on the feedback we got we've created a 1.5.2
> branch
> > >> based
> > >> > > on
> > >> > > > > the
> > >> > > > > >>>> code from approximately Sat Jan 19.
> > >> > > > > >>>>>
> > >> > > > > >>>>> This includes the following JIRAs that were requested:
> > >> > > > > >>>>>
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > >> > > > > >>>>>
> > >> > > > > >>>>> This does not yet include this requested JIRA:
> > >> > > > > >>>>>
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > >> > > > > >>>>>
> > >> > > > > >>>>> We will definitely add that.
> > >> > > > > >>>>>
> > >> > > > > >>>>> For those that are planing to use the 1.5.2 rather than
> > the
> > >> > 1.6.0
> > >> > > > > with
> > >> > > > > >>>> the various system rewrites for performance, can you
> please
> > >> try
> > >> > > the
> > >> > > > > >> 1.5.2
> > >> > > > > >>>> snapshots and report if anything you need ismissing.
> > >> > > > > >>>>>
> > >> > > > > >>>>> Builds available here:
> > >> > > > > >>>>>
> > >> > > > > >>>>> - http://tomee.apache.org/builds.html
> > >> > > > > >>>>>
> > >> > > > > >>>>> If possible, get your feedback in by Friday and we can
> > start
> > >> > > > rolling
> > >> > > > > >>>> potential release candidates.
> > >> > > > > >>>>>
> > >> > > > > >>>>>
> > >> > > > > >>>>> -David
> > >> > > > > >>
> > >> > > > > >>
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
hmm works for me
btw here the content: https://gist.github.com/rmannibucau/5078005
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/3/3 James Green <ja...@gmail.com>
> 404 not found.
>
>
>
> On 3 March 2013 19:46, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > Basically
> >
> >
> http://svn.apache.org/repos/asf/tomee/tomee/tags/tomee-1.5.1/arquillian/arquillian-tomee-tests/arquillian-tomee-jaxrs-tests/src/test/java/org/apache/openejb/arquillian/tests/jaxrs/apppath/AnnotatedApplication.javarelated
> > test was/is passing
> > Le 3 mars 2013 20:28, "Romain Manni-Bucau" <rm...@gmail.com> a
> > écrit :
> >
> > > Hmm, should work on 1.6 and was working for 1.5. I got a weird similar
> > > issue on 1.5 once but was in a particular case.
> > > Le 3 mars 2013 18:12, "James Green" <ja...@gmail.com> a
> écrit :
> > >
> > >> Sorry I'm describing the app incorrectly. From the source this time:
> > >>
> > >> @javax.ws.rs.ApplicationPath("/api")
> > >> public class Activator extends javax.ws.rs.core.Application {
> > >> @Override
> > >> public Set<Class<?>> getClasses() {
> > >> Set<Class<?>> s = new HashSet<Class<?>>();
> > >> s.add(MJActionRest.class);
> > >> return s;
> > >> }
> > >> }
> > >>
> > >> @Stateless
> > >> @Path("mjaction")
> > >> @Consumes({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
> > >> @Produces({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
> > >> public class MJActionRest {
> > >> [ code ]
> > >> }
> > >>
> > >> We get /api/mjaction in glassfish, and /mjaction in tomee.
> > >>
> > >> James
> > >>
> > >>
> > >>
> > >> On 3 March 2013 16:34, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> > >>
> > >> > Isnt it @ApplicationPath?
> > >> >
> > >> > @Path for an Application is not defined IIRC
> > >> > Le 3 mars 2013 16:48, "James Green" <ja...@gmail.com> a
> > écrit
> > >> :
> > >> >
> > >> > > Romain,
> > >> > >
> > >> > > When we deployed our war holding a JAX-RS Application, it has an
> > >> > > @Path("/api"). Thus the classes it returns as resources should end
> > up
> > >> as
> > >> > > /api/resource-class. When deployed into Glassfish this happens.
> > >> > >
> > >> > > When deployed into TomEE, we end up with /resource-class. The /api
> > is
> > >> > > ignored. Is this TomEE too?
> > >> > >
> > >> > > Using 1.6.
> > >> > >
> > >> > >
> > >> > >
> > >> > > On 3 March 2013 12:43, Romain Manni-Bucau <rm...@gmail.com>
> > >> wrote:
> > >> > >
> > >> > > > TomEE is responsible of deployment (so config too) + ee
> > integration
> > >> > > > (cdi+ejb). Here it was a deployment issue.
> > >> > > > Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com>
> a
> > >> > écrit :
> > >> > > >
> > >> > > > > This I must be getting confused.
> > >> > > > >
> > >> > > > > On the home page for the project TomEE is composed as a
> > >> distribution
> > >> > of
> > >> > > > > tomcat plus other apache projects such as CXF.
> > >> > > > >
> > >> > > > > When I see a bug such as this, I read the above and naturally
> > >> assume
> > >> > > that
> > >> > > > > the fault lay with CXF. After all, that's where responsibility
> > for
> > >> > web
> > >> > > > > services lay.
> > >> > > > >
> > >> > > > > So how come the bug is listed as TomEE's fault?
> > >> > > > >
> > >> > > > > Thanks,
> > >> > > > >
> > >> > > > > James
> > >> > > > >
> > >> > > > > Sent from my iPad
> > >> > > > >
> > >> > > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <
> > >> rmannibucau@gmail.com>
> > >> > > > wrote:
> > >> > > > >
> > >> > > > > > Guess you spoke about
> > >> > > https://issues.apache.org/jira/browse/TOMEE-690
> > >> > > > > >
> > >> > > > > > Please take care to not merge any jaxrs fix done since this
> > one
> > >> (or
> > >> > > > 1.5.2
> > >> > > > > > will not be a fixes release)
> > >> > > > > > Le 2 mars 2013 20:12, "David Blevins" <
> > david.blevins@gmail.com>
> > >> a
> > >> > > > écrit
> > >> > > > > :
> > >> > > > > >
> > >> > > > > >> Romain, if you can post the JIRA number that'd be great.
> > >> > > > > >>
> > >> > > > > >>
> > >> > > > > >> -David
> > >> > > > > >>
> > >> > > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> > >> > > rmannibucau@gmail.com
> > >> > > > >
> > >> > > > > >> wrote:
> > >> > > > > >>
> > >> > > > > >>> Hmm, providers were working in last release. The
> deployment
> > is
> > >> > > > > different
> > >> > > > > >>> between both release (so the conf too a bit) but it will
> not
> > >> be
> > >> > > > merged
> > >> > > > > >>> because too different.
> > >> > > > > >>> Le 2 mars 2013 10:16, "James Green" <
> > james.mk.green@gmail.com>
> > >> a
> > >> > > > > écrit :
> > >> > > > > >>>
> > >> > > > > >>>> David,
> > >> > > > > >>>>
> > >> > > > > >>>> Thanks for this. Could someone kindly establish which
> Jira
> > >> > relates
> > >> > > > to
> > >> > > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but
> am
> > >> not
> > >> > > sure
> > >> > > > > if
> > >> > > > > >> it
> > >> > > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6.
> > >> Given
> > >> > it
> > >> > > is
> > >> > > > > in
> > >> > > > > >> the
> > >> > > > > >>>> official spec I might hope for the former...
> > >> > > > > >>>>
> > >> > > > > >>>> James
> > >> > > > > >>>>
> > >> > > > > >>>>
> > >> > > > > >>>> Sent from my iPad
> > >> > > > > >>>>
> > >> > > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <
> > >> david.blevins@gmail.com
> > >> > >
> > >> > > > > wrote:
> > >> > > > > >>>>
> > >> > > > > >>>>> Based on the feedback we got we've created a 1.5.2
> branch
> > >> based
> > >> > > on
> > >> > > > > the
> > >> > > > > >>>> code from approximately Sat Jan 19.
> > >> > > > > >>>>>
> > >> > > > > >>>>> This includes the following JIRAs that were requested:
> > >> > > > > >>>>>
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > >> > > > > >>>>>
> > >> > > > > >>>>> This does not yet include this requested JIRA:
> > >> > > > > >>>>>
> > >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > >> > > > > >>>>>
> > >> > > > > >>>>> We will definitely add that.
> > >> > > > > >>>>>
> > >> > > > > >>>>> For those that are planing to use the 1.5.2 rather than
> > the
> > >> > 1.6.0
> > >> > > > > with
> > >> > > > > >>>> the various system rewrites for performance, can you
> please
> > >> try
> > >> > > the
> > >> > > > > >> 1.5.2
> > >> > > > > >>>> snapshots and report if anything you need ismissing.
> > >> > > > > >>>>>
> > >> > > > > >>>>> Builds available here:
> > >> > > > > >>>>>
> > >> > > > > >>>>> - http://tomee.apache.org/builds.html
> > >> > > > > >>>>>
> > >> > > > > >>>>> If possible, get your feedback in by Friday and we can
> > start
> > >> > > > rolling
> > >> > > > > >>>> potential release candidates.
> > >> > > > > >>>>>
> > >> > > > > >>>>>
> > >> > > > > >>>>> -David
> > >> > > > > >>
> > >> > > > > >>
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: Availability of 1.5.2 snapshots
Posted by James Green <ja...@gmail.com>.
404 not found.
On 3 March 2013 19:46, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Basically
>
> http://svn.apache.org/repos/asf/tomee/tomee/tags/tomee-1.5.1/arquillian/arquillian-tomee-tests/arquillian-tomee-jaxrs-tests/src/test/java/org/apache/openejb/arquillian/tests/jaxrs/apppath/AnnotatedApplication.javarelated
> test was/is passing
> Le 3 mars 2013 20:28, "Romain Manni-Bucau" <rm...@gmail.com> a
> écrit :
>
> > Hmm, should work on 1.6 and was working for 1.5. I got a weird similar
> > issue on 1.5 once but was in a particular case.
> > Le 3 mars 2013 18:12, "James Green" <ja...@gmail.com> a écrit :
> >
> >> Sorry I'm describing the app incorrectly. From the source this time:
> >>
> >> @javax.ws.rs.ApplicationPath("/api")
> >> public class Activator extends javax.ws.rs.core.Application {
> >> @Override
> >> public Set<Class<?>> getClasses() {
> >> Set<Class<?>> s = new HashSet<Class<?>>();
> >> s.add(MJActionRest.class);
> >> return s;
> >> }
> >> }
> >>
> >> @Stateless
> >> @Path("mjaction")
> >> @Consumes({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
> >> @Produces({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
> >> public class MJActionRest {
> >> [ code ]
> >> }
> >>
> >> We get /api/mjaction in glassfish, and /mjaction in tomee.
> >>
> >> James
> >>
> >>
> >>
> >> On 3 March 2013 16:34, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >>
> >> > Isnt it @ApplicationPath?
> >> >
> >> > @Path for an Application is not defined IIRC
> >> > Le 3 mars 2013 16:48, "James Green" <ja...@gmail.com> a
> écrit
> >> :
> >> >
> >> > > Romain,
> >> > >
> >> > > When we deployed our war holding a JAX-RS Application, it has an
> >> > > @Path("/api"). Thus the classes it returns as resources should end
> up
> >> as
> >> > > /api/resource-class. When deployed into Glassfish this happens.
> >> > >
> >> > > When deployed into TomEE, we end up with /resource-class. The /api
> is
> >> > > ignored. Is this TomEE too?
> >> > >
> >> > > Using 1.6.
> >> > >
> >> > >
> >> > >
> >> > > On 3 March 2013 12:43, Romain Manni-Bucau <rm...@gmail.com>
> >> wrote:
> >> > >
> >> > > > TomEE is responsible of deployment (so config too) + ee
> integration
> >> > > > (cdi+ejb). Here it was a deployment issue.
> >> > > > Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com> a
> >> > écrit :
> >> > > >
> >> > > > > This I must be getting confused.
> >> > > > >
> >> > > > > On the home page for the project TomEE is composed as a
> >> distribution
> >> > of
> >> > > > > tomcat plus other apache projects such as CXF.
> >> > > > >
> >> > > > > When I see a bug such as this, I read the above and naturally
> >> assume
> >> > > that
> >> > > > > the fault lay with CXF. After all, that's where responsibility
> for
> >> > web
> >> > > > > services lay.
> >> > > > >
> >> > > > > So how come the bug is listed as TomEE's fault?
> >> > > > >
> >> > > > > Thanks,
> >> > > > >
> >> > > > > James
> >> > > > >
> >> > > > > Sent from my iPad
> >> > > > >
> >> > > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <
> >> rmannibucau@gmail.com>
> >> > > > wrote:
> >> > > > >
> >> > > > > > Guess you spoke about
> >> > > https://issues.apache.org/jira/browse/TOMEE-690
> >> > > > > >
> >> > > > > > Please take care to not merge any jaxrs fix done since this
> one
> >> (or
> >> > > > 1.5.2
> >> > > > > > will not be a fixes release)
> >> > > > > > Le 2 mars 2013 20:12, "David Blevins" <
> david.blevins@gmail.com>
> >> a
> >> > > > écrit
> >> > > > > :
> >> > > > > >
> >> > > > > >> Romain, if you can post the JIRA number that'd be great.
> >> > > > > >>
> >> > > > > >>
> >> > > > > >> -David
> >> > > > > >>
> >> > > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> >> > > rmannibucau@gmail.com
> >> > > > >
> >> > > > > >> wrote:
> >> > > > > >>
> >> > > > > >>> Hmm, providers were working in last release. The deployment
> is
> >> > > > > different
> >> > > > > >>> between both release (so the conf too a bit) but it will not
> >> be
> >> > > > merged
> >> > > > > >>> because too different.
> >> > > > > >>> Le 2 mars 2013 10:16, "James Green" <
> james.mk.green@gmail.com>
> >> a
> >> > > > > écrit :
> >> > > > > >>>
> >> > > > > >>>> David,
> >> > > > > >>>>
> >> > > > > >>>> Thanks for this. Could someone kindly establish which Jira
> >> > relates
> >> > > > to
> >> > > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am
> >> not
> >> > > sure
> >> > > > > if
> >> > > > > >> it
> >> > > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6.
> >> Given
> >> > it
> >> > > is
> >> > > > > in
> >> > > > > >> the
> >> > > > > >>>> official spec I might hope for the former...
> >> > > > > >>>>
> >> > > > > >>>> James
> >> > > > > >>>>
> >> > > > > >>>>
> >> > > > > >>>> Sent from my iPad
> >> > > > > >>>>
> >> > > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <
> >> david.blevins@gmail.com
> >> > >
> >> > > > > wrote:
> >> > > > > >>>>
> >> > > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch
> >> based
> >> > > on
> >> > > > > the
> >> > > > > >>>> code from approximately Sat Jan 19.
> >> > > > > >>>>>
> >> > > > > >>>>> This includes the following JIRAs that were requested:
> >> > > > > >>>>>
> >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> >> > > > > >>>>>
> >> > > > > >>>>> This does not yet include this requested JIRA:
> >> > > > > >>>>>
> >> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> >> > > > > >>>>>
> >> > > > > >>>>> We will definitely add that.
> >> > > > > >>>>>
> >> > > > > >>>>> For those that are planing to use the 1.5.2 rather than
> the
> >> > 1.6.0
> >> > > > > with
> >> > > > > >>>> the various system rewrites for performance, can you please
> >> try
> >> > > the
> >> > > > > >> 1.5.2
> >> > > > > >>>> snapshots and report if anything you need ismissing.
> >> > > > > >>>>>
> >> > > > > >>>>> Builds available here:
> >> > > > > >>>>>
> >> > > > > >>>>> - http://tomee.apache.org/builds.html
> >> > > > > >>>>>
> >> > > > > >>>>> If possible, get your feedback in by Friday and we can
> start
> >> > > > rolling
> >> > > > > >>>> potential release candidates.
> >> > > > > >>>>>
> >> > > > > >>>>>
> >> > > > > >>>>> -David
> >> > > > > >>
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Basically
http://svn.apache.org/repos/asf/tomee/tomee/tags/tomee-1.5.1/arquillian/arquillian-tomee-tests/arquillian-tomee-jaxrs-tests/src/test/java/org/apache/openejb/arquillian/tests/jaxrs/apppath/AnnotatedApplication.javarelated
test was/is passing
Le 3 mars 2013 20:28, "Romain Manni-Bucau" <rm...@gmail.com> a écrit :
> Hmm, should work on 1.6 and was working for 1.5. I got a weird similar
> issue on 1.5 once but was in a particular case.
> Le 3 mars 2013 18:12, "James Green" <ja...@gmail.com> a écrit :
>
>> Sorry I'm describing the app incorrectly. From the source this time:
>>
>> @javax.ws.rs.ApplicationPath("/api")
>> public class Activator extends javax.ws.rs.core.Application {
>> @Override
>> public Set<Class<?>> getClasses() {
>> Set<Class<?>> s = new HashSet<Class<?>>();
>> s.add(MJActionRest.class);
>> return s;
>> }
>> }
>>
>> @Stateless
>> @Path("mjaction")
>> @Consumes({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
>> @Produces({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
>> public class MJActionRest {
>> [ code ]
>> }
>>
>> We get /api/mjaction in glassfish, and /mjaction in tomee.
>>
>> James
>>
>>
>>
>> On 3 March 2013 16:34, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>
>> > Isnt it @ApplicationPath?
>> >
>> > @Path for an Application is not defined IIRC
>> > Le 3 mars 2013 16:48, "James Green" <ja...@gmail.com> a écrit
>> :
>> >
>> > > Romain,
>> > >
>> > > When we deployed our war holding a JAX-RS Application, it has an
>> > > @Path("/api"). Thus the classes it returns as resources should end up
>> as
>> > > /api/resource-class. When deployed into Glassfish this happens.
>> > >
>> > > When deployed into TomEE, we end up with /resource-class. The /api is
>> > > ignored. Is this TomEE too?
>> > >
>> > > Using 1.6.
>> > >
>> > >
>> > >
>> > > On 3 March 2013 12:43, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>> > >
>> > > > TomEE is responsible of deployment (so config too) + ee integration
>> > > > (cdi+ejb). Here it was a deployment issue.
>> > > > Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com> a
>> > écrit :
>> > > >
>> > > > > This I must be getting confused.
>> > > > >
>> > > > > On the home page for the project TomEE is composed as a
>> distribution
>> > of
>> > > > > tomcat plus other apache projects such as CXF.
>> > > > >
>> > > > > When I see a bug such as this, I read the above and naturally
>> assume
>> > > that
>> > > > > the fault lay with CXF. After all, that's where responsibility for
>> > web
>> > > > > services lay.
>> > > > >
>> > > > > So how come the bug is listed as TomEE's fault?
>> > > > >
>> > > > > Thanks,
>> > > > >
>> > > > > James
>> > > > >
>> > > > > Sent from my iPad
>> > > > >
>> > > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <
>> rmannibucau@gmail.com>
>> > > > wrote:
>> > > > >
>> > > > > > Guess you spoke about
>> > > https://issues.apache.org/jira/browse/TOMEE-690
>> > > > > >
>> > > > > > Please take care to not merge any jaxrs fix done since this one
>> (or
>> > > > 1.5.2
>> > > > > > will not be a fixes release)
>> > > > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com>
>> a
>> > > > écrit
>> > > > > :
>> > > > > >
>> > > > > >> Romain, if you can post the JIRA number that'd be great.
>> > > > > >>
>> > > > > >>
>> > > > > >> -David
>> > > > > >>
>> > > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
>> > > rmannibucau@gmail.com
>> > > > >
>> > > > > >> wrote:
>> > > > > >>
>> > > > > >>> Hmm, providers were working in last release. The deployment is
>> > > > > different
>> > > > > >>> between both release (so the conf too a bit) but it will not
>> be
>> > > > merged
>> > > > > >>> because too different.
>> > > > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com>
>> a
>> > > > > écrit :
>> > > > > >>>
>> > > > > >>>> David,
>> > > > > >>>>
>> > > > > >>>> Thanks for this. Could someone kindly establish which Jira
>> > relates
>> > > > to
>> > > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am
>> not
>> > > sure
>> > > > > if
>> > > > > >> it
>> > > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6.
>> Given
>> > it
>> > > is
>> > > > > in
>> > > > > >> the
>> > > > > >>>> official spec I might hope for the former...
>> > > > > >>>>
>> > > > > >>>> James
>> > > > > >>>>
>> > > > > >>>>
>> > > > > >>>> Sent from my iPad
>> > > > > >>>>
>> > > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <
>> david.blevins@gmail.com
>> > >
>> > > > > wrote:
>> > > > > >>>>
>> > > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch
>> based
>> > > on
>> > > > > the
>> > > > > >>>> code from approximately Sat Jan 19.
>> > > > > >>>>>
>> > > > > >>>>> This includes the following JIRAs that were requested:
>> > > > > >>>>>
>> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
>> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
>> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
>> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
>> > > > > >>>>>
>> > > > > >>>>> This does not yet include this requested JIRA:
>> > > > > >>>>>
>> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
>> > > > > >>>>>
>> > > > > >>>>> We will definitely add that.
>> > > > > >>>>>
>> > > > > >>>>> For those that are planing to use the 1.5.2 rather than the
>> > 1.6.0
>> > > > > with
>> > > > > >>>> the various system rewrites for performance, can you please
>> try
>> > > the
>> > > > > >> 1.5.2
>> > > > > >>>> snapshots and report if anything you need ismissing.
>> > > > > >>>>>
>> > > > > >>>>> Builds available here:
>> > > > > >>>>>
>> > > > > >>>>> - http://tomee.apache.org/builds.html
>> > > > > >>>>>
>> > > > > >>>>> If possible, get your feedback in by Friday and we can start
>> > > > rolling
>> > > > > >>>> potential release candidates.
>> > > > > >>>>>
>> > > > > >>>>>
>> > > > > >>>>> -David
>> > > > > >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hmm, should work on 1.6 and was working for 1.5. I got a weird similar
issue on 1.5 once but was in a particular case.
Le 3 mars 2013 18:12, "James Green" <ja...@gmail.com> a écrit :
> Sorry I'm describing the app incorrectly. From the source this time:
>
> @javax.ws.rs.ApplicationPath("/api")
> public class Activator extends javax.ws.rs.core.Application {
> @Override
> public Set<Class<?>> getClasses() {
> Set<Class<?>> s = new HashSet<Class<?>>();
> s.add(MJActionRest.class);
> return s;
> }
> }
>
> @Stateless
> @Path("mjaction")
> @Consumes({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
> @Produces({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
> public class MJActionRest {
> [ code ]
> }
>
> We get /api/mjaction in glassfish, and /mjaction in tomee.
>
> James
>
>
>
> On 3 March 2013 16:34, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > Isnt it @ApplicationPath?
> >
> > @Path for an Application is not defined IIRC
> > Le 3 mars 2013 16:48, "James Green" <ja...@gmail.com> a écrit :
> >
> > > Romain,
> > >
> > > When we deployed our war holding a JAX-RS Application, it has an
> > > @Path("/api"). Thus the classes it returns as resources should end up
> as
> > > /api/resource-class. When deployed into Glassfish this happens.
> > >
> > > When deployed into TomEE, we end up with /resource-class. The /api is
> > > ignored. Is this TomEE too?
> > >
> > > Using 1.6.
> > >
> > >
> > >
> > > On 3 March 2013 12:43, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> > >
> > > > TomEE is responsible of deployment (so config too) + ee integration
> > > > (cdi+ejb). Here it was a deployment issue.
> > > > Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com> a
> > écrit :
> > > >
> > > > > This I must be getting confused.
> > > > >
> > > > > On the home page for the project TomEE is composed as a
> distribution
> > of
> > > > > tomcat plus other apache projects such as CXF.
> > > > >
> > > > > When I see a bug such as this, I read the above and naturally
> assume
> > > that
> > > > > the fault lay with CXF. After all, that's where responsibility for
> > web
> > > > > services lay.
> > > > >
> > > > > So how come the bug is listed as TomEE's fault?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > James
> > > > >
> > > > > Sent from my iPad
> > > > >
> > > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Guess you spoke about
> > > https://issues.apache.org/jira/browse/TOMEE-690
> > > > > >
> > > > > > Please take care to not merge any jaxrs fix done since this one
> (or
> > > > 1.5.2
> > > > > > will not be a fixes release)
> > > > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com>
> a
> > > > écrit
> > > > > :
> > > > > >
> > > > > >> Romain, if you can post the JIRA number that'd be great.
> > > > > >>
> > > > > >>
> > > > > >> -David
> > > > > >>
> > > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> > > rmannibucau@gmail.com
> > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >>> Hmm, providers were working in last release. The deployment is
> > > > > different
> > > > > >>> between both release (so the conf too a bit) but it will not be
> > > > merged
> > > > > >>> because too different.
> > > > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com>
> a
> > > > > écrit :
> > > > > >>>
> > > > > >>>> David,
> > > > > >>>>
> > > > > >>>> Thanks for this. Could someone kindly establish which Jira
> > relates
> > > > to
> > > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am
> not
> > > sure
> > > > > if
> > > > > >> it
> > > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given
> > it
> > > is
> > > > > in
> > > > > >> the
> > > > > >>>> official spec I might hope for the former...
> > > > > >>>>
> > > > > >>>> James
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> Sent from my iPad
> > > > > >>>>
> > > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <
> david.blevins@gmail.com
> > >
> > > > > wrote:
> > > > > >>>>
> > > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch
> based
> > > on
> > > > > the
> > > > > >>>> code from approximately Sat Jan 19.
> > > > > >>>>>
> > > > > >>>>> This includes the following JIRAs that were requested:
> > > > > >>>>>
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > > > > >>>>>
> > > > > >>>>> This does not yet include this requested JIRA:
> > > > > >>>>>
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > > > > >>>>>
> > > > > >>>>> We will definitely add that.
> > > > > >>>>>
> > > > > >>>>> For those that are planing to use the 1.5.2 rather than the
> > 1.6.0
> > > > > with
> > > > > >>>> the various system rewrites for performance, can you please
> try
> > > the
> > > > > >> 1.5.2
> > > > > >>>> snapshots and report if anything you need ismissing.
> > > > > >>>>>
> > > > > >>>>> Builds available here:
> > > > > >>>>>
> > > > > >>>>> - http://tomee.apache.org/builds.html
> > > > > >>>>>
> > > > > >>>>> If possible, get your feedback in by Friday and we can start
> > > > rolling
> > > > > >>>> potential release candidates.
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> -David
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
>
Re: Availability of 1.5.2 snapshots
Posted by James Green <ja...@gmail.com>.
Sorry I'm describing the app incorrectly. From the source this time:
@javax.ws.rs.ApplicationPath("/api")
public class Activator extends javax.ws.rs.core.Application {
@Override
public Set<Class<?>> getClasses() {
Set<Class<?>> s = new HashSet<Class<?>>();
s.add(MJActionRest.class);
return s;
}
}
@Stateless
@Path("mjaction")
@Consumes({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
@Produces({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
public class MJActionRest {
[ code ]
}
We get /api/mjaction in glassfish, and /mjaction in tomee.
James
On 3 March 2013 16:34, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Isnt it @ApplicationPath?
>
> @Path for an Application is not defined IIRC
> Le 3 mars 2013 16:48, "James Green" <ja...@gmail.com> a écrit :
>
> > Romain,
> >
> > When we deployed our war holding a JAX-RS Application, it has an
> > @Path("/api"). Thus the classes it returns as resources should end up as
> > /api/resource-class. When deployed into Glassfish this happens.
> >
> > When deployed into TomEE, we end up with /resource-class. The /api is
> > ignored. Is this TomEE too?
> >
> > Using 1.6.
> >
> >
> >
> > On 3 March 2013 12:43, Romain Manni-Bucau <rm...@gmail.com> wrote:
> >
> > > TomEE is responsible of deployment (so config too) + ee integration
> > > (cdi+ejb). Here it was a deployment issue.
> > > Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com> a
> écrit :
> > >
> > > > This I must be getting confused.
> > > >
> > > > On the home page for the project TomEE is composed as a distribution
> of
> > > > tomcat plus other apache projects such as CXF.
> > > >
> > > > When I see a bug such as this, I read the above and naturally assume
> > that
> > > > the fault lay with CXF. After all, that's where responsibility for
> web
> > > > services lay.
> > > >
> > > > So how come the bug is listed as TomEE's fault?
> > > >
> > > > Thanks,
> > > >
> > > > James
> > > >
> > > > Sent from my iPad
> > > >
> > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com>
> > > wrote:
> > > >
> > > > > Guess you spoke about
> > https://issues.apache.org/jira/browse/TOMEE-690
> > > > >
> > > > > Please take care to not merge any jaxrs fix done since this one (or
> > > 1.5.2
> > > > > will not be a fixes release)
> > > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a
> > > écrit
> > > > :
> > > > >
> > > > >> Romain, if you can post the JIRA number that'd be great.
> > > > >>
> > > > >>
> > > > >> -David
> > > > >>
> > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > >
> > > > >> wrote:
> > > > >>
> > > > >>> Hmm, providers were working in last release. The deployment is
> > > > different
> > > > >>> between both release (so the conf too a bit) but it will not be
> > > merged
> > > > >>> because too different.
> > > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
> > > > écrit :
> > > > >>>
> > > > >>>> David,
> > > > >>>>
> > > > >>>> Thanks for this. Could someone kindly establish which Jira
> relates
> > > to
> > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am not
> > sure
> > > > if
> > > > >> it
> > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given
> it
> > is
> > > > in
> > > > >> the
> > > > >>>> official spec I might hope for the former...
> > > > >>>>
> > > > >>>> James
> > > > >>>>
> > > > >>>>
> > > > >>>> Sent from my iPad
> > > > >>>>
> > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <david.blevins@gmail.com
> >
> > > > wrote:
> > > > >>>>
> > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch based
> > on
> > > > the
> > > > >>>> code from approximately Sat Jan 19.
> > > > >>>>>
> > > > >>>>> This includes the following JIRAs that were requested:
> > > > >>>>>
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > > > >>>>>
> > > > >>>>> This does not yet include this requested JIRA:
> > > > >>>>>
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > > > >>>>>
> > > > >>>>> We will definitely add that.
> > > > >>>>>
> > > > >>>>> For those that are planing to use the 1.5.2 rather than the
> 1.6.0
> > > > with
> > > > >>>> the various system rewrites for performance, can you please try
> > the
> > > > >> 1.5.2
> > > > >>>> snapshots and report if anything you need ismissing.
> > > > >>>>>
> > > > >>>>> Builds available here:
> > > > >>>>>
> > > > >>>>> - http://tomee.apache.org/builds.html
> > > > >>>>>
> > > > >>>>> If possible, get your feedback in by Friday and we can start
> > > rolling
> > > > >>>> potential release candidates.
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> -David
> > > > >>
> > > > >>
> > > >
> > >
> >
>
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Isnt it @ApplicationPath?
@Path for an Application is not defined IIRC
Le 3 mars 2013 16:48, "James Green" <ja...@gmail.com> a écrit :
> Romain,
>
> When we deployed our war holding a JAX-RS Application, it has an
> @Path("/api"). Thus the classes it returns as resources should end up as
> /api/resource-class. When deployed into Glassfish this happens.
>
> When deployed into TomEE, we end up with /resource-class. The /api is
> ignored. Is this TomEE too?
>
> Using 1.6.
>
>
>
> On 3 March 2013 12:43, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > TomEE is responsible of deployment (so config too) + ee integration
> > (cdi+ejb). Here it was a deployment issue.
> > Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com> a écrit :
> >
> > > This I must be getting confused.
> > >
> > > On the home page for the project TomEE is composed as a distribution of
> > > tomcat plus other apache projects such as CXF.
> > >
> > > When I see a bug such as this, I read the above and naturally assume
> that
> > > the fault lay with CXF. After all, that's where responsibility for web
> > > services lay.
> > >
> > > So how come the bug is listed as TomEE's fault?
> > >
> > > Thanks,
> > >
> > > James
> > >
> > > Sent from my iPad
> > >
> > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> > >
> > > > Guess you spoke about
> https://issues.apache.org/jira/browse/TOMEE-690
> > > >
> > > > Please take care to not merge any jaxrs fix done since this one (or
> > 1.5.2
> > > > will not be a fixes release)
> > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a
> > écrit
> > > :
> > > >
> > > >> Romain, if you can post the JIRA number that'd be great.
> > > >>
> > > >>
> > > >> -David
> > > >>
> > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >>> Hmm, providers were working in last release. The deployment is
> > > different
> > > >>> between both release (so the conf too a bit) but it will not be
> > merged
> > > >>> because too different.
> > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
> > > écrit :
> > > >>>
> > > >>>> David,
> > > >>>>
> > > >>>> Thanks for this. Could someone kindly establish which Jira relates
> > to
> > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am not
> sure
> > > if
> > > >> it
> > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it
> is
> > > in
> > > >> the
> > > >>>> official spec I might hope for the former...
> > > >>>>
> > > >>>> James
> > > >>>>
> > > >>>>
> > > >>>> Sent from my iPad
> > > >>>>
> > > >>>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com>
> > > wrote:
> > > >>>>
> > > >>>>> Based on the feedback we got we've created a 1.5.2 branch based
> on
> > > the
> > > >>>> code from approximately Sat Jan 19.
> > > >>>>>
> > > >>>>> This includes the following JIRAs that were requested:
> > > >>>>>
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > > >>>>>
> > > >>>>> This does not yet include this requested JIRA:
> > > >>>>>
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > > >>>>>
> > > >>>>> We will definitely add that.
> > > >>>>>
> > > >>>>> For those that are planing to use the 1.5.2 rather than the 1.6.0
> > > with
> > > >>>> the various system rewrites for performance, can you please try
> the
> > > >> 1.5.2
> > > >>>> snapshots and report if anything you need ismissing.
> > > >>>>>
> > > >>>>> Builds available here:
> > > >>>>>
> > > >>>>> - http://tomee.apache.org/builds.html
> > > >>>>>
> > > >>>>> If possible, get your feedback in by Friday and we can start
> > rolling
> > > >>>> potential release candidates.
> > > >>>>>
> > > >>>>>
> > > >>>>> -David
> > > >>
> > > >>
> > >
> >
>
Re: Availability of 1.5.2 snapshots
Posted by James Green <ja...@gmail.com>.
Romain,
When we deployed our war holding a JAX-RS Application, it has an
@Path("/api"). Thus the classes it returns as resources should end up as
/api/resource-class. When deployed into Glassfish this happens.
When deployed into TomEE, we end up with /resource-class. The /api is
ignored. Is this TomEE too?
Using 1.6.
On 3 March 2013 12:43, Romain Manni-Bucau <rm...@gmail.com> wrote:
> TomEE is responsible of deployment (so config too) + ee integration
> (cdi+ejb). Here it was a deployment issue.
> Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com> a écrit :
>
> > This I must be getting confused.
> >
> > On the home page for the project TomEE is composed as a distribution of
> > tomcat plus other apache projects such as CXF.
> >
> > When I see a bug such as this, I read the above and naturally assume that
> > the fault lay with CXF. After all, that's where responsibility for web
> > services lay.
> >
> > So how come the bug is listed as TomEE's fault?
> >
> > Thanks,
> >
> > James
> >
> > Sent from my iPad
> >
> > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >
> > > Guess you spoke about https://issues.apache.org/jira/browse/TOMEE-690
> > >
> > > Please take care to not merge any jaxrs fix done since this one (or
> 1.5.2
> > > will not be a fixes release)
> > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a
> écrit
> > :
> > >
> > >> Romain, if you can post the JIRA number that'd be great.
> > >>
> > >>
> > >> -David
> > >>
> > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> > >> wrote:
> > >>
> > >>> Hmm, providers were working in last release. The deployment is
> > different
> > >>> between both release (so the conf too a bit) but it will not be
> merged
> > >>> because too different.
> > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
> > écrit :
> > >>>
> > >>>> David,
> > >>>>
> > >>>> Thanks for this. Could someone kindly establish which Jira relates
> to
> > >>>> JAX-RS providers not being picked up, this is in 1.6 but am not sure
> > if
> > >> it
> > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is
> > in
> > >> the
> > >>>> official spec I might hope for the former...
> > >>>>
> > >>>> James
> > >>>>
> > >>>>
> > >>>> Sent from my iPad
> > >>>>
> > >>>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com>
> > wrote:
> > >>>>
> > >>>>> Based on the feedback we got we've created a 1.5.2 branch based on
> > the
> > >>>> code from approximately Sat Jan 19.
> > >>>>>
> > >>>>> This includes the following JIRAs that were requested:
> > >>>>>
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > >>>>>
> > >>>>> This does not yet include this requested JIRA:
> > >>>>>
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > >>>>>
> > >>>>> We will definitely add that.
> > >>>>>
> > >>>>> For those that are planing to use the 1.5.2 rather than the 1.6.0
> > with
> > >>>> the various system rewrites for performance, can you please try the
> > >> 1.5.2
> > >>>> snapshots and report if anything you need ismissing.
> > >>>>>
> > >>>>> Builds available here:
> > >>>>>
> > >>>>> - http://tomee.apache.org/builds.html
> > >>>>>
> > >>>>> If possible, get your feedback in by Friday and we can start
> rolling
> > >>>> potential release candidates.
> > >>>>>
> > >>>>>
> > >>>>> -David
> > >>
> > >>
> >
>
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
TomEE is responsible of deployment (so config too) + ee integration
(cdi+ejb). Here it was a deployment issue.
Le 3 mars 2013 11:29, "James Green" <ja...@gmail.com> a écrit :
> This I must be getting confused.
>
> On the home page for the project TomEE is composed as a distribution of
> tomcat plus other apache projects such as CXF.
>
> When I see a bug such as this, I read the above and naturally assume that
> the fault lay with CXF. After all, that's where responsibility for web
> services lay.
>
> So how come the bug is listed as TomEE's fault?
>
> Thanks,
>
> James
>
> Sent from my iPad
>
> On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > Guess you spoke about https://issues.apache.org/jira/browse/TOMEE-690
> >
> > Please take care to not merge any jaxrs fix done since this one (or 1.5.2
> > will not be a fixes release)
> > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a écrit
> :
> >
> >> Romain, if you can post the JIRA number that'd be great.
> >>
> >>
> >> -David
> >>
> >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <rm...@gmail.com>
> >> wrote:
> >>
> >>> Hmm, providers were working in last release. The deployment is
> different
> >>> between both release (so the conf too a bit) but it will not be merged
> >>> because too different.
> >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
> écrit :
> >>>
> >>>> David,
> >>>>
> >>>> Thanks for this. Could someone kindly establish which Jira relates to
> >>>> JAX-RS providers not being picked up, this is in 1.6 but am not sure
> if
> >> it
> >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is
> in
> >> the
> >>>> official spec I might hope for the former...
> >>>>
> >>>> James
> >>>>
> >>>>
> >>>> Sent from my iPad
> >>>>
> >>>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com>
> wrote:
> >>>>
> >>>>> Based on the feedback we got we've created a 1.5.2 branch based on
> the
> >>>> code from approximately Sat Jan 19.
> >>>>>
> >>>>> This includes the following JIRAs that were requested:
> >>>>>
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> >>>>>
> >>>>> This does not yet include this requested JIRA:
> >>>>>
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> >>>>>
> >>>>> We will definitely add that.
> >>>>>
> >>>>> For those that are planing to use the 1.5.2 rather than the 1.6.0
> with
> >>>> the various system rewrites for performance, can you please try the
> >> 1.5.2
> >>>> snapshots and report if anything you need ismissing.
> >>>>>
> >>>>> Builds available here:
> >>>>>
> >>>>> - http://tomee.apache.org/builds.html
> >>>>>
> >>>>> If possible, get your feedback in by Friday and we can start rolling
> >>>> potential release candidates.
> >>>>>
> >>>>>
> >>>>> -David
> >>
> >>
>
Re: Availability of 1.5.2 snapshots
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
Hum, it's not really user friendly.
When the popup comes on and asks for an Apache ID, just choose the 'no'
button and you will enter automatically to the anonymous mode.
JLouis
2013/3/3 James Green <ja...@gmail.com>
> Am being asked for my Apache ID. I'm listed on
> http://people.apache.org/committer-index.html#unlistedclas but I doubt my
> full name is what is being asked for...
>
> James
>
>
> On 3 March 2013 15:03, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
>
> > Fully agree.
> > The documentation must be updated.
> >
> > Do you have any idea?
> > Or would you propose changes?
> >
> > It's really easy, just use the blue pen icon on top-right of any page.
> You
> > can choose to edit anonymously and propose a modification.
> > Then, we just have to accept the update so that it's a huge contribution
> to
> > the project.
> >
> > Thanks,
> > Jean-Louis
> >
> >
> > 2013/3/3 James Green <ja...@gmail.com>
> >
> > > Jean-Louis,
> > >
> > > I appreciate the advice. I think the documentation might be considered
> a
> > > little bare when it comes to problems in this regard.
> > >
> > > As TomEE becomes more popular (and it will), there will be people who
> > > simply won't know where TomEE ends and a sub-project begins. The
> greater
> > > the understanding gained from the main documentation page, the less
> time
> > > will be wasted by all.
> > >
> > > James
> > >
> > >
> > >
> > > On 3 March 2013 14:19, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
> > >
> > > > James,
> > > >
> > > > Maybe the best is to push a mail here and we can determine if it's
> > TomEE
> > > > fault or not.
> > > > Otherwise, you have to go through all apache project mailing lists
> and
> > > > either post, or check if that is a referenced bug or not.
> > > >
> > > > JLouis
> > > >
> > > >
> > > > 2013/3/3 James Green <ja...@gmail.com>
> > > >
> > > > > This I must be getting confused.
> > > > >
> > > > > On the home page for the project TomEE is composed as a
> distribution
> > of
> > > > > tomcat plus other apache projects such as CXF.
> > > > >
> > > > > When I see a bug such as this, I read the above and naturally
> assume
> > > that
> > > > > the fault lay with CXF. After all, that's where responsibility for
> > web
> > > > > services lay.
> > > > >
> > > > > So how come the bug is listed as TomEE's fault?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > James
> > > > >
> > > > > Sent from my iPad
> > > > >
> > > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Guess you spoke about
> > > https://issues.apache.org/jira/browse/TOMEE-690
> > > > > >
> > > > > > Please take care to not merge any jaxrs fix done since this one
> (or
> > > > 1.5.2
> > > > > > will not be a fixes release)
> > > > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com>
> a
> > > > écrit
> > > > > :
> > > > > >
> > > > > >> Romain, if you can post the JIRA number that'd be great.
> > > > > >>
> > > > > >>
> > > > > >> -David
> > > > > >>
> > > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> > > rmannibucau@gmail.com
> > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >>> Hmm, providers were working in last release. The deployment is
> > > > > different
> > > > > >>> between both release (so the conf too a bit) but it will not be
> > > > merged
> > > > > >>> because too different.
> > > > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com>
> a
> > > > > écrit :
> > > > > >>>
> > > > > >>>> David,
> > > > > >>>>
> > > > > >>>> Thanks for this. Could someone kindly establish which Jira
> > relates
> > > > to
> > > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am
> not
> > > sure
> > > > > if
> > > > > >> it
> > > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given
> > it
> > > is
> > > > > in
> > > > > >> the
> > > > > >>>> official spec I might hope for the former...
> > > > > >>>>
> > > > > >>>> James
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> Sent from my iPad
> > > > > >>>>
> > > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <
> david.blevins@gmail.com
> > >
> > > > > wrote:
> > > > > >>>>
> > > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch
> based
> > > on
> > > > > the
> > > > > >>>> code from approximately Sat Jan 19.
> > > > > >>>>>
> > > > > >>>>> This includes the following JIRAs that were requested:
> > > > > >>>>>
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > > > > >>>>>
> > > > > >>>>> This does not yet include this requested JIRA:
> > > > > >>>>>
> > > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > > > > >>>>>
> > > > > >>>>> We will definitely add that.
> > > > > >>>>>
> > > > > >>>>> For those that are planing to use the 1.5.2 rather than the
> > 1.6.0
> > > > > with
> > > > > >>>> the various system rewrites for performance, can you please
> try
> > > the
> > > > > >> 1.5.2
> > > > > >>>> snapshots and report if anything you need ismissing.
> > > > > >>>>>
> > > > > >>>>> Builds available here:
> > > > > >>>>>
> > > > > >>>>> - http://tomee.apache.org/builds.html
> > > > > >>>>>
> > > > > >>>>> If possible, get your feedback in by Friday and we can start
> > > > rolling
> > > > > >>>> potential release candidates.
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> -David
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Jean-Louis
> > > >
> > >
> >
> >
> >
> > --
> > Jean-Louis
> >
>
--
Jean-Louis
Re: Availability of 1.5.2 snapshots
Posted by James Green <ja...@gmail.com>.
I'm in. Can't say I'm overly impressed with this interface. Someone could
do with upgrading it to Confluence or similar. But that's a different
problem...
James
On 3 March 2013 16:22, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
> I'm using Safari on Mac as well and I also have that warning.
> Actually, it's right because, when using that button, you will get
> forwarded to cms.apache.org
>
> Jean-Louis
>
>
> 2013/3/3 Bjorn Danielsson <bj...@lists.cuspycode.com>
>
> > Are you by any chance using Safari on a Mac? Safari gives me
> > a phishing warning followed by an Apache-ID login prompt when
> > I click "No" in the first dialog. Firefox and Chrome both
> > proceed with an anonymous login.
> >
> > --
> > Bjorn Danielsson
> > Cuspy Code AB
> >
> >
> > James Green <ja...@gmail.com> wrote:
> > > Am being asked for my Apache ID. I'm listed on
> > > http://people.apache.org/committer-index.html#unlistedclas but I doubt
> > my
> > > full name is what is being asked for...
> > >
> > > James
> > >
> > >
> > > On 3 March 2013 15:03, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
> > >
> > >> Fully agree.
> > >> The documentation must be updated.
> > >>
> > >> Do you have any idea?
> > >> Or would you propose changes?
> > >>
> > >> It's really easy, just use the blue pen icon on top-right of any page.
> > You
> > >> can choose to edit anonymously and propose a modification.
> > >> Then, we just have to accept the update so that it's a huge
> > contribution to
> > >> the project.
> > >>
> > >> Thanks,
> > >> Jean-Louis
> > >>
> > >>
> > >> 2013/3/3 James Green <ja...@gmail.com>
> > >>
> > >> > Jean-Louis,
> > >> >
> > >> > I appreciate the advice. I think the documentation might be
> > considered a
> > >> > little bare when it comes to problems in this regard.
> > >> >
> > >> > As TomEE becomes more popular (and it will), there will be people
> who
> > >> > simply won't know where TomEE ends and a sub-project begins. The
> > greater
> > >> > the understanding gained from the main documentation page, the less
> > time
> > >> > will be wasted by all.
> > >> >
> > >> > James
> > >> >
> > >> >
> > >> >
> > >> > On 3 March 2013 14:19, Jean-Louis MONTEIRO <je...@gmail.com>
> > wrote:
> > >> >
> > >> > > James,
> > >> > >
> > >> > > Maybe the best is to push a mail here and we can determine if it's
> > >> TomEE
> > >> > > fault or not.
> > >> > > Otherwise, you have to go through all apache project mailing lists
> > and
> > >> > > either post, or check if that is a referenced bug or not.
> > >> > >
> > >> > > JLouis
> > >> > >
> > >> > >
> > >> > > 2013/3/3 James Green <ja...@gmail.com>
> > >> > >
> > >> > > > This I must be getting confused.
> > >> > > >
> > >> > > > On the home page for the project TomEE is composed as a
> > distribution
> > >> of
> > >> > > > tomcat plus other apache projects such as CXF.
> > >> > > >
> > >> > > > When I see a bug such as this, I read the above and naturally
> > assume
> > >> > that
> > >> > > > the fault lay with CXF. After all, that's where responsibility
> for
> > >> web
> > >> > > > services lay.
> > >> > > >
> > >> > > > So how come the bug is listed as TomEE's fault?
> > >> > > >
> > >> > > > Thanks,
> > >> > > >
> > >> > > > James
> > >> > > >
> > >> > > > Sent from my iPad
> > >> > > >
> > >> > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <
> > rmannibucau@gmail.com>
> > >> > > wrote:
> > >> > > >
> > >> > > > > Guess you spoke about
> > >> > https://issues.apache.org/jira/browse/TOMEE-690
> > >> > > > >
> > >> > > > > Please take care to not merge any jaxrs fix done since this
> one
> > (or
> > >> > > 1.5.2
> > >> > > > > will not be a fixes release)
> > >> > > > > Le 2 mars 2013 20:12, "David Blevins" <
> david.blevins@gmail.com>
> > a
> > >> > > écrit
> > >> > > > :
> > >> > > > >
> > >> > > > >> Romain, if you can post the JIRA number that'd be great.
> > >> > > > >>
> > >> > > > >>
> > >> > > > >> -David
> > >> > > > >>
> > >> > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> > >> > rmannibucau@gmail.com
> > >> > > >
> > >> > > > >> wrote:
> > >> > > > >>
> > >> > > > >>> Hmm, providers were working in last release. The deployment
> is
> > >> > > > different
> > >> > > > >>> between both release (so the conf too a bit) but it will not
> > be
> > >> > > merged
> > >> > > > >>> because too different.
> > >> > > > >>> Le 2 mars 2013 10:16, "James Green" <
> james.mk.green@gmail.com>
> > a
> > >> > > > écrit :
> > >> > > > >>>
> > >> > > > >>>> David,
> > >> > > > >>>>
> > >> > > > >>>> Thanks for this. Could someone kindly establish which Jira
> > >> relates
> > >> > > to
> > >> > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am
> > not
> > >> > sure
> > >> > > > if
> > >> > > > >> it
> > >> > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6.
> > Given
> > >> it
> > >> > is
> > >> > > > in
> > >> > > > >> the
> > >> > > > >>>> official spec I might hope for the former...
> > >> > > > >>>>
> > >> > > > >>>> James
> > >> > > > >>>>
> > >> > > > >>>>
> > >> > > > >>>> Sent from my iPad
> > >> > > > >>>>
> > >> > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <
> > david.blevins@gmail.com
> > >> >
> > >> > > > wrote:
> > >> > > > >>>>
> > >> > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch
> > based
> > >> > on
> > >> > > > the
> > >> > > > >>>> code from approximately Sat Jan 19.
> > >> > > > >>>>>
> > >> > > > >>>>> This includes the following JIRAs that were requested:
> > >> > > > >>>>>
> > >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > >> > > > >>>>>
> > >> > > > >>>>> This does not yet include this requested JIRA:
> > >> > > > >>>>>
> > >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > >> > > > >>>>>
> > >> > > > >>>>> We will definitely add that.
> > >> > > > >>>>>
> > >> > > > >>>>> For those that are planing to use the 1.5.2 rather than
> the
> > >> 1.6.0
> > >> > > > with
> > >> > > > >>>> the various system rewrites for performance, can you please
> > try
> > >> > the
> > >> > > > >> 1.5.2
> > >> > > > >>>> snapshots and report if anything you need ismissing.
> > >> > > > >>>>>
> > >> > > > >>>>> Builds available here:
> > >> > > > >>>>>
> > >> > > > >>>>> - http://tomee.apache.org/builds.html
> > >> > > > >>>>>
> > >> > > > >>>>> If possible, get your feedback in by Friday and we can
> start
> > >> > > rolling
> > >> > > > >>>> potential release candidates.
> > >> > > > >>>>>
> > >> > > > >>>>>
> > >> > > > >>>>> -David
> > >> > > > >>
> > >> > > > >>
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Jean-Louis
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Jean-Louis
> > >>
> >
>
>
>
> --
> Jean-Louis
>
Re: Availability of 1.5.2 snapshots
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
I'm using Safari on Mac as well and I also have that warning.
Actually, it's right because, when using that button, you will get
forwarded to cms.apache.org
Jean-Louis
2013/3/3 Bjorn Danielsson <bj...@lists.cuspycode.com>
> Are you by any chance using Safari on a Mac? Safari gives me
> a phishing warning followed by an Apache-ID login prompt when
> I click "No" in the first dialog. Firefox and Chrome both
> proceed with an anonymous login.
>
> --
> Bjorn Danielsson
> Cuspy Code AB
>
>
> James Green <ja...@gmail.com> wrote:
> > Am being asked for my Apache ID. I'm listed on
> > http://people.apache.org/committer-index.html#unlistedclas but I doubt
> my
> > full name is what is being asked for...
> >
> > James
> >
> >
> > On 3 March 2013 15:03, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
> >
> >> Fully agree.
> >> The documentation must be updated.
> >>
> >> Do you have any idea?
> >> Or would you propose changes?
> >>
> >> It's really easy, just use the blue pen icon on top-right of any page.
> You
> >> can choose to edit anonymously and propose a modification.
> >> Then, we just have to accept the update so that it's a huge
> contribution to
> >> the project.
> >>
> >> Thanks,
> >> Jean-Louis
> >>
> >>
> >> 2013/3/3 James Green <ja...@gmail.com>
> >>
> >> > Jean-Louis,
> >> >
> >> > I appreciate the advice. I think the documentation might be
> considered a
> >> > little bare when it comes to problems in this regard.
> >> >
> >> > As TomEE becomes more popular (and it will), there will be people who
> >> > simply won't know where TomEE ends and a sub-project begins. The
> greater
> >> > the understanding gained from the main documentation page, the less
> time
> >> > will be wasted by all.
> >> >
> >> > James
> >> >
> >> >
> >> >
> >> > On 3 March 2013 14:19, Jean-Louis MONTEIRO <je...@gmail.com>
> wrote:
> >> >
> >> > > James,
> >> > >
> >> > > Maybe the best is to push a mail here and we can determine if it's
> >> TomEE
> >> > > fault or not.
> >> > > Otherwise, you have to go through all apache project mailing lists
> and
> >> > > either post, or check if that is a referenced bug or not.
> >> > >
> >> > > JLouis
> >> > >
> >> > >
> >> > > 2013/3/3 James Green <ja...@gmail.com>
> >> > >
> >> > > > This I must be getting confused.
> >> > > >
> >> > > > On the home page for the project TomEE is composed as a
> distribution
> >> of
> >> > > > tomcat plus other apache projects such as CXF.
> >> > > >
> >> > > > When I see a bug such as this, I read the above and naturally
> assume
> >> > that
> >> > > > the fault lay with CXF. After all, that's where responsibility for
> >> web
> >> > > > services lay.
> >> > > >
> >> > > > So how come the bug is listed as TomEE's fault?
> >> > > >
> >> > > > Thanks,
> >> > > >
> >> > > > James
> >> > > >
> >> > > > Sent from my iPad
> >> > > >
> >> > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <
> rmannibucau@gmail.com>
> >> > > wrote:
> >> > > >
> >> > > > > Guess you spoke about
> >> > https://issues.apache.org/jira/browse/TOMEE-690
> >> > > > >
> >> > > > > Please take care to not merge any jaxrs fix done since this one
> (or
> >> > > 1.5.2
> >> > > > > will not be a fixes release)
> >> > > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com>
> a
> >> > > écrit
> >> > > > :
> >> > > > >
> >> > > > >> Romain, if you can post the JIRA number that'd be great.
> >> > > > >>
> >> > > > >>
> >> > > > >> -David
> >> > > > >>
> >> > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> >> > rmannibucau@gmail.com
> >> > > >
> >> > > > >> wrote:
> >> > > > >>
> >> > > > >>> Hmm, providers were working in last release. The deployment is
> >> > > > different
> >> > > > >>> between both release (so the conf too a bit) but it will not
> be
> >> > > merged
> >> > > > >>> because too different.
> >> > > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com>
> a
> >> > > > écrit :
> >> > > > >>>
> >> > > > >>>> David,
> >> > > > >>>>
> >> > > > >>>> Thanks for this. Could someone kindly establish which Jira
> >> relates
> >> > > to
> >> > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am
> not
> >> > sure
> >> > > > if
> >> > > > >> it
> >> > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6.
> Given
> >> it
> >> > is
> >> > > > in
> >> > > > >> the
> >> > > > >>>> official spec I might hope for the former...
> >> > > > >>>>
> >> > > > >>>> James
> >> > > > >>>>
> >> > > > >>>>
> >> > > > >>>> Sent from my iPad
> >> > > > >>>>
> >> > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <
> david.blevins@gmail.com
> >> >
> >> > > > wrote:
> >> > > > >>>>
> >> > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch
> based
> >> > on
> >> > > > the
> >> > > > >>>> code from approximately Sat Jan 19.
> >> > > > >>>>>
> >> > > > >>>>> This includes the following JIRAs that were requested:
> >> > > > >>>>>
> >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> >> > > > >>>>>
> >> > > > >>>>> This does not yet include this requested JIRA:
> >> > > > >>>>>
> >> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> >> > > > >>>>>
> >> > > > >>>>> We will definitely add that.
> >> > > > >>>>>
> >> > > > >>>>> For those that are planing to use the 1.5.2 rather than the
> >> 1.6.0
> >> > > > with
> >> > > > >>>> the various system rewrites for performance, can you please
> try
> >> > the
> >> > > > >> 1.5.2
> >> > > > >>>> snapshots and report if anything you need ismissing.
> >> > > > >>>>>
> >> > > > >>>>> Builds available here:
> >> > > > >>>>>
> >> > > > >>>>> - http://tomee.apache.org/builds.html
> >> > > > >>>>>
> >> > > > >>>>> If possible, get your feedback in by Friday and we can start
> >> > > rolling
> >> > > > >>>> potential release candidates.
> >> > > > >>>>>
> >> > > > >>>>>
> >> > > > >>>>> -David
> >> > > > >>
> >> > > > >>
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Jean-Louis
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Jean-Louis
> >>
>
--
Jean-Louis
Re: Availability of 1.5.2 snapshots
Posted by Bjorn Danielsson <bj...@lists.cuspycode.com>.
Are you by any chance using Safari on a Mac? Safari gives me
a phishing warning followed by an Apache-ID login prompt when
I click "No" in the first dialog. Firefox and Chrome both
proceed with an anonymous login.
--
Bjorn Danielsson
Cuspy Code AB
James Green <ja...@gmail.com> wrote:
> Am being asked for my Apache ID. I'm listed on
> http://people.apache.org/committer-index.html#unlistedclas but I doubt my
> full name is what is being asked for...
>
> James
>
>
> On 3 March 2013 15:03, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
>
>> Fully agree.
>> The documentation must be updated.
>>
>> Do you have any idea?
>> Or would you propose changes?
>>
>> It's really easy, just use the blue pen icon on top-right of any page. You
>> can choose to edit anonymously and propose a modification.
>> Then, we just have to accept the update so that it's a huge contribution to
>> the project.
>>
>> Thanks,
>> Jean-Louis
>>
>>
>> 2013/3/3 James Green <ja...@gmail.com>
>>
>> > Jean-Louis,
>> >
>> > I appreciate the advice. I think the documentation might be considered a
>> > little bare when it comes to problems in this regard.
>> >
>> > As TomEE becomes more popular (and it will), there will be people who
>> > simply won't know where TomEE ends and a sub-project begins. The greater
>> > the understanding gained from the main documentation page, the less time
>> > will be wasted by all.
>> >
>> > James
>> >
>> >
>> >
>> > On 3 March 2013 14:19, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
>> >
>> > > James,
>> > >
>> > > Maybe the best is to push a mail here and we can determine if it's
>> TomEE
>> > > fault or not.
>> > > Otherwise, you have to go through all apache project mailing lists and
>> > > either post, or check if that is a referenced bug or not.
>> > >
>> > > JLouis
>> > >
>> > >
>> > > 2013/3/3 James Green <ja...@gmail.com>
>> > >
>> > > > This I must be getting confused.
>> > > >
>> > > > On the home page for the project TomEE is composed as a distribution
>> of
>> > > > tomcat plus other apache projects such as CXF.
>> > > >
>> > > > When I see a bug such as this, I read the above and naturally assume
>> > that
>> > > > the fault lay with CXF. After all, that's where responsibility for
>> web
>> > > > services lay.
>> > > >
>> > > > So how come the bug is listed as TomEE's fault?
>> > > >
>> > > > Thanks,
>> > > >
>> > > > James
>> > > >
>> > > > Sent from my iPad
>> > > >
>> > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com>
>> > > wrote:
>> > > >
>> > > > > Guess you spoke about
>> > https://issues.apache.org/jira/browse/TOMEE-690
>> > > > >
>> > > > > Please take care to not merge any jaxrs fix done since this one (or
>> > > 1.5.2
>> > > > > will not be a fixes release)
>> > > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a
>> > > écrit
>> > > > :
>> > > > >
>> > > > >> Romain, if you can post the JIRA number that'd be great.
>> > > > >>
>> > > > >>
>> > > > >> -David
>> > > > >>
>> > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
>> > rmannibucau@gmail.com
>> > > >
>> > > > >> wrote:
>> > > > >>
>> > > > >>> Hmm, providers were working in last release. The deployment is
>> > > > different
>> > > > >>> between both release (so the conf too a bit) but it will not be
>> > > merged
>> > > > >>> because too different.
>> > > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
>> > > > écrit :
>> > > > >>>
>> > > > >>>> David,
>> > > > >>>>
>> > > > >>>> Thanks for this. Could someone kindly establish which Jira
>> relates
>> > > to
>> > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am not
>> > sure
>> > > > if
>> > > > >> it
>> > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given
>> it
>> > is
>> > > > in
>> > > > >> the
>> > > > >>>> official spec I might hope for the former...
>> > > > >>>>
>> > > > >>>> James
>> > > > >>>>
>> > > > >>>>
>> > > > >>>> Sent from my iPad
>> > > > >>>>
>> > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <david.blevins@gmail.com
>> >
>> > > > wrote:
>> > > > >>>>
>> > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch based
>> > on
>> > > > the
>> > > > >>>> code from approximately Sat Jan 19.
>> > > > >>>>>
>> > > > >>>>> This includes the following JIRAs that were requested:
>> > > > >>>>>
>> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
>> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
>> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
>> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
>> > > > >>>>>
>> > > > >>>>> This does not yet include this requested JIRA:
>> > > > >>>>>
>> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
>> > > > >>>>>
>> > > > >>>>> We will definitely add that.
>> > > > >>>>>
>> > > > >>>>> For those that are planing to use the 1.5.2 rather than the
>> 1.6.0
>> > > > with
>> > > > >>>> the various system rewrites for performance, can you please try
>> > the
>> > > > >> 1.5.2
>> > > > >>>> snapshots and report if anything you need ismissing.
>> > > > >>>>>
>> > > > >>>>> Builds available here:
>> > > > >>>>>
>> > > > >>>>> - http://tomee.apache.org/builds.html
>> > > > >>>>>
>> > > > >>>>> If possible, get your feedback in by Friday and we can start
>> > > rolling
>> > > > >>>> potential release candidates.
>> > > > >>>>>
>> > > > >>>>>
>> > > > >>>>> -David
>> > > > >>
>> > > > >>
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Jean-Louis
>> > >
>> >
>>
>>
>>
>> --
>> Jean-Louis
>>
Re: Availability of 1.5.2 snapshots
Posted by James Green <ja...@gmail.com>.
Am being asked for my Apache ID. I'm listed on
http://people.apache.org/committer-index.html#unlistedclas but I doubt my
full name is what is being asked for...
James
On 3 March 2013 15:03, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
> Fully agree.
> The documentation must be updated.
>
> Do you have any idea?
> Or would you propose changes?
>
> It's really easy, just use the blue pen icon on top-right of any page. You
> can choose to edit anonymously and propose a modification.
> Then, we just have to accept the update so that it's a huge contribution to
> the project.
>
> Thanks,
> Jean-Louis
>
>
> 2013/3/3 James Green <ja...@gmail.com>
>
> > Jean-Louis,
> >
> > I appreciate the advice. I think the documentation might be considered a
> > little bare when it comes to problems in this regard.
> >
> > As TomEE becomes more popular (and it will), there will be people who
> > simply won't know where TomEE ends and a sub-project begins. The greater
> > the understanding gained from the main documentation page, the less time
> > will be wasted by all.
> >
> > James
> >
> >
> >
> > On 3 March 2013 14:19, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
> >
> > > James,
> > >
> > > Maybe the best is to push a mail here and we can determine if it's
> TomEE
> > > fault or not.
> > > Otherwise, you have to go through all apache project mailing lists and
> > > either post, or check if that is a referenced bug or not.
> > >
> > > JLouis
> > >
> > >
> > > 2013/3/3 James Green <ja...@gmail.com>
> > >
> > > > This I must be getting confused.
> > > >
> > > > On the home page for the project TomEE is composed as a distribution
> of
> > > > tomcat plus other apache projects such as CXF.
> > > >
> > > > When I see a bug such as this, I read the above and naturally assume
> > that
> > > > the fault lay with CXF. After all, that's where responsibility for
> web
> > > > services lay.
> > > >
> > > > So how come the bug is listed as TomEE's fault?
> > > >
> > > > Thanks,
> > > >
> > > > James
> > > >
> > > > Sent from my iPad
> > > >
> > > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com>
> > > wrote:
> > > >
> > > > > Guess you spoke about
> > https://issues.apache.org/jira/browse/TOMEE-690
> > > > >
> > > > > Please take care to not merge any jaxrs fix done since this one (or
> > > 1.5.2
> > > > > will not be a fixes release)
> > > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a
> > > écrit
> > > > :
> > > > >
> > > > >> Romain, if you can post the JIRA number that'd be great.
> > > > >>
> > > > >>
> > > > >> -David
> > > > >>
> > > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > >
> > > > >> wrote:
> > > > >>
> > > > >>> Hmm, providers were working in last release. The deployment is
> > > > different
> > > > >>> between both release (so the conf too a bit) but it will not be
> > > merged
> > > > >>> because too different.
> > > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
> > > > écrit :
> > > > >>>
> > > > >>>> David,
> > > > >>>>
> > > > >>>> Thanks for this. Could someone kindly establish which Jira
> relates
> > > to
> > > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am not
> > sure
> > > > if
> > > > >> it
> > > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given
> it
> > is
> > > > in
> > > > >> the
> > > > >>>> official spec I might hope for the former...
> > > > >>>>
> > > > >>>> James
> > > > >>>>
> > > > >>>>
> > > > >>>> Sent from my iPad
> > > > >>>>
> > > > >>>> On 2 Mar 2013, at 05:27, David Blevins <david.blevins@gmail.com
> >
> > > > wrote:
> > > > >>>>
> > > > >>>>> Based on the feedback we got we've created a 1.5.2 branch based
> > on
> > > > the
> > > > >>>> code from approximately Sat Jan 19.
> > > > >>>>>
> > > > >>>>> This includes the following JIRAs that were requested:
> > > > >>>>>
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > > > >>>>>
> > > > >>>>> This does not yet include this requested JIRA:
> > > > >>>>>
> > > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > > > >>>>>
> > > > >>>>> We will definitely add that.
> > > > >>>>>
> > > > >>>>> For those that are planing to use the 1.5.2 rather than the
> 1.6.0
> > > > with
> > > > >>>> the various system rewrites for performance, can you please try
> > the
> > > > >> 1.5.2
> > > > >>>> snapshots and report if anything you need ismissing.
> > > > >>>>>
> > > > >>>>> Builds available here:
> > > > >>>>>
> > > > >>>>> - http://tomee.apache.org/builds.html
> > > > >>>>>
> > > > >>>>> If possible, get your feedback in by Friday and we can start
> > > rolling
> > > > >>>> potential release candidates.
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> -David
> > > > >>
> > > > >>
> > > >
> > >
> > >
> > >
> > > --
> > > Jean-Louis
> > >
> >
>
>
>
> --
> Jean-Louis
>
Re: Availability of 1.5.2 snapshots
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
Fully agree.
The documentation must be updated.
Do you have any idea?
Or would you propose changes?
It's really easy, just use the blue pen icon on top-right of any page. You
can choose to edit anonymously and propose a modification.
Then, we just have to accept the update so that it's a huge contribution to
the project.
Thanks,
Jean-Louis
2013/3/3 James Green <ja...@gmail.com>
> Jean-Louis,
>
> I appreciate the advice. I think the documentation might be considered a
> little bare when it comes to problems in this regard.
>
> As TomEE becomes more popular (and it will), there will be people who
> simply won't know where TomEE ends and a sub-project begins. The greater
> the understanding gained from the main documentation page, the less time
> will be wasted by all.
>
> James
>
>
>
> On 3 March 2013 14:19, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
>
> > James,
> >
> > Maybe the best is to push a mail here and we can determine if it's TomEE
> > fault or not.
> > Otherwise, you have to go through all apache project mailing lists and
> > either post, or check if that is a referenced bug or not.
> >
> > JLouis
> >
> >
> > 2013/3/3 James Green <ja...@gmail.com>
> >
> > > This I must be getting confused.
> > >
> > > On the home page for the project TomEE is composed as a distribution of
> > > tomcat plus other apache projects such as CXF.
> > >
> > > When I see a bug such as this, I read the above and naturally assume
> that
> > > the fault lay with CXF. After all, that's where responsibility for web
> > > services lay.
> > >
> > > So how come the bug is listed as TomEE's fault?
> > >
> > > Thanks,
> > >
> > > James
> > >
> > > Sent from my iPad
> > >
> > > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> > >
> > > > Guess you spoke about
> https://issues.apache.org/jira/browse/TOMEE-690
> > > >
> > > > Please take care to not merge any jaxrs fix done since this one (or
> > 1.5.2
> > > > will not be a fixes release)
> > > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a
> > écrit
> > > :
> > > >
> > > >> Romain, if you can post the JIRA number that'd be great.
> > > >>
> > > >>
> > > >> -David
> > > >>
> > > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >>> Hmm, providers were working in last release. The deployment is
> > > different
> > > >>> between both release (so the conf too a bit) but it will not be
> > merged
> > > >>> because too different.
> > > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
> > > écrit :
> > > >>>
> > > >>>> David,
> > > >>>>
> > > >>>> Thanks for this. Could someone kindly establish which Jira relates
> > to
> > > >>>> JAX-RS providers not being picked up, this is in 1.6 but am not
> sure
> > > if
> > > >> it
> > > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it
> is
> > > in
> > > >> the
> > > >>>> official spec I might hope for the former...
> > > >>>>
> > > >>>> James
> > > >>>>
> > > >>>>
> > > >>>> Sent from my iPad
> > > >>>>
> > > >>>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com>
> > > wrote:
> > > >>>>
> > > >>>>> Based on the feedback we got we've created a 1.5.2 branch based
> on
> > > the
> > > >>>> code from approximately Sat Jan 19.
> > > >>>>>
> > > >>>>> This includes the following JIRAs that were requested:
> > > >>>>>
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > > >>>>>
> > > >>>>> This does not yet include this requested JIRA:
> > > >>>>>
> > > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > > >>>>>
> > > >>>>> We will definitely add that.
> > > >>>>>
> > > >>>>> For those that are planing to use the 1.5.2 rather than the 1.6.0
> > > with
> > > >>>> the various system rewrites for performance, can you please try
> the
> > > >> 1.5.2
> > > >>>> snapshots and report if anything you need ismissing.
> > > >>>>>
> > > >>>>> Builds available here:
> > > >>>>>
> > > >>>>> - http://tomee.apache.org/builds.html
> > > >>>>>
> > > >>>>> If possible, get your feedback in by Friday and we can start
> > rolling
> > > >>>> potential release candidates.
> > > >>>>>
> > > >>>>>
> > > >>>>> -David
> > > >>
> > > >>
> > >
> >
> >
> >
> > --
> > Jean-Louis
> >
>
--
Jean-Louis
Re: Availability of 1.5.2 snapshots
Posted by James Green <ja...@gmail.com>.
Jean-Louis,
I appreciate the advice. I think the documentation might be considered a
little bare when it comes to problems in this regard.
As TomEE becomes more popular (and it will), there will be people who
simply won't know where TomEE ends and a sub-project begins. The greater
the understanding gained from the main documentation page, the less time
will be wasted by all.
James
On 3 March 2013 14:19, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
> James,
>
> Maybe the best is to push a mail here and we can determine if it's TomEE
> fault or not.
> Otherwise, you have to go through all apache project mailing lists and
> either post, or check if that is a referenced bug or not.
>
> JLouis
>
>
> 2013/3/3 James Green <ja...@gmail.com>
>
> > This I must be getting confused.
> >
> > On the home page for the project TomEE is composed as a distribution of
> > tomcat plus other apache projects such as CXF.
> >
> > When I see a bug such as this, I read the above and naturally assume that
> > the fault lay with CXF. After all, that's where responsibility for web
> > services lay.
> >
> > So how come the bug is listed as TomEE's fault?
> >
> > Thanks,
> >
> > James
> >
> > Sent from my iPad
> >
> > On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >
> > > Guess you spoke about https://issues.apache.org/jira/browse/TOMEE-690
> > >
> > > Please take care to not merge any jaxrs fix done since this one (or
> 1.5.2
> > > will not be a fixes release)
> > > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a
> écrit
> > :
> > >
> > >> Romain, if you can post the JIRA number that'd be great.
> > >>
> > >>
> > >> -David
> > >>
> > >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> > >> wrote:
> > >>
> > >>> Hmm, providers were working in last release. The deployment is
> > different
> > >>> between both release (so the conf too a bit) but it will not be
> merged
> > >>> because too different.
> > >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
> > écrit :
> > >>>
> > >>>> David,
> > >>>>
> > >>>> Thanks for this. Could someone kindly establish which Jira relates
> to
> > >>>> JAX-RS providers not being picked up, this is in 1.6 but am not sure
> > if
> > >> it
> > >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is
> > in
> > >> the
> > >>>> official spec I might hope for the former...
> > >>>>
> > >>>> James
> > >>>>
> > >>>>
> > >>>> Sent from my iPad
> > >>>>
> > >>>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com>
> > wrote:
> > >>>>
> > >>>>> Based on the feedback we got we've created a 1.5.2 branch based on
> > the
> > >>>> code from approximately Sat Jan 19.
> > >>>>>
> > >>>>> This includes the following JIRAs that were requested:
> > >>>>>
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> > >>>>>
> > >>>>> This does not yet include this requested JIRA:
> > >>>>>
> > >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> > >>>>>
> > >>>>> We will definitely add that.
> > >>>>>
> > >>>>> For those that are planing to use the 1.5.2 rather than the 1.6.0
> > with
> > >>>> the various system rewrites for performance, can you please try the
> > >> 1.5.2
> > >>>> snapshots and report if anything you need ismissing.
> > >>>>>
> > >>>>> Builds available here:
> > >>>>>
> > >>>>> - http://tomee.apache.org/builds.html
> > >>>>>
> > >>>>> If possible, get your feedback in by Friday and we can start
> rolling
> > >>>> potential release candidates.
> > >>>>>
> > >>>>>
> > >>>>> -David
> > >>
> > >>
> >
>
>
>
> --
> Jean-Louis
>
Re: Availability of 1.5.2 snapshots
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
James,
Maybe the best is to push a mail here and we can determine if it's TomEE
fault or not.
Otherwise, you have to go through all apache project mailing lists and
either post, or check if that is a referenced bug or not.
JLouis
2013/3/3 James Green <ja...@gmail.com>
> This I must be getting confused.
>
> On the home page for the project TomEE is composed as a distribution of
> tomcat plus other apache projects such as CXF.
>
> When I see a bug such as this, I read the above and naturally assume that
> the fault lay with CXF. After all, that's where responsibility for web
> services lay.
>
> So how come the bug is listed as TomEE's fault?
>
> Thanks,
>
> James
>
> Sent from my iPad
>
> On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> > Guess you spoke about https://issues.apache.org/jira/browse/TOMEE-690
> >
> > Please take care to not merge any jaxrs fix done since this one (or 1.5.2
> > will not be a fixes release)
> > Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a écrit
> :
> >
> >> Romain, if you can post the JIRA number that'd be great.
> >>
> >>
> >> -David
> >>
> >> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <rm...@gmail.com>
> >> wrote:
> >>
> >>> Hmm, providers were working in last release. The deployment is
> different
> >>> between both release (so the conf too a bit) but it will not be merged
> >>> because too different.
> >>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a
> écrit :
> >>>
> >>>> David,
> >>>>
> >>>> Thanks for this. Could someone kindly establish which Jira relates to
> >>>> JAX-RS providers not being picked up, this is in 1.6 but am not sure
> if
> >> it
> >>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is
> in
> >> the
> >>>> official spec I might hope for the former...
> >>>>
> >>>> James
> >>>>
> >>>>
> >>>> Sent from my iPad
> >>>>
> >>>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com>
> wrote:
> >>>>
> >>>>> Based on the feedback we got we've created a 1.5.2 branch based on
> the
> >>>> code from approximately Sat Jan 19.
> >>>>>
> >>>>> This includes the following JIRAs that were requested:
> >>>>>
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-669
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-668
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-699
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-703
> >>>>>
> >>>>> This does not yet include this requested JIRA:
> >>>>>
> >>>>> - https://issues.apache.org/jira/browse/TOMEE-779
> >>>>>
> >>>>> We will definitely add that.
> >>>>>
> >>>>> For those that are planing to use the 1.5.2 rather than the 1.6.0
> with
> >>>> the various system rewrites for performance, can you please try the
> >> 1.5.2
> >>>> snapshots and report if anything you need ismissing.
> >>>>>
> >>>>> Builds available here:
> >>>>>
> >>>>> - http://tomee.apache.org/builds.html
> >>>>>
> >>>>> If possible, get your feedback in by Friday and we can start rolling
> >>>> potential release candidates.
> >>>>>
> >>>>>
> >>>>> -David
> >>
> >>
>
--
Jean-Louis
Re: Availability of 1.5.2 snapshots
Posted by James Green <ja...@gmail.com>.
This I must be getting confused.
On the home page for the project TomEE is composed as a distribution of tomcat plus other apache projects such as CXF.
When I see a bug such as this, I read the above and naturally assume that the fault lay with CXF. After all, that's where responsibility for web services lay.
So how come the bug is listed as TomEE's fault?
Thanks,
James
Sent from my iPad
On 2 Mar 2013, at 20:01, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Guess you spoke about https://issues.apache.org/jira/browse/TOMEE-690
>
> Please take care to not merge any jaxrs fix done since this one (or 1.5.2
> will not be a fixes release)
> Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a écrit :
>
>> Romain, if you can post the JIRA number that'd be great.
>>
>>
>> -David
>>
>> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>>
>>> Hmm, providers were working in last release. The deployment is different
>>> between both release (so the conf too a bit) but it will not be merged
>>> because too different.
>>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a écrit :
>>>
>>>> David,
>>>>
>>>> Thanks for this. Could someone kindly establish which Jira relates to
>>>> JAX-RS providers not being picked up, this is in 1.6 but am not sure if
>> it
>>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is in
>> the
>>>> official spec I might hope for the former...
>>>>
>>>> James
>>>>
>>>>
>>>> Sent from my iPad
>>>>
>>>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com> wrote:
>>>>
>>>>> Based on the feedback we got we've created a 1.5.2 branch based on the
>>>> code from approximately Sat Jan 19.
>>>>>
>>>>> This includes the following JIRAs that were requested:
>>>>>
>>>>> - https://issues.apache.org/jira/browse/TOMEE-669
>>>>> - https://issues.apache.org/jira/browse/TOMEE-668
>>>>> - https://issues.apache.org/jira/browse/TOMEE-699
>>>>> - https://issues.apache.org/jira/browse/TOMEE-703
>>>>>
>>>>> This does not yet include this requested JIRA:
>>>>>
>>>>> - https://issues.apache.org/jira/browse/TOMEE-779
>>>>>
>>>>> We will definitely add that.
>>>>>
>>>>> For those that are planing to use the 1.5.2 rather than the 1.6.0 with
>>>> the various system rewrites for performance, can you please try the
>> 1.5.2
>>>> snapshots and report if anything you need ismissing.
>>>>>
>>>>> Builds available here:
>>>>>
>>>>> - http://tomee.apache.org/builds.html
>>>>>
>>>>> If possible, get your feedback in by Friday and we can start rolling
>>>> potential release candidates.
>>>>>
>>>>>
>>>>> -David
>>
>>
Re: Availability of 1.5.2 snapshots
Posted by David Blevins <da...@gmail.com>.
As noted, the branch was created just after Sat Jan 19, so does include the JAX-RS change with better logging.
It's fine if we want to revert that, but we'll have to do it quickly. Dev list is probably best place to chat on that.
-David
On Mar 2, 2013, at 12:01 PM, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Guess you spoke about https://issues.apache.org/jira/browse/TOMEE-690
>
> Please take care to not merge any jaxrs fix done since this one (or 1.5.2
> will not be a fixes release)
> Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a écrit :
>
>> Romain, if you can post the JIRA number that'd be great.
>>
>>
>> -David
>>
>> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>>
>>> Hmm, providers were working in last release. The deployment is different
>>> between both release (so the conf too a bit) but it will not be merged
>>> because too different.
>>> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a écrit :
>>>
>>>> David,
>>>>
>>>> Thanks for this. Could someone kindly establish which Jira relates to
>>>> JAX-RS providers not being picked up, this is in 1.6 but am not sure if
>> it
>>>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is in
>> the
>>>> official spec I might hope for the former...
>>>>
>>>> James
>>>>
>>>>
>>>> Sent from my iPad
>>>>
>>>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com> wrote:
>>>>
>>>>> Based on the feedback we got we've created a 1.5.2 branch based on the
>>>> code from approximately Sat Jan 19.
>>>>>
>>>>> This includes the following JIRAs that were requested:
>>>>>
>>>>> - https://issues.apache.org/jira/browse/TOMEE-669
>>>>> - https://issues.apache.org/jira/browse/TOMEE-668
>>>>> - https://issues.apache.org/jira/browse/TOMEE-699
>>>>> - https://issues.apache.org/jira/browse/TOMEE-703
>>>>>
>>>>> This does not yet include this requested JIRA:
>>>>>
>>>>> - https://issues.apache.org/jira/browse/TOMEE-779
>>>>>
>>>>> We will definitely add that.
>>>>>
>>>>> For those that are planing to use the 1.5.2 rather than the 1.6.0 with
>>>> the various system rewrites for performance, can you please try the
>> 1.5.2
>>>> snapshots and report if anything you need ismissing.
>>>>>
>>>>> Builds available here:
>>>>>
>>>>> - http://tomee.apache.org/builds.html
>>>>>
>>>>> If possible, get your feedback in by Friday and we can start rolling
>>>> potential release candidates.
>>>>>
>>>>>
>>>>> -David
>>>>>
>>>>
>>
>>
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Guess you spoke about https://issues.apache.org/jira/browse/TOMEE-690
Please take care to not merge any jaxrs fix done since this one (or 1.5.2
will not be a fixes release)
Le 2 mars 2013 20:12, "David Blevins" <da...@gmail.com> a écrit :
> Romain, if you can post the JIRA number that'd be great.
>
>
> -David
>
> On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > Hmm, providers were working in last release. The deployment is different
> > between both release (so the conf too a bit) but it will not be merged
> > because too different.
> > Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a écrit :
> >
> >> David,
> >>
> >> Thanks for this. Could someone kindly establish which Jira relates to
> >> JAX-RS providers not being picked up, this is in 1.6 but am not sure if
> it
> >> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is in
> the
> >> official spec I might hope for the former...
> >>
> >> James
> >>
> >>
> >> Sent from my iPad
> >>
> >> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com> wrote:
> >>
> >>> Based on the feedback we got we've created a 1.5.2 branch based on the
> >> code from approximately Sat Jan 19.
> >>>
> >>> This includes the following JIRAs that were requested:
> >>>
> >>> - https://issues.apache.org/jira/browse/TOMEE-669
> >>> - https://issues.apache.org/jira/browse/TOMEE-668
> >>> - https://issues.apache.org/jira/browse/TOMEE-699
> >>> - https://issues.apache.org/jira/browse/TOMEE-703
> >>>
> >>> This does not yet include this requested JIRA:
> >>>
> >>> - https://issues.apache.org/jira/browse/TOMEE-779
> >>>
> >>> We will definitely add that.
> >>>
> >>> For those that are planing to use the 1.5.2 rather than the 1.6.0 with
> >> the various system rewrites for performance, can you please try the
> 1.5.2
> >> snapshots and report if anything you need ismissing.
> >>>
> >>> Builds available here:
> >>>
> >>> - http://tomee.apache.org/builds.html
> >>>
> >>> If possible, get your feedback in by Friday and we can start rolling
> >> potential release candidates.
> >>>
> >>>
> >>> -David
> >>>
> >>
>
>
Re: Availability of 1.5.2 snapshots
Posted by David Blevins <da...@gmail.com>.
Romain, if you can post the JIRA number that'd be great.
-David
On Mar 2, 2013, at 1:32 AM, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Hmm, providers were working in last release. The deployment is different
> between both release (so the conf too a bit) but it will not be merged
> because too different.
> Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a écrit :
>
>> David,
>>
>> Thanks for this. Could someone kindly establish which Jira relates to
>> JAX-RS providers not being picked up, this is in 1.6 but am not sure if it
>> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is in the
>> official spec I might hope for the former...
>>
>> James
>>
>>
>> Sent from my iPad
>>
>> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com> wrote:
>>
>>> Based on the feedback we got we've created a 1.5.2 branch based on the
>> code from approximately Sat Jan 19.
>>>
>>> This includes the following JIRAs that were requested:
>>>
>>> - https://issues.apache.org/jira/browse/TOMEE-669
>>> - https://issues.apache.org/jira/browse/TOMEE-668
>>> - https://issues.apache.org/jira/browse/TOMEE-699
>>> - https://issues.apache.org/jira/browse/TOMEE-703
>>>
>>> This does not yet include this requested JIRA:
>>>
>>> - https://issues.apache.org/jira/browse/TOMEE-779
>>>
>>> We will definitely add that.
>>>
>>> For those that are planing to use the 1.5.2 rather than the 1.6.0 with
>> the various system rewrites for performance, can you please try the 1.5.2
>> snapshots and report if anything you need ismissing.
>>>
>>> Builds available here:
>>>
>>> - http://tomee.apache.org/builds.html
>>>
>>> If possible, get your feedback in by Friday and we can start rolling
>> potential release candidates.
>>>
>>>
>>> -David
>>>
>>
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hmm, providers were working in last release. The deployment is different
between both release (so the conf too a bit) but it will not be merged
because too different.
Le 2 mars 2013 10:16, "James Green" <ja...@gmail.com> a écrit :
> David,
>
> Thanks for this. Could someone kindly establish which Jira relates to
> JAX-RS providers not being picked up, this is in 1.6 but am not sure if it
> is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is in the
> official spec I might hope for the former...
>
> James
>
>
> Sent from my iPad
>
> On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com> wrote:
>
> > Based on the feedback we got we've created a 1.5.2 branch based on the
> code from approximately Sat Jan 19.
> >
> > This includes the following JIRAs that were requested:
> >
> > - https://issues.apache.org/jira/browse/TOMEE-669
> > - https://issues.apache.org/jira/browse/TOMEE-668
> > - https://issues.apache.org/jira/browse/TOMEE-699
> > - https://issues.apache.org/jira/browse/TOMEE-703
> >
> > This does not yet include this requested JIRA:
> >
> > - https://issues.apache.org/jira/browse/TOMEE-779
> >
> > We will definitely add that.
> >
> > For those that are planing to use the 1.5.2 rather than the 1.6.0 with
> the various system rewrites for performance, can you please try the 1.5.2
> snapshots and report if anything you need ismissing.
> >
> > Builds available here:
> >
> > - http://tomee.apache.org/builds.html
> >
> > If possible, get your feedback in by Friday and we can start rolling
> potential release candidates.
> >
> >
> > -David
> >
>
Re: Availability of 1.5.2 snapshots
Posted by James Green <ja...@gmail.com>.
David,
Thanks for this. Could someone kindly establish which Jira relates to JAX-RS providers not being picked up, this is in 1.6 but am not sure if it is a bug fix candidate for 1.5 or a new feature for 1.6. Given it is in the official spec I might hope for the former...
James
Sent from my iPad
On 2 Mar 2013, at 05:27, David Blevins <da...@gmail.com> wrote:
> Based on the feedback we got we've created a 1.5.2 branch based on the code from approximately Sat Jan 19.
>
> This includes the following JIRAs that were requested:
>
> - https://issues.apache.org/jira/browse/TOMEE-669
> - https://issues.apache.org/jira/browse/TOMEE-668
> - https://issues.apache.org/jira/browse/TOMEE-699
> - https://issues.apache.org/jira/browse/TOMEE-703
>
> This does not yet include this requested JIRA:
>
> - https://issues.apache.org/jira/browse/TOMEE-779
>
> We will definitely add that.
>
> For those that are planing to use the 1.5.2 rather than the 1.6.0 with the various system rewrites for performance, can you please try the 1.5.2 snapshots and report if anything you need ismissing.
>
> Builds available here:
>
> - http://tomee.apache.org/builds.html
>
> If possible, get your feedback in by Friday and we can start rolling potential release candidates.
>
>
> -David
>
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
If it is in 1.5.2 it should really be removed before the vote
Le 4 mars 2013 22:38, "ymaraner" <tp...@gmail.com> a écrit :
> Romain Manni-Bucau wrote
> > That's a pretty big and important change.
> >
> > I'd keep it for +0.1.x (just my opinion)
> >
> >> If possible, please include TOMEE-664
> >> <https://issues.apache.org/jira/browse/TOMEE-664> in the 1.5.2
> >> release.
>
> After looking at the diffs for that change, I believe that it actually is
> included in the 1.5.2 branch. I tried to delete my comment before anyone
> saw
> it, but apparently I was too late.
>
> However, I have an issue that sounded like the same one that it resolved:
>
> I have an EAR containing a number of EJB jars and one WAR file.
> There are a number of jar files needed by several of the EJB jars that are
> in the lib directory.
> One of those jars in the lib directory contains a persistence.xml file and
> associated class files.
> When I deploy the ear to the 1.5.2 snapshot, the persistence context
> initializes twice, the second initialization is apparently in conjunction
> with the loading of the war file. Unfortunately, this results in the
> ReloadableEntityManagerFactory.delegate not being initialized when I try to
> use it later, resulting in an NPE.
>
> When I deploy the ear to the 1.6.0 snapshot, everything works fine.
>
> I don't know which JIRA Issue fixed the problem in the trunk, but I would
> like that fix included in the 1.5.2 release.
>
> Thanks,
>
>
>
> -----
> - Tim
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Availability-of-1-5-2-snapshots-tp4661139p4661244.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Availability of 1.5.2 snapshots
Posted by ymaraner <tp...@gmail.com>.
Romain Manni-Bucau wrote
> That's a pretty big and important change.
>
> I'd keep it for +0.1.x (just my opinion)
>
>> If possible, please include TOMEE-664
>> <https://issues.apache.org/jira/browse/TOMEE-664> in the 1.5.2
>> release.
After looking at the diffs for that change, I believe that it actually is
included in the 1.5.2 branch. I tried to delete my comment before anyone saw
it, but apparently I was too late.
However, I have an issue that sounded like the same one that it resolved:
I have an EAR containing a number of EJB jars and one WAR file.
There are a number of jar files needed by several of the EJB jars that are
in the lib directory.
One of those jars in the lib directory contains a persistence.xml file and
associated class files.
When I deploy the ear to the 1.5.2 snapshot, the persistence context
initializes twice, the second initialization is apparently in conjunction
with the loading of the war file. Unfortunately, this results in the
ReloadableEntityManagerFactory.delegate not being initialized when I try to
use it later, resulting in an NPE.
When I deploy the ear to the 1.6.0 snapshot, everything works fine.
I don't know which JIRA Issue fixed the problem in the trunk, but I would
like that fix included in the 1.5.2 release.
Thanks,
-----
- Tim
--
View this message in context: http://openejb.979440.n4.nabble.com/Availability-of-1-5-2-snapshots-tp4661139p4661244.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Availability of 1.5.2 snapshots
Posted by Romain Manni-Bucau <rm...@gmail.com>.
That's a pretty big and important change.
I'd keep it for +0.1.x (just my opinion)
Le 4 mars 2013 21:14, "ymaraner" <tp...@gmail.com> a écrit :
> If possible, please include TOMEE-664
> <https://issues.apache.org/jira/browse/TOMEE-664> in the 1.5.2 release.
>
>
>
> -----
> - Tim
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Availability-of-1-5-2-snapshots-tp4661139p4661238.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Availability of 1.5.2 snapshots
Posted by ymaraner <tp...@gmail.com>.
If possible, please include TOMEE-664
<https://issues.apache.org/jira/browse/TOMEE-664> in the 1.5.2 release.
-----
- Tim
--
View this message in context: http://openejb.979440.n4.nabble.com/Availability-of-1-5-2-snapshots-tp4661139p4661238.html
Sent from the OpenEJB User mailing list archive at Nabble.com.