Details
-
Type:
Feature Request
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 3.1.0.Tracking
-
Component/s: UI Components
-
Labels:None
Description
The return of the s:debug that never really got completed in Seam 2 
A <s:debug/> tag that can be dropped in a page and you can bring up a display of what's in the context, the active Seam config, perhaps even some performance numbers for the page, security stuff, persistence stuff.
The ability to add custom facets in this for displaying own data is nice, too.
Gliffy Diagrams
Issue Links
- is blocked by
-
JBSEAM-655
Control log levels from debug page
-
- Open
-
- is related to
-
JBSEAM-987
Debug page improvements
-
- Open
-
-
JBSEAM-3458
UI control for in-page real-time viewing debug info on conversations, context contents, credentials etc
-
- Open
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Please see JBSEAM-987 for various proposals that we received to improve the debug page in Seam 2. This should provide a starting point on how to design this page.
The idea is that we offer a page similar in spirit to phpinfo() (if you are a PHP developer, you know what I am talking about). Nothing beats helping the developer like giving them loads of information to inspect But it should also be simple on the surface for the day-to-day user.
Dan Allen
added a comment - Please see JBSEAM-987 for various proposals that we received to improve the debug page in Seam 2. This should provide a starting point on how to design this page.
The idea is that we offer a page similar in spirit to phpinfo() (if you are a PHP developer, you know what I am talking about). Nothing beats helping the developer like giving them loads of information to inspect But it should also be simple on the surface for the day-to-day user. JBSEAM-3458 is the issue that has the actual mockup.
Linking to a request to control log levels on debug page, JBSEAM-655.
Given how many possibilities there are here, I'm seeing the need for a separate component in JIRA to track debug information screens.
Discussed on IRC - http://echelog.matzon.dk/logs/browse/seam-dev/1313013600
Cody Lerum
added a comment - Discussed on IRC - http://echelog.matzon.dk/logs/browse/seam-dev/1313013600 To display the list of all active beans:
- create a CDI extension that stores all the javax.enterprise.inject.spi.Bean of all @Named classes.
- This is done with the method:
- public <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> event) {
- at render time, loop through all the Beans, and determine which are currently active
- Object o = beanManager.getContext(bean.getScope()).get(bean)
- o is null if there are no active instances
Brian Leathem
added a comment - To display the list of all active beans:
create a CDI extension that stores all the javax.enterprise.inject.spi.Bean of all @Named classes.
This is done with the method:
public <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> event) {
at render time, loop through all the Beans, and determine which are currently active
Object o = beanManager.getContext(bean.getScope()).get(bean)
o is null if there are no active instances
Sounds good – do you see the feature behaving somewhat like this? https://javaserverfaces.dev.java.net/nonav/docs/2.0/pdldocs/facelets/