Re: [Springframework-developer] JmsTemplate102

[<jue...@we...>]

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.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Stig Kleppe-Jorgensen
Sent: Monday, August 02, 2004 3:55 PM
To: spr...@li...
Subject: [Springframework-developer] JmsTemplate102


Hi!

Just playing around with the JMS-support (it's looking great!) and was =
puzzled
that JmsTemplate102 is not divided in 2 classes, one for Queues and one =
for
Topics. Are there any reasons why this is not done? Looks like a better =
OO
solution than having a bunch of if/else's...

Regards,
Stig Kleppe-Jorgensen



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer