[jboss-jira] [JBoss JIRA] Created: (JBAS-6000) Remote Deployment does not work since StreamingTarget makes different assumptions about scheme of deployURI than DeploymentFactoryImpl.handleUri()

Remote Deployment does not work since StreamingTarget makes different assumptions about scheme of deployURI than DeploymentFactoryImpl.handleUri() -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-6000 URL: https://jira.jboss.org/jira/browse/JBAS-6000 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.0.0.CR2, JBossAS-4.2.3.GA Reporter: Stefan Ocke Assignee: Ales Justin To perform a JSR-88 deployment to a remotely installed server, the org.jboss.deployment.remoting.StreamingTarget seems to be the right target to use, since it perfomrs the file upload of the artificat to be deployed. However, StreamingTarget cannot really be used, since it is immpossible to construct a deployURI that is understood by both, StreamingTarget and org.jboss.deployment.spi.factories.DeploymentFactoryImpl.handleUri(): - DeploymentFactoryImpl.handleUri() understands the follwoing URIs: -- "http://org.jboss.deployment/jsr88" (only exact matches are allowed) -- URIs shaving scheme "jnp" - DeploymentManager impl only constructs a StreamingTarget, when the URI has a parameter "targetType=remote". This is in contradiction, wtih the excact matchin of "http://org.jboss.deployment/jsr88", sicne it just does not allow any parameters. So, to get a StreaminTarget, on has to use "jnp:" as scheme in the URI. - But: StreamingTarget cannot handle URIs starting with "jnp", but just schemes like "socket" or "http", where an according TransportClientFactory exists in jboss-remoting module. So in summary, handling of the deployURI seems to be quite inconsistent and works only for the local case and only if URI is "http://org.jboss.deployment/jsr88" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira