The following comment has been added to this issue:
Author: Howard M. Lewis Ship
Created: Sat, 17 Jul 2004 2:58 PM
Body:
It produces, I believe, a very useful error message.
What is your use case? I prefer to keep the number of exceptions at an
absolute minimum.
If you are "polling" the Registry to see if services exist that is bad; better
that we add an API for this purpose than to abuse the existing API.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/HIVEMIND-19?page=comments#action_36729
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/HIVEMIND-19
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HIVEMIND-19
Summary: More descriptive exception reporting
Type: Improvement
Status: Open
Priority: Major
Project: HiveMind
Components:
framework
Versions:
1.0
Assignee: Howard M. Lewis Ship
Reporter: Naresh Sikha
Created: Wed, 7 Jul 2004 2:47 PM
Updated: Sat, 17 Jul 2004 2:58 PM
Description:
I believe Registry.getService should throw more descriptive exceptions in the
sprit of Class.forName.
Currently Registry.getService throws ApplicationRuntimeException and the user
needs to interrogate the message to see what happend.
It is desirable for Registry.getService to throw more descriptive exceptions
when well defined events occur.
- ServiceNotFoundException - there was no metadata defined for that service-id.
- ServiceInstantiationException - there was syntactically valid metadata for
the requested service-id but the implementation could not be instantiated for
some reason.
- ServiceTimeoutException - there was a pooled resource timeout for the
requested service-id.
The reason such exceptions are valuable in my situation is that I have legacy
services that may or may not also be defined in Hivemind. I wish to check
Hivemind first and failing that then try the legacy lookup. Differentiating
between not found, not instantiated, timed out is extremely helpful in this
case.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
