]
Ales Justin commented on JBAS-8734:
-----------------------------------
Could you please push in the whole stack trace, so we see who's the real culprit.
API change in deployment scanner's add cause failed deployments
---------------------------------------------------------------
Key: JBAS-8734
URL:
https://issues.jboss.org/browse/JBAS-8734
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: 6.0.0.CR1
Reporter: Rob Stryker
Assignee: Ales Justin
Priority: Critical
When using the deployment scanner mbean to pass in a new URL that the JBossAS should scan
for deployments, a path format which worked fine in JBoss 5 and below no longer works.
Specifically, passing in a URL such as the one below:
file:/home/rob/apps/eclipse/workspaces/main_code/runtime%20space%20workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1292215199516/deploy/Dyn888.war/
When passing this string into the addURL mbean, the following error in the jboss console
results:
14:52:54,927 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy,
ctxPath=/Dyn888
14:52:54,930 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Start: name=jboss.web.deployment:war=/Dyn888 state=Create mode=Manual
requiredState=Installed: java.net.URISyntaxException: Illegal character in path at index
56: file:/home/rob/apps/eclipse/workspaces/main_code/runtime space
workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1292215199516/deploy/Dyn888.war/
at java.net.URI$Parser.fail(URI.java:2809) [:1.6.0_14]
at java.net.URI$Parser.checkChars(URI.java:2982) [:1.6.0_14]
Despite that I pass in a string with clear %20 blocking out the spaces, the deployment
scanner does not seem to recognize this and errors. This format of a string has no problem
working in AS 5.1 however.
This is blocking JBossTools server integration.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: