[jboss-dev-forums] [JBoss OSGi Development] - Re: HOWTO chage the behaviour of the CL policy

[adrian@jboss.org]

So let's do it the same way. I haven't really looked at this part of the spec yet 
but its certainly something I planned to address.

There's no reason why the SystemBundle classloader couldn't be defined in the
bootstrap to expose the osgi core packages (and maybe some services)
instead of letting them bubble up to the "classpath" using the parent policy.

The other services would just be deployed as bundles.

i.e. just make the parent policy in OSGiClassLoaderSystem 
ParentPolicy.BEFORE_BUT_JAVA_ONLY
then have the following in the bootstrap.xml to be the "system bundle classloader"


  | <deployment xmlns="urn:jboss:bean-deployer:2.0">
  | 
  | 	<classloader><inject bean="system-bundle:4.4.2" /></classloader>
  | 
  | 	<classloader name="system-bundle"
  |                               version="4.4.2"
  |                               xmlns="urn:jboss:classloader:1.0"
  |          >
  | 		<root>${jboss.lib.url}osgi-core.jar</root>
  | 		<root>${jboss.lib.url}jboss-osgi-impl.jar</root>
  |                 <capabilities>
  |                      <package name="org.osgi.framework" version="1.4.0"/>
  |                      <package name="org.osgi.service.packageadmin" version="1.2.0"/>
  |                      <etc./>
  |                  </capabilities>
  | 	</classloader>
  | 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251749#4251749

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251749