[
http://jira.jboss.com/jira/browse/JBSEAM-3159?page=comments#action_12421092 ]
deanhiller commented on JBSEAM-3159:
------------------------------------
I would like to propose one MORE feature to make it even better...if possible, have it
open a new tab or window with the debug.seam page and have that page still go to the
original page that should be handling the exception(the error page or what not). I think
then, we get the best of both worlds :).
Debug/development mode control
------------------------------
Key: JBSEAM-3159
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3159
Project: Seam
Issue Type: Task
Components: Tools
Reporter: Pete Muir
Priority: Critical
Fix For: 2.1.0.BETA2
Currently we have a very overloaded system which is hard to use:
1) debug flag is used to control parsing of hot-deploy (/dev) which is odd
2) to view the debug page at all you must both include jboss-seam-debug.jar and enable
debug mode in components.xml. Further, if you do this, then the debug page handler is
installed, which screws with the exception handling.
I propose that by simply including jboss-seam-debug.jar you get
1) hot deployment enabled
2) use of the debug page by calling /debug.seam BUT not as a redirect off the exception
handler
and, further, by
<exception:exceptions enable-debug-page="true" /> (better ideas for
attribute name?)
you can automagically redirect to the debug page when an exception occurs. The default
for this is false, and this should be set in seam-gen (the seam-gen app should include a
link to debug.seam in perhaps its footer)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira