geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-3909) Make NamingBuilders/NamingBuilderCollection ordered
Date Thu, 13 Mar 2008 17:12:25 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor resolved GERONIMO-3909.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2

Add sort priority order to NamingBuilder/NamingBuilderCollection. Also, added AbstractNamingBuilder.lookupJndiContextMap()
method that the builders can use to see if a given entry was already processed or not. This
is in case two builders are set to process the same type of DD entry. Committed these changes
to trunk (revision 636806).


> Make NamingBuilders/NamingBuilderCollection ordered
> ---------------------------------------------------
>
>                 Key: GERONIMO-3909
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3909
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.2
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>             Fix For: 2.2
>
>
> Sometimes it might be necessary for one NamingBuilder to run before another one. Right
now, the NamingBuilderCollection is un-ordered and the NamingBuilder are invoked in random
order. 

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