Do not get system property substitution in JBoss EAP 5 even when deployment order is specified
Issue
- We use the
SystemPropertiesServiceto specify system properties to be substituted in other MBean deployments. The substitution does not take place even when theLegacyPrefixDeploymentContextComparatorspecifies that theSystemPropertiesServiceMBean be deployed first. - Before we upgraded to JBoss 5, our web context path had a property value that loaded from a property file during application startup. Is there a way to make sure the property file value is loaded before the context path is generated?
- In Jboss 4.0.3 SP1 community version we used to inject the these placeholders using system properties . This feature is not there in Jboss EAP 5
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 5.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
