[jboss-user] [Microcontainer] - Re: Classloading vs. VFS

[ALRubinger]

"jesper.pedersen" wrote : anonymous wrote : 
  |   | Looks like the NCDFE is blocking you from doing that. Which is another issue alltogether. Due to parent>child delegation and leaking of class references, we've got to be very careful what's on the application CP, URLCL, etc. 
  |   | 
  | I only have an AppCL which has my Main and is a parent to the URLCL which has all the JARs. The URLCL is passed to the ServerFactory in bootstrap.

Right, what I'm getting at is the "all the JARs" part.  Take a look at how restrictive/careful we've gotta be in AS, for example:

   /**
  |     * The default list of boot libraries.  Does not include
  |     * the JAXP or JMX impl, users of this class should add the
  |     * proper libraries.
  |     * TODO: use vfs to list the root directory
  |     * http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153175
  |     * 
  |     * Copied from legacy bootstrap ServerLoader
  |     * //TODO JBAS-6920
  |     */
  |    @Deprecated
  |    public static final String[] DEFAULT_BOOT_LIBRARY_LIST =
  |    {
  |          // Concurrent
  |          "concurrent.jar",
  |          // Logging
  |          "log4j-boot.jar", 
  |          "jboss-logging-spi.jar", 
  |          "jboss-logging-log4j.jar",
  |          "jboss-logging-jdk.jar",
  |          "jboss-logmanager.jar",
  |          "jboss-logbridge.jar",
  |          // Common jars
  |          "jboss-common-core.jar",
  |          "jboss-xml-binding.jar",
  |          // Bootstrap
  |          "jboss-bootstrap-spi.jar", 
  |          "jboss-bootstrap-spi-as.jar", 
  |          "jboss-bootstrap-spi-mc.jar",
  |          "jboss-bootstrap-impl-base.jar", 
  |          "jboss-bootstrap-impl-as.jar",
  |          "jboss-bootstrap-impl-mc.jar",
  |          // Microcontainer
  |          "javassist.jar", 
  |          "jboss-reflect.jar", 
  |          "jboss-mdr.jar", 
  |          "jboss-dependency.jar", 
  |          "jboss-kernel.jar",
  |          "jboss-metatype.jar", 
  |          "jboss-managed.jar",
  |          // Fixme ClassLoading
  |          "jboss-vfs.jar", 
  |          "jboss-classloading-spi.jar", 
  |          "jboss-classloader.jar", 
  |          "jboss-classloading.jar",
  |          "jboss-classloading-vfs.jar",
  |          // Fixme aop
  |          "jboss-aop.jar", 
  |          "jboss-aop-mc-int.jar", 
  |          "trove.jar",};

That's in Main.  Any more/less leads to NCDFE.

"jesper.pedersen" wrote : We should make sure that impl-mc meets most of the requirements for projects using the MC as the foundation. Otherwise each project has to implement an extension to fill in the blanks.

So I suppose the question on the table is whether MCServer should init VFS automatically.  While convenient, the thing there is that this isn't really MCServer's job (because it implies VFS will always be used).  Opinions?

S,
ALR

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

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