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" <james.mk.gr...@gmail.com> wrote:
> 404 not found. > > > > On 3 March 2013 19:46, Romain Manni-Bucau <rmannibu...@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" <rmannibu...@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" <james.mk.gr...@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 <rmannibu...@gmail.com> > > wrote: > > >> > > >> > Isnt it @ApplicationPath? > > >> > > > >> > @Path for an Application is not defined IIRC > > >> > Le 3 mars 2013 16:48, "James Green" <james.mk.gr...@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 <rmannibu...@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" <james.mk.gr...@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 < > > >> rmannibu...@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.blev...@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 < > > >> > > rmannibu...@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.gr...@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.blev...@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 > > >> > > > > >> > > >> > > > > >> > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > > > > >
