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. >I have a feeling Felix is probably taking longer to ensure a consistent class >space because of some resolver limitations in Felix. To work around this >resolver limitation, Glassfish uses a slightly different system package >export list (e.g., JAXB and JAX-WS packages are not exported by system >bundle). You can try out by using config.properties distributed by >glassfish (found in glassfish/osgi/felix/conf/config.properties). I have >tried this successfully. I know Felix dev team, Richard in particular, >are working very hard to improve this aspect of Felix resolver and they >have already made significant progress. If you used latest trunk, you >might not even face this problem. I had started with Felix 2.0.1, but I just grabbed 2.0.4 and will try again to see how it goes. I'll post the results when I get a chance. Thanks, Larry --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
