[
https://jira.jboss.org/browse/JBVFS-163?page=com.atlassian.jira.plugin.sy...
]
David Lloyd resolved JBVFS-163.
-------------------------------
Assignee: David Lloyd (was: John Bailey)
Resolution: Rejected
This is not a VFS bug. VFS's job is not URL handling, nor remote fetching of
resources. If anything, this is a bug in the JBoss AS deployment layer. Please open an
issue in the JBAS project.
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBVFS-163
URL:
https://jira.jboss.org/browse/JBVFS-163
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.0.GA, 2.1.2.GA, 3.0.0.CR5
Environment: JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M3 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: David Lloyd
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
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 and JBoss 6; 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira