You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2008/03/12 22:52:46 UTC
[jira] Created: (GERONIMO-3909) Make
NamingBuilders/NamingBuilderCollection ordered
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
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.
[jira] Resolved: (GERONIMO-3909) Make
NamingBuilders/NamingBuilderCollection ordered
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ 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.