I did try to reference the seam-gen application, but it was a bit overwhelming. There was so many files generated, I had a hard time "seeing the forest from the trees". My hope was the EntityHome could save me alot of work for simple CRUD applications, but would I be better off using Session beans and the like instead of figuring out the EntityHome configuration? Anyone use the EntityHome in a produciton environement? Anyone know what the pros and cons are?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041213#4041213
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041213
I don't know specifically about your LoginModule, but to get the logged-in Subject onto the SecurityAssocation stack we need to have two login modules, one is our own custom one, and the other is the JBoss ClientLoginModule. It is the ClientLoginModule that pushes the Subject onto the SecurityAssociation stack upon commit(), and pops on logout() and abort(). Note - make sure that you set restore-login-identity to true for the ClientLoginModule otherwise you get strange behaviour upon cache timeout.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041209#4041209
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041209
As far as I am aware, it isn't possible. The JBoss caching mechanism doesn't/can't distinguish between where the authentication request comes from - e.g. a new browser session vs. new page request vs. EJB call. You can try setting the timeout to 1 second, which would effectively force every page request to hit the LoginModule again, or to 0 seconds which would cause every authentication request (including EJB calls) to hit the login module.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041203#4041203
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041203