Announcement Announcement Module
Collapse
No announcement yet.
SingletonBeanFacotryLocator and WebSphere Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • SingletonBeanFacotryLocator and WebSphere

    Anyone have any luck getting websphere (5) to have a single shared application context among multiple EJBs?

    My EAR strucuture is something like:
    myapp.ear
    - webapp1.war
    - webapp2.war
    - ejb1.jar
    - mdb1.jar
    - mdb2.jar
    - APP-INF/lib/spring.jar
    - APP-INF/lib/foo.jar
    - APP-INF/lib/blah.jar

    The EJBs/MDBs are just thin facades that delegate to a spring managed bean, and they are configured to use SingletonBeanFactoryLocator to fetch the bean factory reference. The web applications are also configured to have the parent context fetched through the same mechanism. Each war/ejb/mdb module has the manifest classpath set with all the utility jars in APP-INF lib as well.

    I have this working in WLS fine, using the APP-INF/lib capability, and only one instance of the root context is created. On WAS5, however, each module ends up loading it's own copy of the context, which isn't what I'm looking for. I'd rather not have to go down the route of having to package utility jars outside the EAR, so if anyone has gotten to behave more like WLS, I'd appreciate any insight you might have.
Working...
X