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

use openejb/Resource name instead of shortname? *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau*

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

So if everything seems ok, is there a way to turn off auto-linking of the queues? -Original Message- From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] Sent: Wednesday, 9 October 2013 1:28 PM To: users@tomee.apache.org Subject: RE: JMS Queues auto-linking to beans that don't need th

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

Hmm, sounds ok since openejb/Resource is our internal prefix for queues. Do you have any issue? Le 9 oct. 2013 07:23, "Adam Steen" a écrit : > Hi Romain > > None of the beans reference the queue using a @Resource. > > Not sure I follow what you mean by "same in xml"? but I specify all my > resou

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

Hi Romain None of the beans reference the queue using a @Resource. Not sure I follow what you mean by "same in xml"? but I specify all my resources in the resources.xml file. The queue as specified as follows The MDBeans reference the queues via an "activation-c

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

Hi You dont use @Resource or same in xml? Le 9 oct. 2013 04:34, "Adam Steen" a écrit : > Hi > > When we start up our app recently ported to Tomee, we get the following > information in our log repeated for all the beans we have, but > > 2013-10-09 10:26:00 INFO org.apache.openejb.config.Auto

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

Hi When we start up our app recently ported to Tomee, we get the following information in our log repeated for all the beans we have, but 2013-10-09 10:26:00 INFO org.apache.openejb.config.AutoConfig processResourceRef Auto-linking resource-ref 'openejb/Resource/FPeJobs/TaskQueue' in bean

Re: Disable/Enable MDB

Thx Em 08/10/2013 17:30, "Romain Manni-Bucau" escreveu: > > Systeminstance.get().getcomponent(containersystem.class).getbeancontext(ejbname).getcontainer() > i think > Le 8 oct. 2013 20:19, "Leonardo K. Shikida" a écrit : > > > Hi Romain > > > > where should I look first in the internals? :-) >

Re: Disable/Enable MDB

Systeminstance.get().getcomponent(containersystem.class).getbeancontext(ejbname).getcontainer() i think Le 8 oct. 2013 20:19, "Leonardo K. Shikida" a écrit : > Hi Romain > > where should I look first in the internals? :-) > > TIA > > Leo > > > > > [] > > Leo > > > On Tue, Oct 8, 2013 at 2:15 PM,

Re: Disable/Enable MDB

Hi Romain where should I look first in the internals? :-) TIA Leo [] Leo On Tue, Oct 8, 2013 at 2:15 PM, Romain Manni-Bucau wrote: > Hi > > You can do it with our internals but it is risky for your app. Isnt it a > design issue? > Le 8 oct. 2013 18:48, "Leonardo K. Shikida" a écrit : >

Re: Disable/Enable MDB

Hi You can do it with our internals but it is risky for your app. Isnt it a design issue? Le 8 oct. 2013 18:48, "Leonardo K. Shikida" a écrit : > Hi > > Is there any way to disable/enable a MDB programmatically? > > Right now, it consumes from a JMS queue and the queue definitions are coded > us

Disable/Enable MDB

Hi Is there any way to disable/enable a MDB programmatically? Right now, it consumes from a JMS queue and the queue definitions are coded using @ActivationConfigProperty. if I just set a flag in the database and let the MDB check it before executing the onMessage() message, I guess I'd have to re

Re: Apache TomEE 1.6.0-SNAPSHOT - web-fragment.xml UnmarshallException

pushed sthg about, not sure it is it since i didn't reproduce but saw something very weird (surely a typo due to IDE completion) *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn:

Re: Apache TomEE 1.6.0-SNAPSHOT - web-fragment.xml UnmarshallException

Right, I have this: https://github.com/jieryn/web-fragment-example But it works, much to my surprise and sadness. Would it be useful if the mergeWeb would print out the web-fragment.xml it is processing if there is an error? I think this will be more useful as more people take increasing advantag

Re: 1.6.0 release plans?

Technically yes, then the issue is we need somebody with all perms to release tomee (ping @David?). *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/r

