Larry Touve wrote:
On 3/4/10 12:33 PM, Sahoo wrote:
On 3/4/10 11:09 AM, Richard S. Hall wrote:
Good point. I will try on Felix trunk and see what happens...
On trunk, I see a bunch of bundles get deployed, some get resolved,
but the only active bundle is:
[ 113] [Active ] [ 1] Appserver Core Bootstraping Classes
(3.0)
There were no errors and the framework appears to be running fine as
far as I can tell.
After installing Felix 2.0.4, copying the config.properties file from the
Glassfish's Felix directory to my 2.0.4 install directory, and editing it
slightly (comment out the autostart line for Glassfish) it looks like things
are OK. I'm not sure if Felix 2.0.4 made a difference, or if I just mucked
something up before.
I also modified the embeddedgf code to point to my GF install, then built and
installed it. Of all the installed bundles, only the following are Active:
Appserver Core Bootstraping Classes (org.glassfish.core.glassfish)
OSGi GlassFish Embedder (sahoo.embeddedgf)
This list does not look complete to me. I expected to see bundles like
com.sun.enterprise.osgi-adapter in ACTIVE state given that you have
mentioned you could access default welcome page and all. You might have
looked at the bundle state while glassfish was still starting.
I am able to hit the default welcome page, and log in to the GF admin console.
When I start up glassfish using asadmin I noticed that there are 40+ active
bundles, and some of the bundles that have missing dependencies when I start up
using embeddedgf (see below) are active when started up via glassfish. I'm not
quite sure what this means yet, as I haven't deployed anything to glassfish
yet, nor have I deployed any other bundles.
This probably has to do with system package export list.
I saw the following exceptions in the log, although they don't seem to be
critical:
-> org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.felix.configadmin:1.2.4
You are right. All those exceptions of type
"org.osgi.framework.BundleException: Bundle symbolic name and version
are not unique" are not critical, as they are appearing because
GlassFish distributes Felix shell, configadmin bundles and in your case,
they were already installed from bundle/ directory of Felix.
As for the missing dependencies, this is an example of what I see when I click
on a bundle that is not Active in the Felix Web Console (not all have
unresolved issues, just some):
Don't worry about all bundles not being ACTIVE or RESOLVED. GlassFish
lazily activates bundles. Unresolved constraints need attention. I am
not sure why this bundle is not able to get all its imports wired. All
those required packages are exported by glassfish modules. Try starting
the following bundle and see if there are unresolved constraints.
I am also confused as to see the bundle version. It is 3.0.0.b74b, which
matches with that of GlassFish 3.0 FCS release. You should be trying out
latest trunk builds (those 3.1-SNAPSHOT builds) to get the embeddedgf to
work.
I have one question for you. Do you have a need to embed glassfish in an
OSGi runtime at this point of time?
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
