Re: [Springframework-developer] JMS remoting provider available

[<jas...@ma...>]

On 27 Oct 2004, at 19:25, j=FCrgen h=F6ller [werk3AT] wrote:
> James,
>
> That's cool stuff! In particular as it reuses the existing=20
> RemoteInvocation support so nicely. However, I still vote to put it=20
> into the sandbox for the 1.1.x timeframe. Mainly because there is no=20=

> time to polish it, and it's worth to be publically introduced in a 1.x=20=

> release.

Fine with me.

> Also, for the server side, we don't ship facilities to host the=20
> MessageListener (JmsServiceExporter) yet. I see that this is in the=20
> works :-) but we're still lacking recommendations on how to deploy JMS=20=

> remoting end-to-end. One more reason to keep it in the sandbox for the=20=

> time being.

OK - but that's one of the reasons I've been trying to get the=20
JCAContainer going, so we have an end-to-end solution for JMS.


> Finally, I'd prefer jms.remoting as package rather than remoting.jms -=20=

> for a comparison, our transaction manager implementations reside in=20
> jdbc respectively orm.hibernate etc too, rather than in the=20
> transaction package. EJB remoting resides in the ejb package too,=20
> despite reusing facilities from the remoting package.

Ah OK. I just went with remoting.jms to be with the other remoting=20
solutions. I'm easy either way.


> So if you don't object to the sandbox and the changed package name,=20
> I'll move it over to the sandbox into the jms.remoting directory... We=20=

> need to clarify that before the 1.1.2 release, which is scheduled to=20=

> happen this Sunday.

Go for it.

Lemme know what needs doing to get it back in once we're getting ready=20=

for 1.2.


James
-------
http://radio.weblogs.com/0112098/