directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <>
Subject [jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars
Date Sun, 26 Dec 2004 00:26:05 GMT
     [ ]
Henri Yandell commented on DIRNAMING-7:

Tomcat's separation choice is interesting. Notably, separating out the java class seems pretty
unnecessary, and separating out the JMX class seems desirable.

We could move the MBean and its Service class into its own one; naming-management. We could
keep the java class in the core package.

I'm still unsure as to why we have some of the Ref classes in core that only factory needs.
Tempting to think they should be moved over.

> Package artifacts into a more modular set of jars
> -------------------------------------------------
>          Key: DIRNAMING-7
>          URL:
>      Project: Directory naming
>         Type: Improvement
>     Reporter: Phil Steitz
>     Assignee: Phil Steitz

> The current naming-factory and naming-core division is not the best setup.  As discussed
on directory-dev, we should change the deployed artifacts to follow the tomcat-5 division:
> naming-core (tc calls this naming-common)
> Everything in o.a.naming plus o.a.naming.factory.ResourceLinkFactory and 
> o.a.naming.factory.ResourceLinkFactory.Constants
> Includes basic naming service and context impl
> Depends on JMX for NamingService
> naming-factory
> Object factories
> Everything in o.a.naming.factory
> Depends on core and the mail API spec to compile; if used, mail session 
> and database connection pool builtins require javamail and commons-dbcp, 
> resp.
> naming-java
> Only JavaURLContextFactory
> Depends on core
> naming-resources
> JNDI access to file / stream resources
> o.a.c.naming.resources
> Depends on core and commons collections
> naming-config
> Contents of o.a.c.naming.config
> Depends on core, and commons beanutils, digester, lang, and logging

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message