[jboss-jira] [JBoss JIRA] Commented: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources

[David Lloyd (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12553820#action_12553820 ] 

David Lloyd commented on JBAS-8319:
-----------------------------------

Just to make sure this is clear to all, this is not a VFS function.  VFS is not meant to support resource types of any kind outside of VFS.  The issue is at the deployer layer, which is apparently ignoring the URL scheme and assuming it's a local filesystem deployment.

> [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-8319
>                 URL: https://jira.jboss.org/browse/JBAS-8319
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployers, VFS
>    Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4,  6.0.0.M5
>         Environment: Bug has been observed on all three versions:
>   * 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 M4 (jboss-vfs 3.0.0 CR5)
>            Reporter: Savas Ali Tokmen
>             Fix For: 6.0.0.CR1
>
>         Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt, stacktrace-jboss6-m5.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.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

-- 
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