RE: [Springframework-developer] Re: JmsTemplate102

[Mark P. <mar...@co...>]

Hi,

Interesting, I guess you would like to have it as a convenience class to
write code like this

public class JmsOrderGateway extends JmsGatewaySupport implement
OrderService
{
	public void sendOrder(Order o)=20
	{
		getJmsTemplate().send(o);
	}
}


In this case you would configure the JmsOrderGateway with an instance of
JmsTemplate that has a default destination and MessageConverter to =
convert
an Order object to jms messages.   Another stub implementation of
OrderService could be used for testing purposes....  Or maybe one based =
on
email?  MailGatewaySupport anyone?

One difference with the DAO analogy is that there is not a corresponding
unified exception hierarchy across different messaging systems.  We had
thought of providing a common messaging exception hierarchy but it =
didn't
seem there was enough meaningful overlap among different messaging
implementations to provide value and the JMS hierarchy is pretty good.
Certainly interested in discussing the point some more though...

Cheers,
Mark




> -----Original Message-----
> From: spr...@li...=20
> [mailto:spr...@li...]
>  On Behalf Of Stig Kleppe-Jorgensen
> Sent: Wednesday, August 04, 2004 5:30 AM
> To: spr...@li...
> Subject: [Springframework-developer] Re: JmsTemplate102
>=20
>=20
> j=FCrgen h=F6ller[ werk3AT] <juergen.hoeller <at> werk3at.com> writes:
>=20
> >=20
> > 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=20
> creating=20
> > dynamic
> destinations), we
> > thought that JmsTemplate102 should use the same approach.
> >=20
> > I agree that separate QueueJmsTemplate and TopicJmsTemplate=20
> subclass=20
> > of
> JmsTemplate would have been a
> > viable strategy too. The pubSubDomain flag would have been somewhat=20
> > confusing
> there, though.
> >=20
> > After all, the JMS 1.0.2 style is not for the long term=20
> anyway, as I=20
> > expect
> it to be superseded by JMS 1.1 quite
> > quickly. That's also the reason why JmsTemplate is not called=20
> > JmsTemplate11
> anymore but rather uses the
> > generic name.
>=20
> Ok, that sounds good :-)
>=20
> Are you planning to add a JmsDaoSupport (like=20
> HibernateDaoSupport) as a convenience class? I've done that=20
> myself in code I'm writing and think it works out well.
>=20
> Regards,
> Stig
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the=20
> changes on Linux.com, ITManagersJournal and NewsForge in the=20
> past few weeks? Now, one more big change to announce. We are=20
> now OSTG- Open Source Technology Group. Come see the changes=20
> on the new OSTG site. www.ostg.com=20
> _______________________________________________
> Springframework-developer mailing list=20
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20