When you create a new Java service, Designer adds a Java class associated with the Java service to a Service Development Project in your local workspace. If an appropriate Service Development Project that corresponds to the service’s IS package does not yet exist, Designer creates one for the service. For more information, see Service Development Projects in the Local Workspace.

Designer adds initial code to the Java service. For all Java services, Designer adds the Java package definition, class definition, primary method definition, and a minimum set of imports. If the service is the second or subsequent Java service created in the same IS folder, Designer also adds any shared code defined in other Java services in the IS folder, additional imports, extends, and implements.

Because Designer is connected to Integration Server, when you save the service in Designer, your changes are also immediately saved in Integration Server.

Additionally, when you save a Java service, Designer compiles it both in the Service Development Project in Designer and on Integration Server. When Designer compiles the service locally, by default, it also rebuilds other classes in the Service Development Project.

If your Java service requires additional classes to compile, you must add them, either as individual class files or in jar files, to both the Service Development Project and to Integration Server. If you set up IS package dependencies for the Java service in Integration Server and there are classes and/or jar files in the IS packages required so that the service can compile, you must manually add them to Service Development Project. For more information, see Adding Classes to the Service Development Project. For more information about adding classes to Integration Server and how Integration Server stores package information, see webMethods Integration Server Administrator’s Guide.

When a folder contains multiple Java services, Designer adds an empty implementation of all of the Java services in the folder to each Java service. This allows a Java service in a folder to invoke another Java service in the same folder directly using methodName(pipeline) where methodName is the local name of the Java service.