JBossDeveloper

If you have stuff you like to contribute (and maintain) you are very welcome. The umbrella project is the home of examples and documentation.

The easiest way to access EJB functionality in OSGi Bundles is to register instances as OSGi Services.

{code}

/**

* Registers osgi services with the (system) bundle injected by the JEE

* container.

*

* @author Rainer Alföldi

*

*/

@Singleton

@Startup

public class Init {

  private static Logger LOGGER = Logger.getLogger(Init.class.getName());

  @Resource

  private BundleContext _bundleContext;

  @Resource

  private XXXResolver _userNameResolver;

....

  @PostConstruct

  private void postConstruct() {

  {

    Dictionary<String, Object> properties = new Hashtable<String, Object>();

  _serviceRegs.add(_bundleContext.registerService(

          UserNameResolver.SERVICE_NAME, _userNameResolver, properties));

  }

....

{code}

I assume XXXResolver is the same as UserNameResolver, which is the EJB being registered as an OSGi service. What is _serviceRegs? Do I get an instance of it through @Resource?

Thanks

Sorry for the late reply.

_serviceRegs is just a Collection of the ServiceRegistrations returned when you register a service.

It is used in

  @PreDestroy

  private void preDestroy() {

    LOGGER.log(Level.INFO, "preDestroy()");

    for (ServiceRegistration serviceReg : _serviceRegs) {

      serviceReg.unregister();

    }

  }

Thanks Rainer.

I get a null for _userNameResolver when I deploy Init as a Singleton EJB in JBoss AS 7.1.1.Final. What is your AS version? Or it’s something else?

        @Resource

        private XXXResolver _userNameResolver;

If I change @Resource to @EJB, it complains about "cannot find EJB with interface XXXResolver". Here I made XXXResolver an interface.

It works if I use JNDI to get hold of EJB XXXResolver. At least it works in a way!

X