geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3026) Support conventions in reference naming.
Date Mon, 26 Mar 2007 18:04:32 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484171
] 

David Jencks commented on GERONIMO-3026:
----------------------------------------

PersistenceManagerRefs >> rev 522511
PersistenceUnitRefs >> rev 522583

> Support conventions in reference naming.
> ----------------------------------------
>
>                 Key: GERONIMO-3026
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3026
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 2.0-M4
>            Reporter: David Jencks
>         Assigned To: David Jencks
>
> Right now we auto-map exact matches between *-ref-name and the name of the thing referenced.
 For instance resource-ref-name matching the connection-factory-name exactly means you don't
need a geronimo plan to point out that foo means foo.
> There are a lot of conventions mentioned in the spec, such as ejbs being in jndi as java:comp/env/ejb
and persistence stuff being under java:comp/env/persistence.  This Jira is proposing that
at least some naming builders have a flag that lets them do an exact match or a match according
to the spec's convention.  This means that e.g. a persistence ref to "persistence/foo" would
match a persistence unit named "persistence/foo" or "foo" with the flag set, but only "persistence/foo"
with the flag unset.

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


Mime
View raw message