[ http://issues.apache.org/jira/browse/JS2-341?page=all ]
David Sean Taylor updated JS2-341:
----------------------------------
Fix Version: 2.0-POST
(was: 2.0-FINAL)
Version: 2.0-POST
(was: 2.0-M4)
(was: 2.0-FINAL)
This one wont make it into 2.0 release
> Add State to Jetspeed Engine for Error Conditions
> -------------------------------------------------
>
> Key: JS2-341
> URL: http://issues.apache.org/jira/browse/JS2-341
> Project: Jetspeed 2
> Type: New Feature
> Components: Components Core
> Versions: 2.0-POST
> Reporter: David Sean Taylor
> Assignee: David Sean Taylor
> Fix For: 2.0-POST
>
> This feature addresses a 'user experience' problem: displaying stack traces
> to the end user. For example, If I change my database connection to a bad
> setting, and then try to hit the portal, I get this in my browser:
> javax.servlet.ServletException: Failed to initalize jetspeed.
> org.apache.jetspeed.exception.JetspeedException: Unable to create Engine
> org.apache.jetspeed.engine.JetspeedServlet.doGet(JetspeedServlet.java:206)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> Ugly.
> I propose that the Jetspeed engine always completes initialization, even on
> error conditions. The engine will have 'state' attribute to determine if the
> engine is running or in
> engine.getState()
> returning states such as RUNNING, INITIALIZING, DOWN, ERROR
> Then a valve can check the engine state, and redirect to servlet pages based
> on the state, or pass thru on the RUNNING state.
> This leads to an interesting challenge: what if the database comes up?
> Should we just restart the app server?
> Thats certainly the easiest solution.
> A retry thread would be another solution
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
