-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Won't Fix
-
Affects Version/s: 6.2.0 CE RC2
-
Fix Version/s: 6.2.0 CE RC2, 6.2.0 CE RC3, 6.2.10 EE GA1, 6.2.X EE
-
Labels:
-
Environment:JBoss EAP 5.1 + MySQL 5.5. Portal ee-6.2.x EE GIT ID: a68ccda94ffb0b19ad6f3e69968994e57c480e43.
-
Fix Priority:5
Steps:
1. Run "ant all" on the portal version source code
2. Run "ant -f build-dist.xml zip-portal-war" source code
3. Run "ant -f build-dist.xml zip-portal-dependencies" source code
4. Set up the WAR with dependencies file on JBoss EAP 5.1
5. Start up JBoss server
6. ROOT.war fails to deploy
DEPLOYMENTS IN ERROR: Deployment "vfsfile:/D:/TEST_ENV/61x-jboss-eap-5.1/jboss-as/server/default/deploy/ROOT.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/D:/TEST_ENV/61x-jboss-eap-5.1/jboss-as/server/default/deploy/ROOT.war/ deployment failed
Expected Behavior:
- Able to run the portal
Actual Behavior:
- Unable to run the portal
Note:
- Have tested on latest ee-6.1.x and was able to run the portal on JBoss EAP 5.1
Reference:
- is caused by
-
LPS-40729 PortalSecurityManager and ModuleFrameworkClassLoader dont get loaded on JBoss EAP 5.1
- Closed
-
LPS-40733 Using W3C_XML_SCHEMA_NS_URI fails on some app servers
- Closed
-
LPS-40750 When ModuleFramework not loaded, use 'dummy' version
-
- Closed
-
-
LPS-34785 make the framework always on
-
- Closed
-