Re: Liquibase datasource problem

Hi what's the issue? do you rely on jndi? mybe prefix the name by openejb:Resource/id of the datasource Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/20 Hildeberto

Re: WARNING: Injection data not found in JNDI context

Right, it really does not get any simpler than this: https://github.com/jmkgreen/test-multi-module I even accept it may not actually have met minimum requirements yet! The log: INFO: Deployed Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp) Nov

Re: WARNING: Injection data not found in JNDI context

Hi just debugged a bit and it only works for ejb ATM Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/20 James Green james.mk.gr...@gmail.com: Right, it really does

Re: WARNING: Injection data not found in JNDI context

I added @Stateless to the web service and indeed warning solved. So I added it to web.xml to resolve my original (business) problem of wanting versioned urls - and the warning comes back. What do I need to do then? I have updated the source project on github to reflect this. On 20 November

Re: Can't run tomee 1.6.0 from eclipse indigo (but could run from 1.5.2)

Hi Romain yes, the app uses quartz and activemq, both persistent my application.properties at WEB-INF org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreCMT org.quartz.jobStore.dataSource=quartzDS org.quartz.jobStore.nonManagedTXDataSource = quartzDS2

Re: WARNING: Injection data not found in JNDI context

Hi I'll fix the pojo issue but you can configure urls in openejb-jar.xml: http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/change-jaxws-url/src/main/resources/META-INF/openejb-jar.xml Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn:

Re: WARNING: Injection data not found in JNDI context

FYI https://issues.apache.org/jira/browse/TOMEE-1081 Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/20 Romain Manni-Bucau rmannibu...@gmail.com: Hi I'll fix the

Re: WARNING: Injection data not found in JNDI context

That works. Do you have a JIRA ticket I can watch? Thanks for your time on this - we appreciate it! On 20 November 2013 10:51, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi I'll fix the pojo issue but you can configure urls in openejb-jar.xml:

Re: WARNING: Injection data not found in JNDI context

Is there an issue covering the lack of support when exposed via web.xml? On 20 November 2013 11:06, Romain Manni-Bucau rmannibu...@gmail.com wrote: FYI https://issues.apache.org/jira/browse/TOMEE-1081 Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/

Re: WARNING: Injection data not found in JNDI context

How should I write the config for multiple EJBs? Adding extra session elements results in none applying and I cannot spot an example. On 20 November 2013 11:11, James Green james.mk.gr...@gmail.com wrote: Is there an issue covering the lack of support when exposed via web.xml? On 20

Re: WARNING: Injection data not found in JNDI context

Actually it's now uberwar creating problems - ignore me :) On 20 November 2013 11:45, James Green james.mk.gr...@gmail.com wrote: How should I write the config for multiple EJBs? Adding extra session elements results in none applying and I cannot spot an example. On 20 November 2013 11:11,

Re: Can't run tomee 1.6.0 from eclipse indigo (but could run from 1.5.2)

You put quartz in the webapp? (WEB-INF/lib?) You can workaround it forcing org.quartz.jobStore.driverDelegateClass to something else than org.quartz.impl.jdbcjobstore.StdJDBCDelegate btw if you can reproduce it in a runnable sample (mvn tomee:run) it would help us to analyze it further. Romain

Re: Can't run tomee 1.6.0 from eclipse indigo (but could run from 1.5.2)

Hi Romain No I did not put quartz in webapp, I am using tomee's quartz let me try the workaround thanks Leo [] Leo On Wed, Nov 20, 2013 at 10:16 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: You put quartz in the webapp? (WEB-INF/lib?) You can workaround it forcing

openejb-javaagent missing from service.bat

Hi! I have to setup TomEE on a windows server as a service. The creation of the service went well with bin/service.bat. After deploying my application i've realized entity weaving is stopped to work. After changing update.bat to appeng openejb-javaagent to the jvm options, and regenerate the

Re: Can't run tomee 1.6.0 from eclipse indigo (but could run from 1.5.2)

BTW the error is still weird so if you have few minutes to try to share sthg helping us to find if we have a bug or not it would still be appreciated Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github:

Re: openejb-javaagent missing from service.bat

Hi I don't think so (we don't have much windows dev here so surely something not seen), please just open a jira and attach a patch, we'll be happy to apply it Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github:

Re: openejb-javaagent missing from service.bat

Thanks! Issue #TOMEE-1082 2013/11/20 Romain Manni-Bucau rmannibu...@gmail.com Hi I don't think so (we don't have much windows dev here so surely something not seen), please just open a jira and attach a patch, we'll be happy to apply it Romain Manni-Bucau Twitter: @rmannibucau Blog:

JMS Topic clientId setting via configuration

Hi! I'm facing the problem that topic MDBs in a TomEE cluster both get same (activeMQ) clientid (the class name of the MDB I suppose). I know of MDB activation config property client id. If it is set to a specific value for a MDB, the jar containing the MDB cannot be shared among cluster nodes.

Re: JMS Queues auto-linking to beans that don't need them

I am seeing similar logging as above, but not openejb/Resource: Nov 20, 2013 8:55:38 PM org.apache.openejb.config.AutoConfig processResourceRef INFO: Auto-linking resource-ref 'java:comp/env/uk.co.mns.mdb.MessagePoster/connectionFactory' in bean TestSingleton to

Re: JMS Queues auto-linking to beans that don't need them

Well using lookup or some other options you can avoid it but this is not an issue at all. It auto links correctly cause your conf is ok Le 20 nov. 2013 22:32, mark silcox msil...@gmail.com a écrit : Yes, same output. On 20 November 2013 21:27, Romain Manni-Bucau rmannibu...@gmail.com wrote:

Re: Can't run tomee 1.6.0 from eclipse indigo (but could run from 1.5.2)

I´ll just try to make it work with 1.6.0 (deadlines are tight) and then I´ll create a nice small project and try to reproduce the problem. I´ve found another problem, but it seems to be JPA specific, so I´ve sent to their list. BTW, what openJPA version is used in tomee 1.6.0? I could not find

Re: Can't run tomee 1.6.0 from eclipse indigo (but could run from 1.5.2)

Oh Sorry @MappedById was proposed in the first draft of JPA 2.0 and then renamed to @MapsId TIA Leo [] Leo On Wed, Nov 20, 2013 at 11:21 PM, Leonardo K. Shikida shik...@gmail.comwrote: I´ll just try to make it work with 1.6.0 (deadlines are tight) and then I´ll create a nice small