[
https://jira.jboss.org/jira/browse/JBIDE-3383?page=com.atlassian.jira.plu...
]
Francisco Jose Peredo Noguez updated JBIDE-3383:
------------------------------------------------
Description:
As I start to build more complex .page.xml files with lots of rules, if-outcomes, and
redirects with params, I start to find it hard to debug them.
If a page.xml file does not do what I expect, I can not put a breakpoint inside a rule to
see if the navigator entered it, or a inspect/watch to see what is the value of a
particular EL expression during navigation.
was:
As I start to build more complex .page.xml files with lots of rules, if-outcomes, and
redirects with params, I start to find it hard to debug them.
If they do not do what I expect, I can not put a breakpoint inside a rule to see the
navigator entered it, or a watch to see the value of a particular EL expression during has
the value I expect.
Navigation debugging/inspect: Debugger for .page.xml files
----------------------------------------------------------
Key: JBIDE-3383
URL:
https://jira.jboss.org/jira/browse/JBIDE-3383
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Francisco Jose Peredo Noguez
As I start to build more complex .page.xml files with lots of rules, if-outcomes, and
redirects with params, I start to find it hard to debug them.
If a page.xml file does not do what I expect, I can not put a breakpoint inside a rule to
see if the navigator entered it, or a inspect/watch to see what is the value of a
particular EL expression during navigation.
--
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