Limitations of the JMS and MQ JMS bindings

The JMS and MQ JMS bindings have a limitation.

A limitation and a reminder when using the JMS and MQ JMS bindings are discussed.

Business Object XML using JMS TextMessage serialization type

The Business Object XML using JMS TextMessage serialization type can only serialize business objects; that is, an interface operation must have its input(s) and output(s) defined as a business object type. An interface operation cannot be defined with primitive types for input and output. The following operation, for example, is not allowed.
Operation defined with primitive type inputs and outputs

Implications of generating default bindings

When you generate a binding, several fields will be filled in for you as defaults, if you do not choose to enter the values yourself. For example, a connection factory name will be created for you. If you know that you will be putting your application on a server and accessing it remotely with a client, you should at binding creation time enter JNDI names rather than take the defaults since you will likely want to control these values through the administration console at run time.

However, if you did accept the defaults and then find later that you cannot access your application from a remote client, you can use the administration console to explicitly set the connection factory value. Locate the provider endpoints field in the connection factory settings and add a value such as <server_hostname>:7276 (if using the default port number).

Feedback
(C) Copyright IBM Corporation 2005, 2007. All Rights Reserved.