aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ARIES-370) Ensure custom element are parsed after blueprint element in Parser.loadComponents
Date Fri, 03 Sep 2010 13:42:33 GMT

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

Lin Sun resolved ARIES-370.
---------------------------

    Resolution: Fixed

see subversion commit tab for commits

> Ensure custom element are parsed after blueprint element in Parser.loadComponents
> ---------------------------------------------------------------------------------
>
>                 Key: ARIES-370
>                 URL: https://issues.apache.org/jira/browse/ARIES-370
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>    Affects Versions: 0.1
>            Reporter: Lin Sun
>            Assignee: Lin Sun
>             Fix For: 0.2
>
>
> Currently, when we load components in Parser.java, for the child nodes of root, we parse
blueprint elements and custom elements based on the order specified in the blueprint definition
XML.   It is possible when we are parsing the custom element that contains a global configuration
for the other blueprint components before the other blueprint components are parsed (and registered
in component definition registry).  
> Proposed is a change to ensure we always finish parsing blueprint components first and
ensure they are registered in the component definition registry before we start to pass custom
elements.  This way, if we support bundle wide transaction, we can easily apply it to all
the blueprint components that has been registered in the component definition registry.

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