|
From: <nic...@ya...> - 2004-09-23 04:26:07
|
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 == ex.getClass()) {
return new JmsException(ex);
}
Kind regards,
Nick Airey
|