Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Shared Services

    Posted on

    I have a need to create a shared audit service that will be available to all applications running on the server. It seems the correct way to do this would be to create a statemless session bean, install it as a module, and make it global in the config file.

    The creation of the stateless EJB works great. When I deploy it through the deployment directory (by dropping the .jar file there), it registers fine and works great.

    When I then configure it to be a module in the static modules directory structure, it fails to load the bean.

    What I did was create a module.xml file, point it at the jar, set up the dependencies, and set a global module in urn:jboss:domain:ee:1.1.

    The jar IS available globally, as I can reference the classes in the jar from other applications deployed in the deployment directory. It just won't load the stateless bean. This is the same jar that works fine from the deployment directory.

    I have searched for any documentation on how to make this work and cannot find any. Does anyone have a clue how to get this to load? Am I missing some kind of module initialization method or something? There is no error generated. The log looks fine. But the bean is never loaded to JNDI and does not become available for injection into other applications. I can make it work fine by using the JBoss-Structure xml and referencing a dynamic module.


    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ false true

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat