Richard S. Hall wrote:
On 3/4/10 1:47 PM, Richard S. Hall wrote:
On 3/4/10 1:24 PM, Sahoo wrote:
Richard S. Hall wrote:
On 3/4/10 12:33 PM, Sahoo wrote:
Richard S. Hall 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.
What did you try to do?
I modified the embeddedgf bundle to point to my GF installation,
built it, deployed it, and started it. I was under the impression
that this would start the GF server.
That should have worked. Do you see any error related to activation
of configadmin bundle? "Appserver Core Bootstraping Classes" bundle
would have tried to start org.apache.felix.configadmin bundle. Are
you not on recent trunk build gf? If not, please use a recent build
of glassfish.
I was using the v3 release, I believe. Must I use a trunk build?
Yes, for embeddedgf to work as outlined in that blog, one needs to use a
more recent build from trunk.
Ok, I built GF trunk and tried it on both Felix framework 2.0.4 and
trunk. It didn't quite work in either case, but the behavior looks the
same in either case:
The server does start to some degreee since I am able to see the admin
console "loading" page, but the admin console never finishes loading.
I am seeing CNFEs for javax.transactions.TransactionManager.
My guess is that we need to configure some framework properties to get
it to work, but I am not sure.
GlassFish configures a few things in config.properties:
1. The system packages needs to be correctly set. Felix by default
exports javax.transaction package by system bundle with
version=${jre.version}, but jre has only a couple of exception classes
from that package. Sometimes jre.version is actually higher than the
actual versions of those packages - I know OSGi version of Java SE and
EE packages is hot topic right now. So, GlassFish configures that
package the following way:
javax.transaction; javax.transaction.xa;partial=true; mandatory:=partial, \
It also adds javax.transaction, javax.transaction.* to bootdelegation
list to avoid loader constraint violation, as javax.sql package, part of
JRE, references classes from javax.transaction package.
From the description of your problem, it may be related to the above
configuration.
2. We also set
org.osgi.framework.bundle.parent=framework so that JDK's tools.jar and
jars from jre.ext.dirs are available to bundles.
If you look at config.properties that's distributed by GlassFish, it
contains comments explaining these changes.
Thanks,
Sahoo
-> richard
-> richard
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
