Improved binary installers

There are now binary installers for each of the products in the Celtix family. The installers are smaller and present the installer with only the options available for the product they have downloaded.

Improved source installer

The source installer has been updated to use Maven 2.0. It provides a single target for building all of the projects incorporated into Celtix Enterprise. In addition, the individual projects can be built separately.

Operation-based routing

You can define routes that use specific operations of an endpoint as a source or target. This facilitates the construction of routes that are more fine grained than routes that have fully defined endpoints as sources or targets.

Recipient List Routing Pattern

You can define a list of recipients for messages. The messages are routed to one of more of the recipients on the list based on a specified set of criteria.

Routing Slip Routing Pattern

You can define routes that pass messages through a series of endpoints based on a specified set of criteria. This is a simplified form of service orchestration.

Load Balancing

You can define routes that distribute requests across a number of endpoints that implement the same service. The default load balancing algorithm is round-robin. However, you can implement your own load balancing algorithm and plug it into the router.

Application naming

Applications deployed into the container now use the name of the WAR as their application name.

Multiple Spring bean deployment

A user can now deploy multiple Spring beans to be deployed as a part of an application. Spring bean files must be placed in the META-INF/spring folder of the WAR.

Drag and drop deployment

The Celtix Enterprise container now scans the container repository for newly added WARs. When a new WAR is found, the application it defines is automatically deployed into the container.

Application monitoring

Using the Web Service management interface or the JMX management interface, you can get the state of an application in the Celtix Enterprise container. Applications are either STARTED, STOPPED, or FAILED.

Configuration

The configuration model used by Celtix Advanced Service Engine has been simplified. You no longer need to use the bean/property/value nesting. Instead configuraiton is specified using elements.

Support for mixed style WSDL interfaces.

Apache Incubator Qpid can now be used an alternative JMS transport.

For information on setting this up see Chapter 4, Using Celtix Advanced Messaging as a JMS Replacement in Using the Celtix Enterprise JMS Transport.

Support for JAX-WS Handlers when using Dispatch/Provider API's.

Performance improvements.

Bug fixes and other enhancements.

JMS 1.1 compliance.

Performance improvements.

Bug fixes and other enhancements.

Welcome Page on *NIX

On *NIX systems where Mozilla or Netscape is not present, the Welcome Page will not display when the installer finishes running. You can manually load the Welcome page from the docs folder of the installation.

Linux Installations with GCJ

There is a known problem with running the Linux installer (.bin extension) on a system with GCJ (GNU Compiler for Java) installed. It has been identified as an InstallAnywhere bug. When running the installer you may see the following output:

"Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX)

Stack Trace:
java.lang.NoClassDefFoundError: while resolving class: ZeroGe
  at java.lang.VMClassLoader.resolveClass(java.lang.Class)
(/usr/lib64/libgcj.so.5.0.0)"
      

The solution is to install a Sun JVM and put that on your path. For example, on a machine with a JRE installed at /opt/jdk1.5.0_03_64/jre run the following:

export PATH=/opt/jdk1.5.0_03_64/jre/bin:$PATH

Mule Download

You must download a number of the Mule runtime libraries from www.mulesource.com before using the router. A script, download_mule is provided with the installation. You must type yes when asked to accept the MuleSource Public License.

POJO Mode

The following features are not supported:

PAYLOAD Mode

The following features are not supported:

MESSAGE Mode

The following features are not supported:

REST Support

The router does not support services that use REST style interfaces. There is currently no way for the router to pass the HTTP verbs to endpoints.

Code Generation

Do not generate more than one server, implementation, or client per project. Support for multiple code generations in a single project will be made available via the update site in the near future.

Annotations

Using non-default attribute values when adding JAX-WS annotations can cause problems with the generated code and WSDL. We recommend using only the default values when creating annotations.

Path Names

The GUI tools do not work properly when there are spaces in the workspace's path name.

Top-level README

The README in the samples folder contains instructions for setting a number of environment variables. These should be ignored. Celtix Enterprise includes a script, celtix_env, that properly sets your environment.

Building on Linux

On versions of Linux with a system wide Ant configuration file installed (/etc/ant.conf) you may see the following error when building the samples:

	"Exception in thread main java.lang.ClassDefNotFoundError org/apache/tools/ant/Launch/Launcher"
      

If you get this error, use the --noconfig option when running Ant. This will bypass the system's ant configuration and ensure that the version of Ant installed with Celtix Enterprise is called.

	ant --noconfig
      

WS-RM Samples

The WS-Reliable Messaging demo in service_creation/ws_rm fails if the client is run a second time against the same server. This is due to a bug in the demo code whereby the MessageLossSimulator interceptor is installed on both the client and server side and results in loss of partial responses originated from the server.

To workaround, apply the following changes:

Service Creation HTTP Demos

Only some of the samples have been updated to reflect the new configuration system. For example, the ws_addressing sample has been updated, but not the hello_world_https sample. However, all demos continue to work as before.

Start Script & SunOS

The Apache Incubator ServiceMix start script located in $SERVICEMIX_HOME/bin/servicemix is not compatible with SunOS /bin/sh, to workaround this issue we launch Apache Incubator ServiceMix using Bash in $CELTIX_HOME/bin/servicemix_start.sh. This requires that a Unix/Linux system have bash installed in /bin.

When CELTIX_HOME/bin/servicemix_start.sh is launched on a system without bash present in /bin the following warning will be displayed:

"The ServiceMix executable requires bash installed in /bin."

The script will then exit.

Unpacking Files

Apache Incubator ServiceMix has a known issue with unpacking files placed in its deploy and install folders, this is documented in Apache Incubator ServiceMix's bug tracking system under SM-607. This issue may be observed when CELTIX_HOME/bin/servicemix_deploy_sa and/or CELTIX_HOME/bin/servicemix_install_ca scripts are executed. If this issue occurs the user may retry the script or they may edit the 'monitorInterval' value in SERVICEMIX_HOME/conf/servicemix.xml to a larger value.