You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/10/28 08:38:56 UTC

[jira] Closed: (GERONIMO-513) jndi refs should result in dependencies, optionally

     [ http://issues.apache.org/jira/browse/GERONIMO-513?page=all ]
     
David Jencks closed GERONIMO-513:
---------------------------------

    Resolution: Fixed

After more thought and discussion with Dain we are trying a simpler implementation.  All web app modules will depend on all ManagedConnectionFactory gbeans and all ejbs in the ear.  This will make sure that all possible jndi references for a servlet are started before the servlets init method is called.  This is overkill, but does allow for possible future use of non- java:comp jndi contexts that are so popular (even though we don't currently support that) and eliminates trying to figure out how to unwrap circular ejb dependencies.

Before implementing this I implemented a jndi-ref to dependency solution; I'll attach that as well for future reference.

Sending        modules/jetty-builder/src/java/org/apache/geronimo/jetty/deployment/JettyModuleBuilder.java
Sending        modules/tomcat-builder/src/java/org/apache/geronimo/tomcat/deployment/TomcatModuleBuilder.java
Adding         modules/web-builder/src/java/org/apache/geronimo/web/deployment/AbstractWebModuleBuilder.java
Transmitting file data ...
Committed revision 329128.

> jndi refs should result in dependencies, optionally
> ---------------------------------------------------
>
>          Key: GERONIMO-513
>          URL: http://issues.apache.org/jira/browse/GERONIMO-513
>      Project: Geronimo
>         Type: New Feature
>   Components: naming
>     Versions: 1.0-M3
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0

>
> After non-reference gbean dependencies (GERONIMO-512) are implemented, jndi refs should result in creating these dependencies.  They need to be optional to take account of (at least) these scenarios:
> 1. circular ejb references A uses B uses A.  
> 2. An ejb has 2 resource refs: if the first one isn't available, it tries the backup second one.
> So, the naming schema needs an optional <optional/> tag to prevent a ref from turning into a dependency.

-- 
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