portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-740) Allow overriding the default Spring assembly without having to modify it
Date Mon, 25 Jun 2007 02:09:26 GMT

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

Ate Douma resolved JS2-740.
---------------------------

    Resolution: Fixed

Done

> Allow overriding the default Spring assembly without having to modify it
> ------------------------------------------------------------------------
>
>                 Key: JS2-740
>                 URL: https://issues.apache.org/jira/browse/JS2-740
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Assembly/Configuration
>    Affects Versions: 2.1.1
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.1.1
>
>
> Spring provides a simply configuration override solution: just have it load the overriding
bean definitions later.
> Jetspeed currently loads all configurations (except the boot which is loaded first) from
one directory which makes it difficult to use this feature as there is no guarantee in which
order the files will be loaded.
> By adding an additional assembly subdirectory, override, to be loaded after the default
assembly directory, it becomes very easy to use the Spring override feature.
> Just put only your changed/modified bean definitions in an Spring configuration xml file
and there is no need to change the default assembly anymore.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message