Issue Type: Bug Bug
Affects Versions: 3.0
Assignee: Tobias Mattsson
Created: 10/Oct/13 11:30 AM
Description:

When using profiles in Spring the active profile settings seem to get loss in application context initialization.

Application/Servlet context gets initialized in the BlossomModuleSupport class which will be extended by the Mgnl module class.

Usually there are a few ways to set the active profile in Spring (spring.profiles.active):

1. via <context-param> in the web.xml
2. via system property -Dspring.profiles.active=development
3. setting the attribute profiles in the <bean> tag of the context definition
4. by code calling setActiveProfile("development") of Springs ConfigurableEnvironment class

The latter should automatically be called when providing the profile name via system property (VM arg).

We tried system property, context-param and bean xml definition, no success.

If the profile definition is missing several beans are just ignored during instantiation process.

We use xml profile and annotation based profiles, this makes no difference.

Environment: Windows 7 professional
Tomcat 7.0.32/JBoss eap 6.1
Spring MVC 3.2.3
Project: Magnolia Blossom Module
Priority: Neutral Neutral
Reporter: Sigurd Rolfes
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to