Hi,
yes, right, ARGHHH.
I took the latest SM trunk and installed it, but in the root pom of my
project, I still had the dependency to SM 3.2.1. Means the
servicemix-shared-3.2.1 was bundled from my local maven repository into my
SA.
I looked into the root pom of SM 3.3 trunk and checked all dependency
versions I saw that 3.3 now uses cxf 2.1 incubator instead 2.02 which was
used in SM 3.2.
However, when I use cxf 2.1 in my projects all my wsdl2java goals are not
working any more because it complains that it can't find an element which is
defnined in an included xsd of the wsdl. Well, it is there, but I don't know
what the problem is. So, I switched back to cxf 2.0.2 incubator and
erverything is build fine. I guess this is more cxf then SM related.
Now to the main point:
I'm pretty sure that the latest 3.3 trunk components are used, however, you
might guess it, still problems which look pretty simple.
This is (a part) of my debug logs, when I start my integration test:
...
2008-03-29 01:48:36,437 [main ] DEBUG ManagementContext
- Registering system service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AdminCommandsService
2008-03-29 01:48:36,437 [main ] INFO InstallSharedLibrary
- Deploying shared library:
file:///d:\java\.m2\repository/org/apache/servicemix/servicemix-shared/3.3-SNAPSHOT/servicemix-shared-3.3-SNAPSHOT-installer.zip
2008-03-29 01:48:36,437 [main ] ERROR InstallationService
- Deployment failed
javax.jbi.management.DeploymentException: java.net.URISyntaxException:
Illegal character in path at index 10:
file:///d:\java\.m2\repository/org/apache/servicemix/servicemix-shared/3.3-SNAPSHOT/servicemix-shared-3.3-SNAPSHOT-installer.zip
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.unpackLocation(AutoDeploymentService.java:606)
at
org.apache.servicemix.jbi.framework.InstallationService.installSharedLibrary(InstallationService.java:213)
at
org.apache.servicemix.jbi.framework.AdminCommandsService.installSharedLibrary(AdminCommandsService.java:104)
at
org.apache.servicemix.jbi.container.InstallSharedLibrary.doDeploy(InstallSharedLibrary.java:37)
at
org.apache.servicemix.jbi.container.DeploySupport.deploy(DeploySupport.java:58)
at
org.apache.servicemix.jbi.container.SpringJBIContainer.afterPropertiesSet(SpringJBIContainer.java:111)
...
For me it looks like there is a problem in the URI, because at position 10
there is a backslash instead of a slash.
So, where does it come from ... I have my MAVEN_OPTS env var, but here I use
slashes, no backslashes:
MAVEN_OPTS=-Duser.home=/d:/java -Xmx768m
Maybe I should change the SM code to replace backslashes with slashes in the
method?
Anyone having an idea?
--
View this message in context:
http://www.nabble.com/Integration-Test%3A-UnknownHostException-tp16278375s12049p16368303.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
