#11 View saved ObjectMessage message.xml more easily

[Elias Ross]

If an ObjectMessage is serialized out from a classpath
from another provider (say, JBoss), viewing the saved
message doesn't work. You get

2005-01-28 12:17:54,831 ERROR [FileRepository] ( )
com.example.sms.Record
java.lang.ClassNotFoundException:

It would be good to be able to set the classloader for
the "messages" folder. Or, when the message is
serialized to XML store which classloader/provider was
used.

[Elias Ross]

Logged In: YES
user_id=556458

The workaround is (of course) to set the classpath before
starting the application.

[Colin Crist]

Logged In: YES
user_id=66833

Good point. I can see a number of options:

1. Allowing you do have more than one "messages" folder each
with its own classloader (although Hermes uses the last
selected session to create messages when browsing stuff in
the messages folder so you could get round this problem at
the moment I think)

2. Improving the rather lame File provider so you can
reference differnnt classloaders with each destination as a
per-destination property (this is a 1.9 feature out shortly).

3. Storing the original classloader with the message and
defaulting to "System" if that loader does not exist.

All of the above are fairly easy. I'll choose one with the
least Swing changes unless you have a strong opinion.

Colin.