-
Bug
-
Resolution: Done
-
Major
-
JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x, and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.), we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss 6.0.0 M3:
- In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws: java.io.IOException: No context factory for http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
- In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file : /simple-war-1.0.3-SNAPSHOT.war
- relates to
-
JBVFS-163 [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
- Resolved
-
JBAS-5643 MainDeployer MBean methods don't work in JBoss 5.0 CR1
- Closed
-
JBPAPP-8215 EAP 5 does not support fetching http resource for deployment
- Closed
-
JBAS-6521 Remove deprecated deploy/undeploy(Deployment) from Legacy MainDeployer(MBean)
- Closed