In order to consume an OSGi service, you need a BundleContext which will be
only available if you depeloy your WAR as a WAB. If you can't convert your
WAR to WAB, then we provide options to convert it on the fly. Wait for
GlassFish 4.0 where we expose this conversion facility via asadmin deploy
command. We have an enhancement request in the system to be able to customize
the service criteria of @OSGiService annotation using system property or
configuration admin. Once we do that you will be able to customize the
injection point on the fly. So, over all answer is these things are possible.
Sahoo
--
[Message sent by forum member 'ss141213']
View Post: http://forums.java.net/node/896631