[Cosmo-dev] split open and melt
bcm at osafoundation.org
Thu Oct 11 08:13:51 PDT 2007
On 10/11/07, Randy Letness <randy at osafoundation.org> wrote:
> With multiple wars, would each war have its own services implementation
> or would it be shared (put in tomcat/common/lib)? We probably want them
> shared as we don't want multiple Hibernate SessionFactory instances
> running, and multiple caches, which would require a distributed cache.
> We could package cosmo as an ear instead of war, but that would require
> moving to a different appserver.
both are possible. the default deployment would be to use a shared
provider jar. this also has the effect of moving all of hibernate's
runtime dependencies out of the wars into the shared area as well,
which lets us save PermGen space.
we could also share the api jar and any other jars depended on by
multiple wars. i'm not sure how much of a win that is, though; it puts
a dependency management burden on snarf, and it makes things more
difficult for people who want to use a container other than tomcat.
packaging an ear is a great alternative for people using ejb
containers, and we should eventually do that no matter what.
More information about the cosmo-dev