[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3159) Debug/development mode control

[Dan Allen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Allen updated JBSEAM-3159:
------------------------------

    Fix Version/s: 2.2.0.CR1
                       (was: The future)
         Assignee: Dan Allen


> Debug/development mode control
> ------------------------------
>
>                 Key: JBSEAM-3159
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3159
>             Project: Seam
>          Issue Type: Task
>          Components: Tools
>            Reporter: Pete Muir
>            Assignee: Dan Allen
>            Priority: Critical
>             Fix For: 2.2.0.CR1
>
>
> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira