In geronimo-openjb Matt Hogstrom found a problem in daytrader with message-destination-ref handling. Instead of a jndi link to

java:comp/geronimo/env/jms/TradeStreamerTopic

which would work we were getting links to

java:openejb/Resource/jms/TradeStreamerTopic

which didn't work. It appears that, in geronimo, first a GeronimoMappedName is set up to mark a link as in the working link above. However later there's some code that appears to be trying to link up any unassigned message destination refs with an openejb resource link, and it was ignoring the mapped name. Changing the code to only add the resource link if there is no mapped name fixed the geronimo-openejb problem.

I have a really hard time following this jndi code in openejb but i don't quite see where the message-destination-link is being followed. I would sort of expect that it might be followed in this resource link code... so I hope that it is being followed correctly somewhere. Is there a test where the message-destination-ref-name is different from the message-destination-link?

Anyway this is tracked in GERONIMO-3306 and the fix is rev 555412.

thanks
david jencks

Reply via email to