Well, there is nothing for TomEE currently AFAIK.
Then, I guess Antonio's (Goncalves) book is a good starting point.
You can also try to buy Adam's (Bien) ones. He just revisited and published
a new version few days ago.
Then, you can pay with all examples from OpenEJB/TomEE website.
The
After a lot of investigation I've found a problem here on forum. I was using
TomEE v1.0 with ActiveMQ client jar v5.5.1 which has some bug or whatever.
Everything works smoothly with latest Tomee v1.1 build.
There are no exceptions, however I am periodically checking logs for any
kind of related
Hi Fernando,
thanks for the review. The problem is related to loading and I think you
got the point, in fact I had the same interface for multiple implementation.
However, even changing this I had some stranger issues related to the fact
that it was not possible (due to classloading problems) to
A queue is maybe not the faster. If you manage to reproduce it in an hello
world i could have a look
Le 7 sept. 2012 19:33, Luca Merolla luca.mero...@gmail.com a écrit :
Hi Fernando,
thanks for the review. The problem is related to loading and I think you
got the point, in fact I had the same
I removed the queue as well. I basically did mange by using Infinispan as
cache and share some objects among the WAR and EJBs.
It should be much faster now.
On Fri, Sep 7, 2012 at 7:42 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote:
A queue is maybe not the faster. If you manage to reproduce
Oki,
I had a lot of conccurrency issues with IS but if it works for you thats
fine
Le 7 sept. 2012 19:56, Luca Merolla luca.mero...@gmail.com a écrit :
I removed the queue as well. I basically did mange by using Infinispan as
cache and share some objects among the WAR and EJBs.
It should be
I have multiple WARs that rely on the same depenency jar, which contains
EJBs, including the @LocalBean, @Local, and @Remote classes. One WAR is the
host for the EJB, the others use the remote interface via JNDI.
Using the default JNDI naming scheme, this cause conflicts when initializing
the
The ejb servlet in tomee webapp could fwd to another url the call, simply
split this servlet in two and it should be fine.
But today it is not done iirc
Le 7 sept. 2012 23:15, jiminitaur james.ar...@gmail.com a écrit :
I have multiple WARs that rely on the same depenency jar, which contains
I'm really interested about this question as well since there is a couple of
issues that have been fixed. (Hibernate, Grails...) Has someone an idea
about that?
--
View this message in context:
http://openejb.979440.n4.nabble.com/Next-TomEE-release-date-tp4657315p4657331.html
Sent from the
I think it's pretty critical to get a release out before JavaOne, which is just
weeks away.
Might be tricky, but I think we can do it.
-David
On Sep 7, 2012, at 4:01 PM, Jeremyau wrote:
I'm really interested about this question as well since there is a couple of
issues that have been
10 matches
Mail list logo
