As I said that blog is old. In the latest implementation, stateless EJBs
with local business interface automatically get deployed as OSGi
services. You can which EJBs to be registered as service via Export-EJB
manifest header which takes a list of EJB names. It takes a special
value called ALL to indicate that all stateless EJBs with local business
interfaces be exposed as OSGi service. Please look at a more recent
sample which demonstrates this:
http://weblogs.java.net/blog/ss141213/archive/2010/03/30/ejb-osgi-service-demo-eclipsecon
Given that blogs are not good for changing implementations, I have
started to maintain a Wiki page [1].
Thanks,
Sahoo
[1]
http://wiki.glassfish.java.net/Wiki.jsp?page=OSGi
On Tuesday 08 June 2010 06:46 PM, glassfish_at_javadesktop.org wrote:
> The nightly build of yesterday yes.
>
> My use case is exactly what was shown in the blog: Back session EJB by OSGi bundles. The latter contain changeable business logic we can substitute easily without a full redeploy cycle of the complete application.
>
> In the meantime I've made it work by adding a bundle listener in the activator. That seem to work as the EJB is being deployed before the bundle gets the STARTED state.
>
> Now, if the EJB's are also deployed as OSGi services of course... :-) You do have an example somewhere as of the classes I should use to get to those services ?
>
> Thanks !
> [Message sent by forum member 'jan_goyvaerts']
>
> http://forums.java.net/jive/thread.jspa?messageID=473325
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>