Patches item #542341, was opened at 2002-04-10 22:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=542341&group_id=22866
Category: JBossMX Group: v3.0 Rabbit Hole (unstable) Status: Open Resolution: None Priority: 5 Submitted By: Larry Sanderson (lsanders) Assigned to: Nobody/Anonymous (nobody) Summary: Fixed Deployment of Exploded Archives Initial Comment: These patches allow exploded archives to be deployed. Most of the code for this was already in place, and as such these patches are mostly trivial. EARDeployer,EJBDeployer,RARDeployer,SARDeployer: I simply modified the accept methods to take directories. JARDeployer: Fixed a bug - it was reading the META-INF directory of rt.jar instead of the local archive. MainDeployer: Added the ability for SubArchives to be deployed from a directory. I also limited subDeployment to the first directory depth (i.e. a jar file two directories down will no longer be deployed). Is this correct? It could break existing archives, but I don't think anyone actually placed sub-deploment archives any deeper than the root directory. Added an MBean Operation called getWatchUrl(URL). This operation takes the URL of any deployed service/archive, and it returns the URL that should be checked for modification (i.e. META-INF/jboss- service.xml for exploded sar files, etc..). This is used by URLDeploymentScanner to help redeploy exploded archives. URLDeploymentScanner: Utilized the new MainDeployer's getWatchUrl operation within the isModified method. Also, allow the filescanner to deploy directories. I hope this helps, and I'm sorry if the code isn't pristine - I'm still gettting used to the JBoss layout. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=542341&group_id=22866 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
