I do not have any problems with seam gen at all. But the deployment to Jboss failed with the above mentioned bug. By reading about JPA annotation with JEE 5.0 and Hibernate, I asked myself the same question. Why does it not work? Maybe: I am using jboss-4.2.0.GA and jboss-4.2.0.GA that comes with different Hibernate version than the one comes with jboss-seam-2.0.0CR2 (hibernate version 3.2.5)
How can I check hibernate version that comes with jboss-4.2.0.GA?
Thanks,
-b
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093659#4093659
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093659
I think you're confusing "maxSession" with "maxMessages". "maxSession" controls the number of concurrently operating threads. The pool size controls the number of MDB object instances created and pooled by JBoss. This pool size should be larger than the number of concurrent threads, otherwise the threads get blocked.
Anyway, you probably don't need to worry about messing with these settings in EJB3, unless there's some performance issue you're dealing with.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093655#4093655
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093655
Good afternoon,
Does anyone know the difference between session timeout and not logged in yet? It is easy to configure my application to redirect to the login page using attribute login-view-id of pages.xml for both scenarios.
However, I want to display a message like "You session times out. Please login again" for the first session timeout scenario to differ from the second not logged in scenario.
Is there a way that I can approach this in Seam? Thank you very much for your help.
Regards,
Sheng
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093654#4093654
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093654