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 single app that depends on those libraries. Jim Toby Crawley <t...@tcrawley.org> writes: > 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 that dependency). We'd then attach the correct versioned > classloaders to the deployment based on the resolved dependencies and > have the isolated classloader check with those classloaders first. > > I'm not sure at this point if the added complexity of such an approach would > be worth the potential memory savings, but I could possibly be convinced > otherwise. > > - Toby > > On Jul 6, 2012, at 9:19 AM, Murtaza Husain wrote: > >> Toby, >> >> Most of my apps have almost similar dependencies, anyway those can be shared >> between runtimes ? >> >> Murtaza >> -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