Re: 1.6.0 release plans?

@Romain, not sure to understand the details, but do you mean you may have a way to release TomEE+ 1.6.0 official release without waiting for the (unknown) OpenJPA 2.3.0 release? Thanks, Alex On Tue, Oct 8, 2013 at 4:55 PM, Romain Manni-Bucau wrote: > I meant forking it for the release "as usual

Re: 1.6.0 release plans?

I meant forking it for the release "as usual", not using a snapshot which wouldn't be professional *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rm

Re: Apache TomEE 1.6.0-SNAPSHOT - web-fragment.xml UnmarshallException

Hi it doesn't reproduce creating a project with a dependency of the same kind (jar) with a web-fragment? *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.co

Apache TomEE 1.6.0-SNAPSHOT - web-fragment.xml UnmarshallException

I'm using Apache TomEE 1.6.0-SNAPSHOT from October 8th. I have seen these errors for a while now, but am not able to reproduce it in a sample project. I have a lot of WEB-INF/lib/blah.jar files which contain META-INF/web-fragment.xml files which configure the system modularly. At start up, I see th

Re: 1.6.0 release plans?

Possible, but I would only release TomEE itself not all modules to avoid depending on a snapshot. TomEE is different because if the snapshot is available during the build, which is obviously the case, we can embedded the JAR file in the zip file. JLouis 2013/10/8 Romain Manni-Bucau > technical

Re: 1.6.0 release plans?

technically it is possible *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/8 Alex Th

Re: 1.6.0 release plans?

Otherwise, can a TomEE 1.6.0 official release be make with a snapshot OpenJPA 2.3 ? I'm concerned if we have no visibility Thanks, Alex On Tue, Oct 8, 2013 at 2:46 PM, Romain Manni-Bucau wrote: > Would mean reverting some code in openejb + forking openwebbeans and update > the code + accepti

Re: 1.6.0 release plans?

Would mean reverting some code in openejb + forking openwebbeans and update the code + accepting to not work in some cases in java 7...so I don't think so. *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/*

Re: 1.6.0 release plans?

>From OpenJPA's web site: = The 2.x releases (2.2.2 is the latest) are a production ready, compliant implementation of the JSR-317 Java Persistence 2.0

Re: 1.6.0 release plans?

@Alex: 2.3.0, there are working on it but want to address few blocking issues before AFAIK *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibuca

Re: 1.6.0 release plans?

@Romain: which OpenJPA release are you waiting to make TomEE 1.6.0 generally available, and what is this OpenJPA release's schedule? Thanks, Alex On Tue, Oct 8, 2013 at 11:01 AM, zmirc wrote: > I would really want to know that, too. > > > > -- > View this message in context: > http://openejb.9

Re: 1.6.0 release plans?

I would really want to know that, too. -- View this message in context: http://openejb.979440.n4.nabble.com/1-6-0-release-plans-tp4665437p4665447.html Sent from the OpenEJB User mailing list archive at Nabble.com.

Re: 1.6.0 release plans?

Hi I don't have all the keys to release (and we need it too here) but 1 month means no RC/beta (which is not an issue). ATM only OpenJPA release is really blocking us. *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/*

Re: 1.6.0 release plans?

+1, we also need in my company an official TomEE 1.6.0 "Generally Available" release (i.e., not Snapshot release), no later than mid-november ; so I guess beta/rc should start ASAP this month. @TomEE team, is this schedule possible? thanks, Alex On Mon, Oct 7, 2013 at 9:50 PM, Jim Ancona wro

Re: Apache TomEE 1.6.0-SNAPSHOT -- NPE

It works. Thanks! On Tue, Oct 8, 2013 at 12:55 AM, Romain Manni-Bucau wrote: > Hi > > 2 oct is too old ;). Joke apart it should be fixed. > Le 8 oct. 2013 02:31, "jieryn" a écrit : > >> 07-Oct-2013 20:25:11.822 SEVERE [localhost-startStop-1] >> org.apache.openejb.observer.ObserverManager.fireEve