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

Anand Babu (JIRA) issues at jboss.org
Tue Nov 21 09:29:00 EST 2017


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

Anand Babu commented on JBAS-8319:
----------------------------------

How to migrate services of MainDeployer and SubDeployer to wildfly or EAP.

MainDeployer we used ejb-jar annotation. But I am unable to find for SubDeployer.

> [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-8319
>                 URL: https://issues.jboss.org/browse/JBAS-8319
>             Project: Application Server 3  4  5 and 6
>          Issue Type: Bug
>          Components: ProfileService
>    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
>            Assignee: Emanuel Muckenhuber
>              Labels: deployer, deployment, remote
>             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 was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list