On your original problem - it's hard to suggest a solution based on the info available (not your fault, you've supplied everything available) without using a debugger - it could be due to having two datamodels in the same bean - have you tried with just one? Otherwise, get your debugger out and track down why you are getting that exception (and specifically on which datamodel it is occurring).
On your second problem - I'm not sure, perhaps try using page parameters instead? Sorry, not very helpful, but I'm no expert on the el enhancement stuff :(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039639#4039639
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039639
It's not the default behavior. The default behavior is to flush a persistence context (translation: dirty check objects, generate and execute SQL DML) when a transaction commits.
If you use Hibernate as your JPA provider, you can enable FlushModeType.MANUAL when you begin a conversation, so that the persistence context bound to that conversation is only flushed when you call entityManager.flush().
Please also read the Seam documentation, I'm basically quoting verbatim.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039633#4039633
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039633
"christian.bauer(a)jboss.com" wrote : Also note that system transactions and conversations are not related in a Seam application. These are independent contexts with a quite different scope. System transactions are short, conversations are potentially long-running and spanning several requests.
|
Suppose that you have a conversation and you don't want to persist your changes until that conversation has ended. I believe this is the default behavior.
How is this behavior related to transactions?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039631#4039631
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039631
Hey all,
Once again, I am pretty new to Seam and I am just barely scratching the surface right now. I am running Seam example successfuly with Tomcat 6 at the moment. My understanding is that jboss-app.xml file is only used for when you are deploying the app to a Jboss AS correct?
But seeing that to get Seam running in tomcat 6 there are all sorts of jar files that are needed, I am assuming this jboss-app.xml still functions the same as it does in a Tomcat 6 environment as it does with JBoss AS as a deployment server ? Hope my question makes sense. Bottomline do I need this file to make a seam project run on Tomcat 6?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039630#4039630
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039630