If you run two or more target platforms at the same time, make sure that at most one of them contains the service registry bundles (org.eclipse.swordfish.registry). Otherwise, the following error is thrown: failed SelectChannelConnector@0.0.0.0:9001 java.net.BindException: Address already in use at sun.nio.ch.Net.bind(Native Method)
Packages generated from WSDLs sometimes have an odd name. For example, a WSDL with the following name space <schema xmlns:svn="http://types.sopware.org/demos/Library/Common/1.0"/> generates a package like org.sopware.services.demos.library._1, org.sopware.types.demos.library.common._1.
Currently, you cannot specify an alternate package name. As a workaround, you can use the refactoring feature of Eclipse to change the package name.
Swordfish does not support RPC/encoded WSDLs because the RPC binding style is obsolete and non-interoperable. Swordfish leverages the CXF wsdl2java tool to generate a plug-in's source code, resulting in this restriction.
For details see, Rpc/encoded WSDLs are not supported in JAXWS 2.0 error.
This code is related to the behaviour of the Jetty http server used inside Swordfish. URLs that do not point to a file have to be terminated with a slash ("/") character.
Please ensure that the service URL in your WSDL stored in the service registry (for dynamic endpoint resolution) and/or your jaxws-consumer.xml (for static endpoint resolution) ends with a slash.