Re: Packaging advice

just remove the listener and it works *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/3

Re: Packaging advice

Yeah I think this is where I am coming unstuck with portability. See http://stackoverflow.com/questions/15156171/glassfish-web-xml-servlet-mapping-to-webservice-gets-classcastexceptionfor the problem I was having declaring jaxws services in web.xml portably. Without shipping a jaxws implementatio

Re: Packaging advice

Jaxrs and jaxws are for sure but for jaxws you need to map them in web.xml Le 5 mars 2013 22:56, "James Green" a écrit : > The only producers I have our POJO Factories for my Mongo DAOs. They all > @Inject an @ApplicationScoped datasource which itself holds the Mongo > client connection. > > So w

Re: Packaging advice

The only producers I have our POJO Factories for my Mongo DAOs. They all @Inject an @ApplicationScoped datasource which itself holds the Mongo client connection. So web-tier.war depending-on service-tier.jar depending-on persistence-tier.jar each with beans.xml. Should I expect JAX-RS and JAX-WS

Re: Packaging advice

Yes a jar without a beans.xml is not a cdi one. About webservices maybe you hit the fact a pojo one (not ejb) should be defined in web.xml. finally you are right about pooling (but a lot of mongo stuff is thread safe. Producers with scopes (reauest?) can be another answer Le 5 mars 2013 22:13, "Jam

Re: Packaging advice

I only added @Stateless to my @WebService classes because of deployment errors in TomEE. They worked fine in Glassfish. Figured perhaps CDI wasn't as mature in TomEE? Didn't realise beans.xml had to go into each jar. Will add. If I'm reading this right, POJOs @Injected into a SLSB will share the

Re: Packaging advice

Hi It works, ensure you have a beans.xml in each jar + about annotations check your need but @applicationscoped is tempting. Finally sharing your exception can help too Le 5 mars 2013 21:39, "James Green" a écrit : > I've spent the past year developing a Java EE 6 application with JAX-RS and >