I believe there is a mechanism in JBoss for sharing dependencies by
creating modules for them and installing them in the server itself, but
if you have more than one or two, it's probably more trouble than it's
worth.
Alternatively, you might consider turning your apps into libraries,
forming a si
Murtaza:
Technically it may be possible. The first naive approach that comes to mind is
a classloader per dependency that would be specific to the particular version
of the dependency an application needs (the version is needed because the other
applications could require a different version of
Murtaza:
On Jul 6, 2012, at 7:01 AM, Murtaza Husain wrote:
> Three requests -
> (msg/respond "/queue/work" (partial apply *) :selector "operation='multiply'")
> 1) Can the topic and queue be expressed as :queue/work or :topic/work, like
> datomic style ?
That would be trivial to implement. Can
Toby,
Most of my apps have almost similar dependencies, anyway those can be
shared between runtimes ?
Murtaza
On Friday, July 6, 2012 5:12:50 PM UTC+5:30, Toby Crawley wrote:
>
> Murtazza:
>
> The memory cost of the isolated runtimes is much lower than a JVM per app
> since we don't duplicate
Murtazza:
The memory cost of the isolated runtimes is much lower than a JVM per app since
we don't duplicate every class. Anything loaded by the system class loader
(java.*, javax.*, etc) and any java classes needed by Immutant itself are not
duplicated - only classes loaded from the app's depe
Hi Jim,
Congratulations on 0.2, and the new messaging API is beautiful.
Three requests -
(msg/respond "/queue/work" (partial apply *) :selector "operation='multiply'")
1) Can the topic and queue be expressed as :queue/work or :topic/work, like
datomic style ?
2) Can the message {"operation"
Hi Jim,
"Multiple apps can be deployed to a single Immutant, each with its own
isolated runtime"
How much cost in terms of memory does the isolated runtime extract ? I
assume by isolated runtime it means that all dependencies are laded in a
separate runtime. usually starting a separate JVM for
We released our second version of Immutant today. Read all about it here:
http://bit.ly/immutant020
For those unfamiliar with Immutant, here are the high points:
- Simple functions with side effects triggering JBoss AS7 services
- Very dynamic, no XML or YAML config, just Clojure
- Depl