Hi,
when I modified our companies JMS Provider to be JMS 1.1 compliant
I had some problems with the new interfaces, because my implementations
implemented too much of them.
E.g. StdServerSessionPool and ConnectionFactoryHelper have some lines
in them, where they check
... if blaBla instanceof TopicBlaBla...
... else if blaBla instanceof QueueBlaBla...
(with BlaBla in {Connection, ConnectionFactory})
So my "Super"ConnectionImpl (which implemented both QueueConnection
and TopicConnection and had to be used as a QueueConnection)
got detected as a TopicConnection instead.
I only got around this one by *not* implementing the respective
interfaces by the superclass, but extending and implementing in
otherwise nearly empty subclasses.
I must admit, that I did so before diving deeper in the JBoss-sources,
which I did afterwards to get the XA-family working.
Perhaps you come up with a better solution.
Enjoy,
Michael.
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
