You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2006/04/21 22:45:05 UTC
[jira] Created: (GERONIMO-1888) Better help for bad references
Better help for bad references
------------------------------
Key: GERONIMO-1888
URL: http://issues.apache.org/jira/browse/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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1888) Better help for bad references
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1888?page=all ]
Aaron Mulder updated GERONIMO-1888:
-----------------------------------
Assign To: Aaron Mulder
Priority: Minor (was: Major)
> Better help for bad references
> ------------------------------
>
> Key: GERONIMO-1888
> URL: http://issues.apache.org/jira/browse/GERONIMO-1888
> Project: Geronimo
> Type: Improvement
> Security: public(Regular issues)
> Components: usability
> Versions: 1.0
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Minor
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1888) Better help for bad references
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1888?page=all ]
Aaron Mulder updated GERONIMO-1888:
-----------------------------------
Assign To: (was: Aaron Mulder)
> Better help for bad references
> ------------------------------
>
> Key: GERONIMO-1888
> URL: http://issues.apache.org/jira/browse/GERONIMO-1888
> Project: Geronimo
> Type: Improvement
> Security: public(Regular issues)
> Components: usability
> Versions: 1.0
> Reporter: Aaron Mulder
> Priority: Minor
> Fix For: Wish List
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1888) Better help for bad references
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1888?page=all ]
Matt Hogstrom updated GERONIMO-1888:
------------------------------------
Fix Version: Wish List
(was: 1.1)
> Better help for bad references
> ------------------------------
>
> Key: GERONIMO-1888
> URL: http://issues.apache.org/jira/browse/GERONIMO-1888
> Project: Geronimo
> Type: Improvement
> Security: public(Regular issues)
> Components: usability
> Versions: 1.0
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Minor
> Fix For: Wish List
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira