You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <de...@tuscany.apache.org> on 2008/08/11 09:37:48 UTC
[jira] Updated: (TUSCANY-2535) Tuscany dosn't run if install on a
WebSphere server that has itself been installed in a directory with a space
in the name
[ https://issues.apache.org/jira/browse/TUSCANY-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ant elder updated TUSCANY-2535:
-------------------------------
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.3.1
> Tuscany dosn't run if install on a WebSphere server that has itself been installed in a directory with a space in the name
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2535
> URL: https://issues.apache.org/jira/browse/TUSCANY-2535
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.3
> Environment: WinXP SP2 IBM JDK 5 WebSphere 6.1
> Reporter: Simon Laws
> Assignee: Raymond Feng
> Fix For: Java-SCA-1.3.1
>
>
> From the mail list
> Caused by: java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:854)
> at org.apache.tuscany.sca.node.impl.NodeImpl.configureNode(NodeImpl.java:508)
> at org.apache.tuscany.sca.node.impl.NodeImpl.<init>(NodeImpl.java:186)
> ... 15 more
> Caused by: java.net.URISyntaxException: Illegal character in opaque
> part at index 22: wsjar:file:/C:/Program
> Files/IBM/WebSphere/AppServer/profiles/soa/installedApps/soa/simple-ear.ear/simple-ejb.jar!/service.composite
> at java.net.URI$Parser.fail(URI.java:2821)
> at java.net.URI$Parser.checkChars(URI.java:2994)
> at java.net.URI$Parser.parse(URI.java:3031)
> at java.net.URI.<init>(URI.java:590)
> at java.net.URI.create(URI.java:852)
> ... 17 more
> It appears to be complaining about the path at which my websphere home
> resides, ie the space in "Program Files".... Is this something that
> Tuscany should be dealing with? Or could it be a websphere bug?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.