[jboss-user] [JBoss Seam] - Re: Seam Conversation Should Be Flexible but NOT

[petemuir]

anonymous wrote : 
  | * Maintaining the session timeout, say 30 minutes
  | 
  | * Maintaining the EJB3 timeout 
  | 

This is a pain:

http://jira.jboss.com/jira/browse/EJBTHREE-788

"app4you at yahoo.com" wrote : * Live development in Eclipse using Tomcat plug-in for quick monkey-do-monkey-see will crash Tomcat server.  If you modified a Java file then Tomcat will automatically updates the changes ====> crashed most of the time

I don't work with Tomcat, but I believe this is due to poor interaction between Eclipse and Tomcat.  This works fairly well with JBoss AS, and Max was talking to the guy who deals with who writes the hot-replacement for Eclipse to try and improve it.

anonymous wrote : * Conversation timer should be flexible to turn on/off.  Say if your application requires that the application form has to be in the edit mode all time unless user clicked on the Done button.  If you want to conversation to end at the same time as the http session timeout, then you have to set the conversation timeout to equal to the HTTP session timeout, 30 minutes,  you are asking for bog down - too many sessions.  Otherwise, say while the user is looking at the data report for 5 minutes then she tries to fix something on application entry form, boom!  Conversation is timed out, redirected to the home.faces.  This is bad!!!  Imagine that you have the tree and tab interfaces and the application has tons of modules, unless your application is simple like the Hotel demo app.

I don't quite get what you are after here.  You want to have it so that conversations can never timeout? Then it's just SESSION scope (but admittedly isolated)...  You can already achieve this effect by having a very very long conversation timeout.  Or are you after flexibility - giving different conversations different timeouts (you can currently do this programmatically, but not through xml/annotations)

anonymous wrote : * Seam's security is not sufficient enough to protect all the resources besides the component classes and the XHTML files, like the standard J2EE Form-based Authentication or ACEGI.  If ACEGI or custom filter is used, Seam's conversation stack will kick in (from my experience here) very unpredictable.

Can you file an issue for this (your underlying problem of not being able to protect resources, not the issues integrating other security solutions) :) 

Thanks for the feedback :)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038099#4038099

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038099