|
From: Stig Kleppe-J. <sj...@on...> - 2004-08-04 09:30:14
|
jürgen höller[ werk3AT] <juergen.hoeller <at> werk3at.com> writes: > > Well, given that JmsTemplate for JMS 1.1 can use a uniform manner of accessing queues and topic, and that > JmsTemplate itself already has a pubSubDomain property (for creating dynamic destinations), we > thought that JmsTemplate102 should use the same approach. > > I agree that separate QueueJmsTemplate and TopicJmsTemplate subclass of JmsTemplate would have been a > viable strategy too. The pubSubDomain flag would have been somewhat confusing there, though. > > After all, the JMS 1.0.2 style is not for the long term anyway, as I expect it to be superseded by JMS 1.1 quite > quickly. That's also the reason why JmsTemplate is not called JmsTemplate11 anymore but rather uses the > generic name. Ok, that sounds good :-) Are you planning to add a JmsDaoSupport (like HibernateDaoSupport) as a convenience class? I've done that myself in code I'm writing and think it works out well. Regards, Stig |