Re: Location of jar bean so it's seen by CDI

it is redeployed every nights normally so try it again today with maven and it should be fine *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannib

Re: Location of jar bean so it's seen by CDI

Great!! Where can I get my hands on this? Not the 1.6.0-SNAPSHOT I can get from the website, apparently. On Sunday 12 May 2013 at 22:51, Romain Manni-Bucau [via OpenEJB] wrote: > was it :) > > https://issues.apache.org/jira/browse/TOMEE-928 > > *Romain Manni-Bucau* > *Twitter: @rmannib

Re: Set exception mappers for global scope in tests

@classes defines classes of your app. Mappers are loaded with rhis classloader in one case not in the other. Globally if you think to cdi classes contains all cdi classes (app classloader) Le 12 mai 2013 23:43, "Chris.Christo" a écrit : > Cool, that worked, I don't understand why though? > > The

Re: Set exception mappers for global scope in tests

Cool, that worked, I don't understand why though? The whole point of me moving the property definition for exception mappers at the @Config level is so I can I have some generic pre configured test class which all tests can subclass. This pre configured test class would have some generic method

Re: Set exception mappers for global scope in tests

take care using @Classes you specify explicitely the "application classpath" so use: @Classes({ GoodExceptionMapper.class, BadExceptionMapper.class, ExampleRest.class, ExampleService.class }) *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibuc

Re: Location of jar bean so it's seen by CDI

was it :) https://issues.apache.org/jira/browse/TOMEE-928 *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/r

Re: asynch listener

If you inject the sessioncontext in an ejb no worry if ut works but sthg can be wrong/not as fine as it could Le 12 mai 2013 16:47, "hwaastad" a écrit : > Hi, > I have a logging bean (@Observes) annotated with: > @Asynchronous > @Stateless > > The class injects > @Resource Sessioncontext > > It w

asynch listener

Hi, I have a logging bean (@Observes) annotated with: @Asynchronous @Stateless The class injects @Resource Sessioncontext It works fine in the last 1.6.0 snapshot (today) and I get the correct principal, however the logs are showing: -- WARNING: Injection data not found in JNDI context: jndiNam

Re: Location of jar bean so it's seen by CDI

Sure, I'm not opposed to sharing my big project, but for simplicity's sake: http://cl.ly/1C2H1s2K0G0q is JSONIssue.zip, a Netbeans Maven Java EE Project. I'm deploying it to TomEE 1.6.0-SNAPSHOT. Requesting http://localhost:8080/JSONIssue/generic using a browser generates a JSON output via a

Re: Location of jar bean so it's seen by CDI

Hmm, Wonder if classifier are well handled... Can you share a project to reproduce it please? Le 12 mai 2013 11:45, "Caroline" a écrit : > Thanks Romain for the clear instructions. I am another big step closer to > using this in my master thesis. > > Is there a known issue with > > WARNING: Exc

Re: Location of jar bean so it's seen by CDI

Thanks Romain for the clear instructions. I am another big step closer to using this in my master thesis. Is there a known issue with WARNING: Exception in handleFault on interceptor org.apache.cxf.binding.xml.interceptor.XMLFaultOutInterceptor@1c9598c0 org.apache.cxf.interceptor.Fault: net/s