could you raise a jira issue for this
thanks,
Rob
On Feb 4, 2008, at 1:47 PM, vjarnot wrote:
Anyone out there?
vjarnot wrote:
Is there any reason that
org.apache.activemq.ActiveMQMessageTransformation
copyProperties method doesn't check for null before calling
setObjectProperty(...)?
This is causing null pointer exceptions for us when trying to bridge
Oracle's AQ with ActiveMQ - Oracle returns a value of null for
JMSXGroupSeq (and maybe others, that's the first one that causes the
failure).
Since passing a null to setObjectProperty appears to inevitably
fail (null
pointer thrown from TypeConversionSupport.convert(...)) why not
check for
null and not call setObjectProperty?
TypeConversionSupport even has an assert line that seems to
indicate the
value should never be null, but calling code
(ActiveMQMessageTransformation in my case) doesn't prevent that from
happening.
It seems that in order to get this bridge to work, we're going to
have to
patch ActiveMQMessageTransformation - or does anyone have a better
idea?
--
View this message in context:
http://www.nabble.com/ActiveMQMessageTransformation.copyProperties-NullPointerException-tp15236447s2354p15268425.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
