ContextLoader is not released correctly on module reload.
---------------------------------------------------------
Key: BLOSSOM-7
URL: http://jira.magnolia-cms.com/browse/BLOSSOM-7
Project: Magnolia Blossom Module
Issue Type: Bug
Affects Versions: 1.1
Reporter: Danilo Ghirardelli
Assignee: Tobias Mattsson
In class BlossomModuleSupport, when calling method
closeRootWebApplicationContext(), the spring application context is closed
correctly, but the "contextLoader" in the class is not set to null.
When a blossom module reloads itself (which may happen on any change on
/modules/<module>/config node), the spring application context can be closed,
but a reference to the contextLoader is left anyway. When the start of the
module is called, it finds an instance of contextLoader (even if the context is
closed) and throws exception, so it's impossible to reload context until server
restart. Is this wanted for some reason or it is a bug?
If it is wanted you should update the example on the wiki page to avoid spring
re-initialization when the lifecicle of the module is a simple reload and not a
system start/shutdown (which I think it would be a good practice anyway).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
