Drapierwim,
thank you for the very precise answer. It solves my problems too.
I just want to add. That you can simplify that was said in documentation
(7.4.2):
@PersistenceContext(type=EXTENDED)
|private EntityManager em;
|
Denis.
View the original post :
Thank you for your answers, i used the documentation path to solve my problem.
What is the difference, if there is any, between the documentation and the
simple (EXTENDED) solution?
Sincerely
Stefan
View the original post :
Take a look at the Seam reference documentation
chaperter: 7.4. Seam managed transactions
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3947357#3947357
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3947357
Ok I'm kind of stuck here... so I will do my best to explain.
I've read in the seam documentation the following
anonymous wrote :
| Seam completely solves the problem of unwanted
LazyInitializationExceptions, while working around the biggest problem in the
open session in view pattern. The
As long as you are injecting the Seam-managed EPC, and not an
EJB-container-managed EPC, and as long as you remain in a single conversation,
you will not get an LIE. It does not matter how many SFSBs you have. Of course,
as soon as you @End the conversation, you can get an LIE.
View the
[EMAIL PROTECTED] wrote : Have you set jboss.entity.manager.factory.jndi.name
in persistence.xml?
This is my entry in the persistence.xml
| property name=jboss.entity.manager.factory.jndi.name
value=java:/accountingEntityManagerFactory/
|
The value only references a context-param in my
I've found the problem the param-name was wrong in the web.xml instead of
accountingDatabase.persistenceUnitJndiName it schould be
entityManager.persistenceUnitJndiName.
But after a quick test I still got
| 08:58:03,473 ERROR [LazyInitializationException] failed to lazily
initialize a
Use
@In(create=true)
| EntityManager entityManager
For Seam-managed EMs.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3941728#3941728
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3941728
I've read the doc and made some changes... with no success
added in the web.xml
| context-param
|
param-nameorg.jboss.seam.core.init.managedPersistenceContexts/param-name
| param-valueaccountingDatabase/param-value
| /context-param
|
| context-param
Thanks to my servers log file and the issues example project I've come a step
closer.
Seems now I'm stuck with this
anonymous wrote : 2006-05-06 22:44:47,563 DEBUG
[org.jbpm.graph.def.GraphElement] executing action '#{accountsManager.find}'
| 2006-05-06 22:44:47,563 DEBUG
Have you set jboss.entity.manager.factory.jndi.name in persistence.xml?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3941701#3941701
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3941701
Sorry everyone,
I'm
a) too stupid
b) too tired...
When I get the @DataModelSelection for an EntityBean, I don't seem to have a
fully bound instance. This is why the generated code refreshes the entity with
merge(). A refresh() helps as well...
Goodnight,
Stefan
View the original post :
12 matches
Mail list logo
