geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Created: (GERONIMO-1888) Better help for bad references
Date Fri, 21 Apr 2006 20:45:05 GMT
Better help for bad references

         Key: GERONIMO-1888
     Project: Geronimo
        Type: Improvement
    Security: public (Regular issues) 
  Components: usability  
    Versions: 1.0    
    Reporter: Aaron Mulder
     Fix For: 1.1

If a GBean can't start beacuse of a missing reference, it would be great to give a more helpful
error message.  Like if the reference included the name "Foo", print a list of all AbstractNames
including name="Foo" in the format you'd expect for the reference in question (slightly different
for GBean-to-GBean references vs J2EE Component-to-Resource references, etc.).  It would be
great if it came out like this:

Unable to resolve reference to <artifactId>bar</artifactId><name>Foo</name>.
 Did you mean one of these instead?
 * <artifactId>baz</artifactId><name>Foo</name>
 * <artifactId>other</artifactId><name>Foo</name>

Unable to resolve reference to <artifactId>bar</artifactId><name>Foo</name>.
 There are no components with <name>Foo</name> in this module or any of its dependencies.
 Perhaps you need to add a <dependency> to this module and point it to one of the following
modules which has a component with <name>Foo</name>:
 * mygroup/myartifact/1.0/car
 * other/something/3.4/rar

This is aggravated by the fact that our resource target names are no longer JMX names, so
we can't tell people to look up the component in the JMX debug tool.  However, it's mitigated
by the fact that you have to declare dependencies explicitly and can more often just use <name>Foo</name>.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message