|
From: <jue...@we...> - 2004-09-23 06:45:30
|
Thanks for spotting this! The problem is that Spring's JmsException is =
an abstract base class, not to be thrown directly, but the standard =
JMSException is not, i.e. it can be thrown directly. I've added a check =
to convert plain JMSException to Spring's UncategorizedJmsException =
without trying to load a counterpart class.
=20
Juergen
=20
________________________________
Von: spr...@li... im Auftrag =
von nic...@ya...
Gesendet: Do 23.09.2004 06:26
An: spr...@li...
Betreff: [Springframework-developer] javax.jms.JMSException processing
Hi Guys,
I was testing some of the JMS send functionality using IBM-MQ as the =
provider,
and noticed a bug in
org.springframework.jms.support.JmsUtils.convertJmsAccessException()
The bug is that if the exception parameter ex is exactly a
javax.jms.JMSException, the JMSUtils class tries to instantiate an
org.springframework.jms.JMSException (note: incorrect case of JMS in the =
spring
class)
This method needs to treat the base javax.jms.JMSException as a special =
case.
You can use code something like this: (sorry it's not tested and not a =
patch
format - development machines at my work don't have 'net access, but I'm =
sure
you'll get the idea) Insert this code after the JMSSecurityException =
check:
if (javax.jms.JMSException.class =3D=3D ex.getClass()) {
return new JmsException(ex);
}
Kind regards,
Nick Airey
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|