i would venture that 'most likely you can't'. The reason would be that first of all, the applet can only talk to its server. So it means that the jms server should be at the same location as the applet's origine. But that is not an actual reason. What would be more of a pb is the way JMS is usaually implemented. It would not work with a JMS provider that uses client-based storage (the messages are sent directly to each client machines and stored on the file system). It would not work either with multicat based implementations. so considering all the technical impossibilities, you'd be left searching for a specific JMS client library implementation that can 'walk in between the rain-drops'.

I would avoid the problem alltogether by creating a servlet that does the job on behalf of the applet. The servlet is your JMS client (does the subscribe/publish) and the applet becomes a simple remote UI.

makes sense?

cheers

laurent