Hi Larry,
Larry Touve wrote:
Thanks to all who have been responding.
Having said that, embeddedgf approach should also work. I don't know
what is making you to conclude about missing dependencies when you
follow the instructions in that blog to embed glassfish in felix.
When I 'start' the bundle, it installs the 218 (or so) Glassfish bundles. They
are all in various
States - some active, some resolved, and some installed. At this point I was unable
to access either the root welcome page (localhost:8080) or the admin console
(localhost:4848), as well as 'asadmin list-domains' showed that domain1 was not
running. When I looked at some of the bundles that were either in the resolved
or installed state some listed errors in resolving dependencies. I was using
the Felix Web Console to examine the bundles. At this point, I wasn't sure which
bundles should have been active/resolved/installed, so I focused on getting the
Felix Web Console running in the Glassfish-launched Felix (which turned out to
be
Pretty easy). Running this way showed that the bundles are all in various states
(not all are active), so I stopped Investigating the embeddedgf path.
GlassFish does not activate all bundles. To start with, most bundles
remain in INSTALLED state. They move to RESOLVED state as and when they
participate in class loading - this is taken care by OSGi framework.
GlassFish has a notion of lazy loading of services. As and when services
are needed from bundles, glassfish activates necessary bundles.
In future, when you encounter such problem, run jstack to find more
about the state of the process.
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
