Colin Crist [02/Jan/08 10:19 AM] As a default Hermes uses the last selected session in the browser tree to use as a factory for creating messages as it needs to create a connection and session to use as a factory for messages. If no session has yet been selected it just uses the first in the tree. This is the current functionality in the version you are using. Not clear I grant you. How about you can select an override to a specific JMS provider and hence classpath group for localised code in an object message? This always means you must be able to connect to a JMS provider in order to create a message. I can add this to the General panel in the Configuration dialog? Does this sound good? Can you elaborate on any specific additional requirements. Its quite easy so can be fixed for the 1.13 release.

Colin Crist [01/Feb/08 06:40 AM] You can now set the JMS ession to use as a message factory (and hence its classpath) from the General configuration dialog.