|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Okay it is in their, I missed that over the course of 30 mins, trying to figure out what I was doing wrong...can the class
scopes.web.UserSession be listed in the stack listing. It got lost for me in that long list. Like typical Java Stack traces I scanned the left hand side of the list looking for one of my classes. I did not see it in the list, as we just were throwing up internal classes. It would be nice if this was listed like:
15:05:47,093 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."jb225-lab-3-3.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jb225-lab-3-3.war".WeldService: org.jboss.weld.exceptions.DefinitionException: WELD-000072 Managed bean declaring a passivating scope must be passivation capable. Bean: Managed Bean [class scopes.web.UserSession] with qualifiers [@Any @Default]
at class scopes.web.UserSession
at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
Can that be done? or something else to make this easier to read and find for a normal user.