When using the publish methods to publish a message, messages are first being put in a MessagePipeline. Messages in the same MessagePipeline will be concatenated to form on bigger Message before it's being send out. The MessageServiceClient manages a collection of MessagePipeline, each mapped to an identifying key consisting of the Topic Name and Message Type. When HTTP is used as the underlying transport layer of the MessageServiceClient, the current key is not sufficient enough. Adding the Destination Servlet Context Path to the key ensures that Messages with different Destination Servlet Context Paths cannot be concatenated, which is mandatory for HTTP. JMS doesn't suffer from this. Marking this one as FIXED.
Bug
Major
MODIFY
/icefaces/trunk/icefaces/core/src/com/icesoft/net/messaging/MessageServiceClient.java
When using the publish methods to publish a message, messages are first being put in a MessagePipeline. Messages in the same MessagePipeline will be concatenated to form on bigger Message before it's being send out. The MessageServiceClient manages a collection of MessagePipeline, each mapped to an identifying key consisting of the Topic Name and Message Type. When HTTP is used as the underlying transport layer of the MessageServiceClient, the current key is not sufficient enough. Adding the Destination Servlet Context Path to the key ensures that Messages with different Destination Servlet Context Paths cannot be concatenated, which is mandatory for HTTP. JMS doesn't suffer from this. Marking this one as FIXED.