[GLASSFISH-11611] ejb-jar shared by different applications Created: 25/Feb/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: classloader
Affects Version/s: 3.1
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: felipegaucho Assignee: Sanjeeb Sahoo
Resolution: Unresolved Votes: 10
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 11,611


— Scenario:

  • an ejb-jar containning the code related to a JPA persistence layer.
  • two (or more) web-applications that depends on the above ejb-jar.

— Today solution:

None, people need to invent alternative solutions like to deploy the ejb-jar in
the Glassfish lib folder or to re-pack the ejb-jar in each of the differente
applications. The former solution open a security breach and the latter forces a
complicated synchronization between the deployment artifacts every time the
persistence layer is modified.

People also reported problems using Hibernate with the ejb-jar shared through
the Glassfish lib folder. Since a Stateless session bean is already loaded in
one classloader, Glassfish throws exceptions if a second application tries to
load the same EJB.

— Proposed feature:

Glassfish should support the deployment of ejb-jar as "sharable resource",
including security management on what application can access the resource and
managing the classloader issues related to such feature.

Comment by rodgarcialima [ 25/Feb/10 ]
      • Issue 11611 has been confirmed by votes. ***
Comment by vladperl [ 25/Feb/10 ]

There are plenty cases when the deployment of ejb-jar as "sharable resource" make
perfect sense.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Thu Apr 27 19:15:19 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.