Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Tom <tom400f@gmail.com>
Newsgroups: comp.lang.java.programmer
Subject: Re: Any open source solution with JMS and server-side clustering?
Date: Thu, 9 Jun 2011 20:33:32 +0000 (UTC)
Organization: Aioe.org NNTP Server
Lines: 35
Message-ID: <israms$m1i$1@speranza.aioe.org>
References: <c79dd756-8bfa-435e-872b-e1b8339e2413@glegroupsg2000goo.googlegroups.com>
NNTP-Posting-Host: Vd3zjYYo2heJAT9ZVcrkiA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: Pan/0.133 (House of Butterflies)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5165

On Thu, 09 Jun 2011 10:46:17 -0700, saxo123 wrote:

> Hello,
> 
> maybe my point may be misunderstood. So I try with an analogy: in "good"
> old RMI there were several clients and one server instance. With JMS
> there is no server instance in the sense of RMI as JMS only does the
> transportation. So I'm looking for an open source solution that combines
> JMS with such a server instance on which custom code can be executed.
> Both, JMS and the server instance needs to be clustered. I don't want to
> go with some application server as there is no need for EJBs for my
> application. Thanks for any suggestions. I did search the internet, but
> didn't find anything useful in reasonable time.
> 
> Thanks, Oliver

Not quite sure what you mean in that you are combining
two issues... client/server is one thing (I mean in the sense that
the client is a user front-end) and server components
set up to react in a messaging environment are another.

Anyway, you could consider Inq (mine at http://www.inqwell.com). It has
its own scripting language. Although this may be more than you were
considering it does mean you can reparse (parts of) your application
into the server(s) while they are running. The idea is that enterprise
apps are quick and easy to build. Everything is a map so relationships
(while obviously inferred in the data model) are defined at runtime
according to the needs of the context. Entities are only modelled
and mapped (to a database) once. Inq can call Java and Java can call Inq.

I typically work in situations where time-scales are short, requirements
are poorly specified and subject to change at short notice. No time
for UML designs etc etc.

But if you could be more specific....