Re: ApplicationComposer and Deltaspike 1.0

Did you add deltaspike beans in app? Le 18 août 2014 09:33, hwaastad he...@waastad.org a écrit : Hi, I'm trying to get a test going using ApplicationComposer. However it fails with this: SEVERE - CDI Beans module deployment failed java.lang.IllegalStateException: Could not find beans for

tomee+hibernate+java8 possible?

Hello, we are using tomee 1.6 with hibernate 4.2. Now that 1.7 is out, we are interested to migrate to it, and start using the new java8 features. We are not sure which hibernate version introduced support for java8 (it turns out extremely difficult to come to that information...), so we

Re: Switching to Eclipselink in TomEE plus?

I missed this, but I see now that I too have this warning in my logs. For me it started appearing in the 1.7.0 release. It didn't occur in my 20140721 snapshot. Running Ubuntu 12.04.4 server, Java 1.7, eclipselink 2.4.2, Mysql. -- Bjorn Danielsson Cuspy Code AB Howard W. Smith, Jr.

Re: tomee+hibernate+java8 possible?

Hi If you add jpa 2.1 api replacing javee api jar by geronimo jar (javee api is just a shade of geronimos ones) it should work Le 18 août 2014 10:46, Emmanuel Touzery emmanuel.touz...@lecip-its.com a écrit : Hello, we are using tomee 1.6 with hibernate 4.2. Now that 1.7 is out, we are

Re: Switching to Eclipselink in TomEE plus?

Guys saying there is an issue is useless, we are still waiting to something to reproduce and at least a stack. Surely a path issue or jmx character issue. Le 18 août 2014 11:49, Bjorn Danielsson bjorn-apa...@lists.cuspycode.com a écrit : I missed this, but I see now that I too have this warning

Re: Switching to Eclipselink in TomEE plus?

Hi Romain, This was the only output I could find in the boot logs. Do you want a sample for this? I can just zip something up :-) On 18 August 2014 13:53, Romain Manni-Bucau rmannibu...@gmail.com wrote: Guys saying there is an issue is useless, we are still waiting to something to reproduce

Re: ApplicationComposer and Deltaspike 1.0

Hi, No I've not added any DS beans. Which beans are you thinking of? Just by adding core-api/core-impl(runtime) results in this error. br hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/ApplicationComposer-and-Deltaspike-1-0-tp4671240p4671247.html Sent from the

Re: Switching to Eclipselink in TomEE plus?

A github project would be awesome Le 18 août 2014 14:04, Karl Kildén karl.kil...@gmail.com a écrit : Hi Romain, This was the only output I could find in the boot logs. Do you want a sample for this? I can just zip something up :-) On 18 August 2014 13:53, Romain Manni-Bucau

Re: ApplicationComposer and Deltaspike 1.0

WindowBeanHolder? ;) AppComposer doesnt use classpath so you need to build the app yourself, even libraries Le 18 août 2014 14:32, hwaastad he...@waastad.org a écrit : Hi, No I've not added any DS beans. Which beans are you thinking of? Just by adding core-api/core-impl(runtime) results in

Re: ApplicationComposer and Deltaspike 1.0

Sure, I did inclusion while your reply was in the air :-) By extending and testing: return new Class?[]{TestService.class,WindowBeanHolder.class,WindowIdHolder.class,ConversationBeanHolder.class,ViewAccessBeanHolder.class,ViewAccessBeanAccessHistory.class,ViewAccessViewHistory.class}; OK, one

Re: Switching to Eclipselink in TomEE plus?

Can't get a stack trace, just the warning. But after peeking in the Eclipselink source code it seems clear the thing that is null is this variable, which is supposed to hold a platform-specific Eclipselink MBean: JMXServerPlatformBase.runtimeServicesMBean And adding this in

Re: Switching to Eclipselink in TomEE plus?

Are you setting the properties -Declipselink.register.run.mbean=true, or -Declipselink.register.dev.mbean=true If so then then you will require -Dcom.sun.management.jmxremote=true - This used to be on/true by default, but was removed from the release. Andy. On 18/08/2014 16:40, Bjorn

Re: Switching to Eclipselink in TomEE plus?

Andy, no I didn't modify any startup scripts. I tried adding -Dcom.sun.management.jmxremote=true just now and nothing changed. When I crank up eclipselink.logging.level the logs show that the eclipselink MBeanDevelopmentServices is registered, but the next mbean is null. That's the

