Re: Using tomee quartz causing job not found exception

2013-05-17 Thread Romain Manni-Bucau
We worked on classloading on trunk, issues are welcomed ;) Le 17 mai 2013 03:09, splazit i...@ssosol.com a écrit : I think the major issue with tomee (at least w/ version 1.5.x) is the class loading issue. I've been playing w/ both Jboss AS 7 and Tomee and Jboss AS 7 is definitely better in

Re: initialize-in-order in application.xml is not honored

2013-05-17 Thread Romain Manni-Bucau
Maybe try to reproduce it? Le 17 mai 2013 03:09, splazit i...@ssosol.com a écrit : Hi Romain, Thanks for the reply. Unfortunately, I cant' share the file w/ you. I'm pretty sure that the ear structure complies to J2EE standards and it's currently running fine in Jboss AS 7. I did not change

EJBContainer No provider definition found

2013-05-17 Thread Caroline
Hi, Romain already helped me tremendously on http://openejb.979440.n4.nabble.com/Location-of-jar-bean-so-it-s-seen-by-CDI-td4662777.html. I tried to have CDI look for newly added .jars after deployment. I understand now that's not what CDI does. However, I need to build in this scanning for .jars

Re: EJBContainer No provider definition found

2013-05-17 Thread John D. Ament
Just to have a little better context, you want to go from your local tomee instance to a remote OpenEJB instance running in a separate JVM? On Fri, May 17, 2013 at 7:08 AM, Caroline caroline.van.den.ha...@gmail.comwrote: Hi, Romain already helped me tremendously on

Re: EJBContainer No provider definition found

2013-05-17 Thread Caroline
@Romain: 1) Ok i fixed my pom.xml 2) I see. I apologize for not having a clue (yet). I replaced the body of refreshEJB() with: AreeInput input = (AreeInput) new InitialContext().lookup(java:comp/env/plaininput); and annotated the PlainInput as: @Stateless @EJB(beanInterface = AreeInput.class,

stand alone Application looks up remote EJB by global jndi name

2013-05-17 Thread ZhongGuan
Hi i met a problem in Tomee+ 1.5.1 When I use a stand alone Application to lookup the remote EJB by global jndi name in EJB3.1 (java:global, java:app, java:module), it always fails. It succeeds When I use the same global jndi name to lookup a local EJB (in a local EJBClient). so the jndi name

Re: stand alone Application looks up remote EJB by global jndi name

2013-05-17 Thread Romain Manni-Bucau
Hi i guess it is fixed on trunk (1.6.0-SNAPSHOT) after discussion with the Expert Group (EJB spec guys) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn:

Re: EJBContainer No provider definition found

2013-05-17 Thread Caroline
I used your simple-webservice example to produce an example where I'm looking for a PlainInput that is in one of the packages. Eventually I will want to load a .jar from my local TomEE. https://www.dropbox.com/s/c9wc0grl4reqolz/simple-rest.zip?v=1rw- Op vrijdag 17 mei 2013, om 13:59 heeft

Re: EJBContainer No provider definition found

2013-05-17 Thread Romain Manni-Bucau
you forgot to add PlainInput in @Classes in the test @Classes({ GreetingService.class, PlainInput.class }) then you get this warning: WARNING - Unresolved ejb reference java:comp/env/plaininput with ejb-link beanPlainInput in bean PlainInput. Will attempt resolution again at runtime. then i

Re: EJBContainer No provider definition found

2013-05-17 Thread Romain Manni-Bucau
PS: @Stateless(name = beanPlainInput) @EJB(beanInterface = AreeInput.class, beanName = beanPlainInput, name = plaininput) works too *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/

Re: EJBContainer No provider definition found

2013-05-17 Thread Romain Manni-Bucau
FYI https://issues.apache.org/jira/browse/OPENEJB-2025 hope it helps your case *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:

Re: EJBContainer No provider definition found

2013-05-17 Thread Romain Manni-Bucau
You can't update on the fly dropping jar in a war (wouldnt mean anything seems app is linked at startup). Not sure what you expect here but maybe have a look to jrebel or fakereplace. If you want just autodeploy an app (not a part of app) we have it now through deployments config in tomee.xml or

Re: EJBContainer No provider definition found

2013-05-17 Thread Caroline
I have a web application which provides an interface A. Upon receiving a request from a client, with implementation names in it, I want my web application to look in a certain folder /my/folder/*.jar on my TomEE for these implementations to interface A. Then, I want my web application to use

Re: EJBContainer No provider definition found

2013-05-17 Thread Romain Manni-Bucau
In java only OSGi could do it but you ll loose a lot of the simplicity you have ATM Maybe just using a custom spi with your own loader would be enough but i really doubt of the use case (+ i think it should be forbidden in prod) Le 18 mai 2013 01:06, Caroline caroline.van.den.ha...@gmail.com

Re: EJBContainer No provider definition found

2013-05-17 Thread Caroline
Is the location where I expect these .jar's the restricting factor, or is it the fact that I want to load .jar's that were added after deployment time? I can't use OSGi. By custom SPI you mean Service Provider Interface and by own loader you mean an implementation of Tomcat WebappClassLoader?