[jira] Updated: (HIVEMIND-30) JNDI Adapters to Hivemind Default Registry

["Howard M. Lewis Ship (JIRA)" <hi...@jakarta.apache.org>]

     [ https://issues.apache.org/jira/browse/HIVEMIND-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated HIVEMIND-30:
-----------------------------------------

    Assignee:     (was: Howard M. Lewis Ship)

> JNDI Adapters to Hivemind Default Registry
> ------------------------------------------
>
>                 Key: HIVEMIND-30
>                 URL: https://issues.apache.org/jira/browse/HIVEMIND-30
>             Project: HiveMind
>          Issue Type: New Feature
>          Components: framework
>    Affects Versions: 1.0
>         Environment: Windows XP, Sun J2SDK1.4.2_04, Eclipse 3.0
>            Reporter: Naresh Sikha
>         Attachments: naming.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.