Frequently Asked Questions


How can I resolve the JMX port error that arises when I start more than one target platform?

When trying to start several Swordfish launch configurations, exceptions stating that the JMX port is already in use, will arise. This happens because each configuration includes a ServiceMix management bundle, which starts the JMX server on the default port. To avoid this exception:
  1. Click Run > Run Configurations.... .
  2. Select the additional launch configuration and click the Arguments tab.
  3. In the VM arguments section, add the rmiRegistryPort property and set the value to the port that the JMX server will use . For example, set -DrmiRegistryPort=5556 .

How can I resolve this error: failed SelectChannelConnector@0.0.0.0:9001java.net.BindException: Address already in use

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)

How can I deal with generated package names with special characters

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.

Why do I get the error: RPC/encoded WSDLs are not supported in JAXWS 2.0

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.