geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Closed: (GERONIMO-556) Optional resource refs
Date Thu, 29 May 2008 19:41:44 GMT


David Jencks closed GERONIMO-556.

    Resolution: Won't Fix

I don't think this is worth the effort.  If someone has optional resource refs perhaps they
can look them up in the global jca: context where they are all now bound.  This is less flexible
but there doesnt' seem to be any support for this feature.

> Optional resource refs
> ----------------------
>                 Key: GERONIMO-556
>                 URL:
>             Project: Geronimo
>          Issue Type: New Feature
>          Components: deployment
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: Wish List
> 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.
You can reply to this email to add a comment to the issue online.

View raw message