11 Replies Latest reply on Mar 2, 2010 6:16 PM by Ales Justin

    Deployment lazyResolve and lazyStart

    Adrian Brock Master

      With https://jira.jboss.org/jira/browse/JBDEPLOY-247

       

      You can now do lazyResolve and lazyStart for deployments.

      However, beyond what OSGi will do there's nothing that actually sets this up.

       

      I propose we add a new META-INF/jboss-deployment.xml which would be some generic

      metadata for this kind of processing and other possible deployment control parameters.

       

      e.g. something like

       

      <deployment xmlns="urn:jboss:deployment:1.0">

       

          <!-- Deploy this deployment in the described stage initially - i.e. no classloader -->

          <required-stage>DESCRIBE</required-stage>

       

          <!-- Only create the classloader when somebody wants to import our package or module -->

          <lazy-resolve/>

       

          <!-- Only move the deployment to the REAL stage when somebody loads a class from our classloader - with an optional filter -->

          <lazy-start filter="com.acme.somepackage"/>

       

      </deployment>