geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-556) Optional resource refs
Date Mon, 29 Aug 2005 21:30:05 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-556?page=all ]

Aaron Mulder updated GERONIMO-556:
----------------------------------

    Fix Version: 1.0
    Description: 
Right now, all resource refs (and other jndi entries) specified in a spec-dd must be resolved
during deployment or building the configuration will fail.  It's possible that some resource
refs are optional and that the app can function to  some extent with them missing.

We could support this by including an optional "optional" marker in the geronimo plan. The
simplest implementation would attempt to resolve the ref to an object name present during
deployment, and use it if the name is found, and bind nothing if the name is not found.  Then
the app would get a naming exception at runtime if it tried to look up the missing resource.

We should decide what should happen when the entire target object name is supplied.  We could
use it to bind a reference, or only bind a reference if the gbean is present at deploy-time.

  was:
Right now, all resource refs (and other jndi entries) specified in a spec-dd must be resolved
during deployment or building the configuration will fail.  It's possible that some resource
refs are optional and that the app can function to  some extent with them missing.

We could support this by including an optional "optional" marker in the geronimo plan. The
simplest implementation would attempt to resolve the ref to an object name present during
deployment, and use it if the name is found, and bind nothing if the name is not found.  Then
the app would get a naming exception at runtime if it tried to look up the missing resource.

We should decide what should happen when the entire target object name is supplied.  We could
use it to bind a reference, or only bind a reference if the gbean is present at deploy-time.

    Environment: 

> Optional resource refs
> ----------------------
>
>          Key: GERONIMO-556
>          URL: http://issues.apache.org/jira/browse/GERONIMO-556
>      Project: Geronimo
>         Type: New Feature
>   Components: deployment
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0

>
> Right now, all resource refs (and other jndi entries) specified in a spec-dd must be
resolved during deployment or building the configuration will fail.  It's possible that some
resource refs are optional and that the app can function to  some extent with them missing.
> We could support this by including an optional "optional" marker in the geronimo plan.
The simplest implementation would attempt to resolve the ref to an object name present during
deployment, and use it if the name is found, and bind nothing if the name is not found.  Then
the app would get a naming exception at runtime if it tried to look up the missing resource.
> We should decide what should happen when the entire target object name is supplied. 
We could use it to bind a reference, or only bind a reference if the gbean is present at deploy-time.

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


Mime
View raw message