[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-2149) More informative error messages

jaikiran pai (JIRA) jira-events at lists.jboss.org
Sat Aug 14 10:45:12 EDT 2010


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

jaikiran pai resolved EJBTHREE-2149.
------------------------------------

    Component Fix Version(s): jboss-ejb3-core:1.5.0
               Fix Version/s: depchain-1.0.0
                  Resolution: Done


The error message for this specific error will now contain the ejb name and the ejb class name. 

As for applying it to all such exceptions, that has to be taken up on a case by case basis. If you find any similar issues, feel free to create a JIRA.
 

> More informative error messages
> -------------------------------
>
>                 Key: EJBTHREE-2149
>                 URL: https://jira.jboss.org/browse/EJBTHREE-2149
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: core
>         Environment: EAP 5.1.0
>            Reporter: Ondrej Žižka
>            Assignee: jaikiran pai
>             Fix For: depchain-1.0.0
>
>         Attachments: EJB3-errormsg.txt, ejb3-tutorial-1.0.jar
>
>
> Let's say I am a maintainer of an EJB app. I deploy an EJB to JBoss EAP, and get hunderds of lines of stacktrace, from which I only need a single line:
>    No container configured with name 'Custom Message Driven Bean''
> and the second most important information, WHERE that dependency comes from, is completely missing.
> So i get 50 % of information I need packaged in useless repeatedly printed stacktraces (but that's other story).
> Could the Ejb3AnnotationHandler put an information to the Exception's message about where did it dig the MDB reference from?
> And, generally - could this be applied to all error messages?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the jboss-jira mailing list