On 2001.11.29 17:30:34 -0500 Andreas Schaefer wrote: > Hi Geeks > > Because the "unlocking" of files by the URLClassLoader > does not work we are back at the beginning. > > I suggest these chances to JBoss Deployer: > - all deployment units gets their own directory where they > are copied/expanded there (JAR,EAR,WAR,SAR) which > is unique (maybe "deploy1, deploy2, etc.)
DeployerMBeanSupport does this now (ExpandPackages) > - EAR,WAR and SAR files are expanded as they are into these > deployement directories mentioned above named after the archive what does naming after the archive give you? you need a generated unique name or else use the entire url of the package to guarantee uniqueness, at this point copying the archive name into the path is only to help people trying to figure out what went wrong;-) > - WAR archives in an EAR archive are expanded in a sub-directory > of the EAR deployment directory named after the WAR file I don't know how this works, does j2ee deployer do this or the servlet container? > - "Deployment.java" class will only contain the deployment directory > and the "Application.java" as data container for the root archive > - "Application.java" contains Modules (see Deployment) representing > inner archives > > Based on these changes I will rewrite the J2eeDeployer and Container- > Factory. Later on I will migrate these changes also to the > J2eeScropeDeployer. I would ditch the non-scope deployer. I think figuring out how to specify which scope is an unanswered question. I have a large part of a "universal deployer" written, the idea is to separate the unpacking phase (same for every kind of package) and the dd processing phase (actually done by package specific deployer.) It's very similar to how ServiceDeployer and RARDeployer work now with DeployerMBeanSupport. If you want to collaborate I could send you what I have now, or if you want to use the unpacking services of DeployerMBeanSupport anything you do now could easily be converted to use the UniversalDeployer once I get it done. Or maybe you want to start over;-) I've also been investigating unified deployment descriptors. It turns out it is pretty easy to use xslt to combine the j2ee and jboss deployment descriptors into one which has the basic structure of the j2ee descriptor with jboss stuff appended at the appropriate level of detail. This means you only have to make one pass through the dd, and you can have a single unified (non j2ee) dd if you wish. (Anatoly Akkerman requested this a few days ago). So far I have one that combines ejb-jar and jbosscmp-jdbc (actually a slightly different version of the latter I am working with). If you're interested tell me which files to combine first and I'll write a script. david jencks > > xxxxxxxxxxxxxxxxx > Andreas Schaefer > Senior Consultant > JBoss Group, LLC > xxxxxxxxxxxxxxxxx > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
