that's the case, map rest endpoints with @ApplicationPath/web.xml and all will be fine
or set the system property openejb.jaxrs.application to false (but i rather advise you to fix the sub context used by rest part of your app) *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/5/2 OCal <[email protected]> > Hi, > > > Romain Manni-Bucau wrote > > any rest subclass of Application? if yes any @ApplicationPath or mapping > > of > > this class in the web.xml? if no that's normal, the rest servlet will be > > mapped to /* as the spec requires > > ... > > No subclass and entry in the web.xml. I just trimmed my application, there > is an .war file which shows the behaviors which helps in testing. That war > includes the sources. Also, here are the links: > > https://www.dropbox.com/s/16sk7lfg5mqpzlf/tomeetest.war > https://www.dropbox.com/s/0oov9hh2jwdq7ic/tomeetest.zip (Eclipse project) > > After deploying the war, one needs to do three things: > > 1. Check at startup about the datasource creation. There are some messages > in console with prefix ">>>>>>> " This happens in startup as implementation > of ServletContextListener > 1. Access localhost:8080/tomeetest > 2. Access localhost:8080/rest/test. By default html response will come. > > TomEE 1.5.1 : Everything works when ran from Eclipse. Standalone it fails > (just now discovered). > > TomEE 1.5.2 : #1 Datasource creation fails. Application undeploys. Both > Eclipse and standalone. > > TomEE 1.6.0 Snapshot: #1,3 works. #2 fails. It seems to map those JSF pages > to rest endpoints. Both Eclipse and standalone. > > Thanks. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Datasource-problem-with-TomEE-1-5-2-Works-in-1-5-1-tp4662607p4662658.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
