The following issue has been updated:
Updater: Naresh Sikha (mailto:[EMAIL PROTECTED])
Date: Wed, 28 Jul 2004 6:58 PM
Comment:
Patch framework src/java and src/test to include JNDI adapters and unit tests.
Changes:
Attachment changed to naming.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/HIVEMIND-30?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/HIVEMIND-30
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HIVEMIND-30
Summary: JNDI Adapters to Hivemind Default Registry
Type: New Feature
Status: Open
Priority: Major
Project: HiveMind
Components:
framework
Versions:
1.0
Assignee: Howard M. Lewis Ship
Reporter: Naresh Sikha
Created: Wed, 28 Jul 2004 6:58 PM
Updated: Wed, 28 Jul 2004 6:58 PM
Environment: Windows XP, Sun J2SDK1.4.2_04, Eclipse 3.0
Description:
HiveMind Developers,
I have put together a simple set of JNDI providers that sit on top of
the default Registry. They will find services and configurations for
JNDI composite names.
The syntax for the composite names is:
Services - "service:/"; + service_interface_name + "/" + service_id
Configurations - "configuration:/" + configuration_id
Service names have a couple of options in support of globally unique services.
Option 1 - Interface only - "service:/"; + service_interface_name
Option 2 - Id only - "service://"; + service_id
Option 2 works by passing in Object.class as the interface class which
is a circumvention to be sure but still is an assignable type.
I find the JNDI providers to be useful to get at services and
configurations where J2EE context (servlet request, servlet context,
etc.) is not available such as in helper classes.
This is also useful in enforcing layer separation - clients of my
services are only dependent upon the service interfaces and JNDI and
not on the infrastructure of my services (Hivemind).
All the code is documented and there are unit tests to support.
Thanks for your feedback.
---------------------------------------------------------------------
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]
