Chris Harris wrote: > > Can't you implement Observer via JMS and Message-Driven > Beans?
Hmmmm.. That's an intriguing thought. Haven't thought of that before. How would you do it? Does the observable bean take a list of client queues (would that work? Are they serialisable?) or queue names. When something changes in the bean it sends a JMS message off and the clients (ie servlet, desktop app etc) must be JMS message listeners. What about dealing with the problem of multiple instances of the one bean where the app server allocates one instance per client, rather than a shared one. Unless that set of queue references is persisted, the others won't know about the global set of queues. Gut feel is that it can't be done, but I'm willing to be convinced otherwise. -- Justin Couch http://www.vlc.com.au/~justin/ Freelance Java Consultant http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant ------------------------------------------------------------------- =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
