well I would have just produced the entity manager directly. Also
maybe check validation-mode in the persistence unit.
BTW do you care adding your code to this sample? (ie providing us a
formal patch in a TOMEE ticket)?
This way it will add at least a test for this issue
Romain Manni-Bucau
it is fixed now. Was the same without being the same ;) (not the same
call actually, I missed this one, sorry)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-10-02
Hi,
sure.
I'll just refurbish my example a little bit since the way I produce the EM
now, breaks all my manytomany persist invocations
br hw
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/deltaspike-fullstack-example-tp4672086p4672103.html
Sent from the TomEE
Hi Romain,
Just a small check with you before a start digging into DS and
entitymanager.
Container-managed entitymanager:
@PersistenceContext(unitName = ValidationPU)
private EntityManager entityManager;
@Produces
EntityManager createEntityManager() {
Hi!
I'm trying to understand how I can use @Inject to inject EJBs.
1. If I want to inject an EJB that is packaged in the WAR together with the
code trying to inject it i assume I can use @Inject, correct?
2. As 1 but the EJB is packaged in a separate ejb-jar. I assume I can still
use @Inject
Well I don't know exactly how EJB and CDI is managed internally by TomEE.
But using @Inject whatever the class is will mean that the lifecycle of
that instance will be managed by CDI container. On the other side if you
use @EJB the bean will be managed by EJB container, and this means EJB
Hi,
I am not sure about that Alex. I use @Inject only and Stateless and stuff is
working fine
Skickat från min iPhone
3 okt 2014 kl. 15:30 skrev Alex Soto asot...@gmail.com:
Well I don't know exactly how EJB and CDI is managed internally by TomEE.
But using @Inject whatever the class is
Basic rule these days is @inject local and use @EJB for remote beans. If in
doubt use @EJB. That gives you all transactional state guaranteed.
Andy
On 3 Oct 2014 06:31, Alex Soto asot...@gmail.com wrote:
Well I don't know exactly how EJB and CDI is managed internally by TomEE.
But using
Yes, I remember when I became TomEE user, I think Romain advised me that I
can use @Inject or @EJB. I decided to only use @EJB for EJBs and @Inject
for @SessionScoped, @ApplicationScoped, @RequestScoped beans.
On Fri, Oct 3, 2014 at 10:49 AM, karl.kil...@gmail.com wrote:
Hi,
I am not sure
That's right Howard. It's kind of a TomEE feature though. So what I blurted
above is the safe bet. Anything you can 'get' local @inject, inter-app or
inter-machine use @EJB
Andy.
http://www.tomitribe.com - @AndyGeeDe - On a mobile device, and I have fat
fingers. Sorry for typos.
On 3 Oct 2014
...or use @inject all over and produce your remotes :-)
br hw
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Regarding-Inject-vs-EJB-for-EJB-tp4672108p4672117.html
Sent from the TomEE Users mailing list archive at Nabble.com.
It is never late to know sth new. But then if this is TomEE specific your
are tight to TomEE and won t be able to run on wildfly fir example
El divendres, 3 octubre de 2014, hwaastad he...@waastad.org va escriure:
...or use @inject all over and produce your remotes :-)
br hw
--
View this
Well rule is simple: for @Stateless/@Singleton if CDI is enabled
(beans.xml) @Inject = @EJB. For @Stateful @Inject only makes sense
with a normal scope and here cdi handles the stateful lifecycle (no
need to call @Remove).
@EJB doesn't for for remote ejb excepted using TomEE specific feature
like
for all intents and purposes, as long as you're using @Local/@LocalBean
@Inject should work the exact same as @EJB, regardless of
SLSB/SFSB/Singleton. Obviously if you're in a Bean Archive you'll want to
give your SFSB a scope so that the containers work with it properly but
last time I tried
can be a lifecycle issue. You use the database during flushing right?
not sure it is good.
BTW updated
http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/deltaspike-fullstack/src/main/resources/META-INF/beans.xml
should be ok for you when using a JTA persistence unit
Romain Manni-Bucau
Our trunk sample uses jta and javax transactional, next step is to remove
manual repos
Le vendredi 3 octobre 2014, hwaastad he...@waastad.org a écrit :
OK,
what you said made me think of eclipselink flush mode.
by setting:
eclipselink.persistence-context.flush-mode=commit
It seems that
16 matches
Mail list logo