Re: Switching to Eclipselink in TomEE plus?

Ok think I get i, that's a tomee bug. I'll try to fix it tonight Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-18 20:02 GMT+02:00 Bjorn Danielsson

Re: Switching to Eclipselink in TomEE plus?

https://issues.apache.org/jira/browse/TOMEE-1296 Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-18 20:15 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com: Ok

Re: ApplicationComposer and Deltaspike 1.0

did you add the producer? * DefaultConfigPropertyProducer BTW using arquillian (openejb embedded adapter) allows you to add deltaspike jars directly: http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/deltaspike-configproperty/src/test/java/org/superbiz/deltaspike/config/ConfigTest.java

Re: Switching to Eclipselink in TomEE plus?

Wow! That was fast ;-) Could you also please answer a stupid question: the bug only affected Eclipselink monitoring, am I correct here? Because I never saw any problems, just this strange warning. -- Bjorn Danielsson Cuspy Code AB Romain Manni-Bucau rmannibu...@gmail.com wrote:

Re: Switching to Eclipselink in TomEE plus?

yep you can also disable it setting openejb.eclipselink.jmx=false Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-18 20:33 GMT+02:00 Bjorn Danielsson

Re: Switching to Eclipselink in TomEE plus?

Romain is 'always' fast! :D On Mon, Aug 18, 2014 at 2:33 PM, Bjorn Danielsson bjorn-apa...@lists.cuspycode.com wrote: Wow! That was fast ;-)

Re: Switching to Eclipselink in TomEE plus?

Is this (openejb.eclipselink.jmx=false) added as part of the fix, or is openejb.eclipselink.jmx=false available in tomee 7.0 final release, already? On Mon, Aug 18, 2014 at 2:36 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: you can also disable it setting openejb.eclipselink.jmx=false

Re: Switching to Eclipselink in TomEE plus?

don't forget to add professionally ;) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-18 20:59 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com: Romain is

Re: Apache TomEE 1.7.0 Release

A huge thank you to everyone involved. I am using TomEE for all my projects and my customers' projects. Keep going with the great work. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Apache-TomEE-1-7-0-Release-tp4671162p4671260.html Sent from the TomEE Users

Re: Switching to Eclipselink in TomEE plus?

it is in 1.7 Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-18 21:00 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com: Is this (openejb.eclipselink.jmx=false)

Re: Switching to Eclipselink in TomEE plus?

okay, i just confirmed that with my app and tomee+ 1.7.0. i added the following to my java [startup] options -Dopenejb.eclipselink.jmx=false and i see the following in the log file: 2014-08-18 15:14:00 Commons Daemon procrun stdout initialized [EL Info]: 2014-08-18

Re: ApplicationComposer and Deltaspike 1.0

That's it. Thanks a lot!! I'm trying to keep away from arquillian as much as I can :-) Yeah, I checked: File[] libs = Maven.resolver().loadPomFromFile(pom.xml).resolve(org.apache.deltaspike.core:deltaspike-core-impl:1.0.1).withoutTransitivity().as(File.class); And its working fine. No, right

Re: ApplicationComposer and Deltaspike 1.0

well you can do the same (adding jar to be scanned) but: 1) you loose part of interest of AppComposer 2) it uses internal and we don't guarantee any stability on it Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau

Re: ApplicationComposer and Deltaspike 1.0

Hmm, have you got any example on using a resolver for app composer? I might take back my comments on arquillian. I just added omnifaces (or any other cdi enabled library) and the search for classes starts again..phew! br hw -- View this message in context:

Re: ApplicationComposer and Deltaspike 1.0

Well I don't use Maven resolver with AppComposer but JarLocation.jarLocation(AClassFromTheJar.class) which gives you the jar path and you can add it in AppModule as jars. We can think to add @Jars as we added @Classes Romain Manni-Bucau Twitter: @rmannibucau Blog:

Re: ApplicationComposer and Deltaspike 1.0

+1 for @Jars :-) I'll happily help testing :-) br hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/ApplicationComposer-and-Deltaspike-1-0-tp4671240p4671269.html Sent from the TomEE Users mailing list archive at Nabble.com.

Re: ApplicationComposer and Deltaspike 1.0

http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/test/java/org/apache/openejb/testing/AppComposerJarsTest.java Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: