Hi, DS doc specifies the use of BeanManagedUserTransactionStrategy in
beans.xml.
Should'nt that be enough?
..or containermanaged strategy?
br hw
--
View this message in context:
http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/JPA-doc-related-to-EM-Pro
waastad/TomeeDsValidation.git) and u'll see that
> validation fails if the entitymanager is produced like this.
>
> br hw
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/JPA-doc-related-to-EM-Prod
ils if the entitymanager is produced like this.
br hw
--
View this message in context:
http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/JPA-doc-related-to-EM-Producer-tp4658999p4659079.html
Sent from the Apache DeltaSpike Incubator Discussions mailing list archive at
Nabble.com.
return entityManagerFactory.createEntityManager();
> }
>
> with a little help from @romain i realized that my em's were resource_local
> using the producer shown in the DS docs.
>
> br hw
>
>
>
> --
> View this message in context:
> http://apache-
yManagerFactory.createEntityManager();
}
with a little help from @romain i realized that my em's were resource_local
using the producer shown in the DS docs.
br hw
--
View this message in context:
http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/JPA-doc-related-to
since we only provide documentation about deltaspike itself, it should be
clear implicitly.
some modules extend ee6/ee7 and therefore you will see a mix of java ee and
deltaspike by definition.
(BMT is a valid part of the spec. and therefore nothing special/separated.)
regards,
gerhard
2014-09-
On Thu, Sep 25, 2014 at 7:05 PM, Gerhard Petracek
wrote:
>
> please have a look at [1]. there you can see several differences compared
> to your demo.
> e.g. you don't have the TransactionalInterceptor in your beans.xml (see
> [2]). if you would like to use jta, please have a look at [3].
Hi Ger
hi claudio,
please have a look at [1]. there you can see several differences compared
to your demo.
e.g. you don't have the TransactionalInterceptor in your beans.xml (see
[2]). if you would like to use jta, please have a look at [3].
regards,
gerhard
[1]
https://github.com/jboss-developer/jboss
thx for providing the demo-application which illustrates the issue. i'll
have a look at it.
regards,
gerhard
2014-09-24 3:51 GMT+02:00 Claudio Miranda :
> On Mon, Sep 22, 2014 at 5:36 PM, Gerhard Petracek
> wrote:
> > that part of the documentation is based on demo-applications.
> > if someth
On Mon, Sep 22, 2014 at 5:36 PM, Gerhard Petracek
wrote:
> that part of the documentation is based on demo-applications.
> if something doesn't work for you, please provide a link to
> a demo-application which illustrates the issue.
See [1] for the demo application that reproduces the issue. Ther
hi claudio,
the injected entity-manager is already a proxy -> you can expose it as it
is.
that part of the documentation is based on demo-applications.
if something doesn't work for you, please provide a link to
a demo-application which illustrates the issue.
regards,
gerhard
2014-09-22 22:24
Hi, I was reading the jpa doc [1], and the recommendation to inject
the @PersistenceUnit to create an EM to produce it, the @Transactional
doesn't work, as the EM is BMT, the em.persist doesn't flush the
entity to table.
Also every emf.createEM invocation will create a new EM, looks like
the right
12 matches
Mail list logo