"Dimitris" wrote : | Lets say we have: | | a.bean | |-b.bean | |-c.jar | | And just 3 deployers, registered in that priority order: | | (C)lassLoadingDeployer -> (B)eanDeployer -> (J)ARDeployer. | | After the deployment structure is analyzed (by the bean & jar deployers) we have the corresponding DeploymentContext/subcontexts in place with each one having recorded its own url as a classpath. | | How 2nd stage deployment processing would work in this case, wrt depth and priority (.jar comes before .bean, according to suffix rules) | | C(c.jar) C(b.bean) C(a.bean) | B(c.jar) B(b.bean) B(a.bean) | J(c.jar) J(b.bean) J(a.bean) | | Or | | C(c.jar) B(c.jar) J(c.jar) | C(b.bean) B(b.bean) J(b.bean) | C(a.bean) B(a.bean) J(a.bean) | | Also, in the 1st case, should the MainDeployer control the traversal, or simply pass the base context to each deployer, and he traverses at will? | | Finally, what would the ClassLoadingDeployer do? | | Judging from the 3.x/4.x mechanism it seems to be creating a UCL for the base node, then adding the classpath of all subnodes to this UCL. (but processing here is parent first). | | Should I just go to the top most deployment, create a plain URLClassLoader, add all classpaths, and point to it from subcontexts? |
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863396#3863396 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863396 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
