> > > You have to remember that the specs are generally written from the > application developer's standpoint. As a result, application developers > must assume that for a portable application to work, the below is true. > NOte that it doesn't say that the client must throw an exception, etc. > This is to allow flexibility in the vendors to build more creative > solutions. > > Probably a good caveat to think about now is that if you don't follow these > rules, non-portable behavior may occur. >
I agree. however, for me to make my code more portable I'd first have to jump in and figure out a way to to resolve this. There are PLENTY of JMS extensions in ActiveMQ. this one in particular just seems to be a bit difficult to work around. KEvin -- We’re hiring if you know of any awesome Java Devops or Linux Operations Engineers! Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts>
