Re: [JBoss-dev] WL Deployer, II
This is not going to work as many users already have stated they create deployment units that contain all app server DDs and even proprietary descriptors for their own use. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Andreas Schaefer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 15, 2002 3:13 PM Subject: [JBoss-dev] WL Deployer, II Hi Geeks Based on an email of Dain I think the easiest way to start is to use the Deployer's accept() method and add additional test in the current deployers there that only JBoss compliant are deployed. Now the Foe-Deployer can check it if not compliant and then try to convert it to a JBoss compliant deployment which is then resent to the Main Deployer for another try. This wouldn't require a new Main Deployer or add any dependencies into the existing deployers. Any objects to add this tests to the existing deployers ? Most likely I will test for JAR if jboss.xml is available, in WAR that either jboss-web.xml is available or no other DD is there except web.xml, for EARs I don't know. x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] WL Deployer, II
Hi Scott This is not going to work as many users already have stated they create deployment units that contain all app server DDs and even proprietary descriptors for their own use. I don't think it would cause problems because I don't check if there are foe DDs but if the archives misses necessary JBoss specific DDs. That is how I think the test would work: JAR archvies: - check if jboss.xml is there if not then it is treated as foe WAR archives: - check if jboss-web.xml is there - if not then check if another foe deployment descriptor is available (I know this is weak and we have to go over it if this and check if for the supported foes this is true or if they can contain data which would not required a jboss-web.xml file). If FOUND then treat is as foe EAR archives: I don't know if there are vendor specific DDs but I guess we don't need currently to make a mapping because we don't have a JBoss specific DD for EARs. Andy ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] WL Deployer, II
I'm saying that users are including jboss.xml, weblogic.xml, sun-j2ee-ri.xml, ... DDs in the deployment build because they want a one deployment unit works with all servers package. This is not going to work as many users already have stated they create deployment units that contain all app server DDs and even proprietary descriptors for their own use. I don't think it would cause problems because I don't check if there are foe DDs but if the archives misses necessary JBoss specific DDs. That is how I think the test would work: JAR archvies: - check if jboss.xml is there if not then it is treated as foe This condition is true for many of our current ejb jars in the testsuite. WAR archives: - check if jboss-web.xml is there - if not then check if another foe deployment descriptor is available (I know this is weak and we have to go over it if this and check if for the supported foes this is true or if they can contain data which would not required a jboss-web.xml file). If FOUND then treat is as foe A jboss-web.xml descriptor is required even less frequently. EAR archives: I don't know if there are vendor specific DDs but I guess we don't need currently to make a mapping because we don't have a JBoss specific DD for EARs. Supporting third party deployment packages is to me a pure filtering service that should not affect our core deployment processing. Its a big enough mess in there as it is without this added in. ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] WL Deployer, II
on 16-05-2 01.18, Scott M Stark at [EMAIL PROTECTED] wrote: because they want a one deployment unit works with all servers package. What can We be part of Invent here ? ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] WL Deployer, II
Hi Scott For the sake of stability and easier to use the accept() is not a good choice. So I guess the only thing we can do is really to create a second Main Deployer providing another domain of deployment. Now I can add a Scanner on a different directory (like the Farm) and use the Foe-Deployer directly. Isn't there a way in the current MainDeployer to create different domains of deployment where each domain has its own scanner(s) and deployers ? Or would it work to ask the user to rename the files: myStupidWLApplication.jar - myStypidWLApplication.wl.jar ? Andy I'm saying that users are including jboss.xml, weblogic.xml, sun-j2ee-ri.xml, ... DDs in the deployment build because they want a one deployment unit works with all servers package. This is not going to work as many users already have stated they create deployment units that contain all app server DDs and even proprietary descriptors for their own use. I don't think it would cause problems because I don't check if there are foe DDs but if the archives misses necessary JBoss specific DDs. That is how I think the test would work: JAR archvies: - check if jboss.xml is there if not then it is treated as foe This condition is true for many of our current ejb jars in the testsuite. WAR archives: - check if jboss-web.xml is there - if not then check if another foe deployment descriptor is available (I know this is weak and we have to go over it if this and check if for the supported foes this is true or if they can contain data which would not required a jboss-web.xml file). If FOUND then treat is as foe A jboss-web.xml descriptor is required even less frequently. EAR archives: I don't know if there are vendor specific DDs but I guess we don't need currently to make a mapping because we don't have a JBoss specific DD for EARs. Supporting third party deployment packages is to me a pure filtering service that should not affect our core deployment processing. Its a big enough mess in there as it is without this added in. ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] WL Deployer, II
If we don't currently support deployment domains with different policies we need to as converting third partly packages is only one use case. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Andreas Schaefer [EMAIL PROTECTED] To: Scott M Stark [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, May 15, 2002 5:41 PM Subject: Re: [JBoss-dev] WL Deployer, II Hi Scott For the sake of stability and easier to use the accept() is not a good choice. So I guess the only thing we can do is really to create a second Main Deployer providing another domain of deployment. Now I can add a Scanner on a different directory (like the Farm) and use the Foe-Deployer directly. Isn't there a way in the current MainDeployer to create different domains of deployment where each domain has its own scanner(s) and deployers ? Or would it work to ask the user to rename the files: myStupidWLApplication.jar - myStypidWLApplication.wl.jar ? Andy ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] WL Deployer, II
1. Multiple domains could be set up pretty easily if we reversed the dependency between MainDeployer and SubDeployers. Subdeployers would be standalone, MainDeployer would have a depends-list of all the subdeployers it used. At least one complete deployer would have to be in the non-auto-deployed startup jboss-service.xml. 2. This idea of foe-deployer (I love the name) is really similar to my idea of xslt based deployment, where deployment consists of transforming all the dd's to mbean configuration, then deploying the mbeans. I've been hoping to get back to this for a couple months. Thanks david jencks On 2002.05.15 20:55:44 -0400 Scott M Stark wrote: If we don't currently support deployment domains with different policies we need to as converting third partly packages is only one use case. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Andreas Schaefer [EMAIL PROTECTED] To: Scott M Stark [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, May 15, 2002 5:41 PM Subject: Re: [JBoss-dev] WL Deployer, II Hi Scott For the sake of stability and easier to use the accept() is not a good choice. So I guess the only thing we can do is really to create a second Main Deployer providing another domain of deployment. Now I can add a Scanner on a different directory (like the Farm) and use the Foe-Deployer directly. Isn't there a way in the current MainDeployer to create different domains of deployment where each domain has its own scanner(s) and deployers ? Or would it work to ask the user to rename the files: myStupidWLApplication.jar - myStypidWLApplication.wl.jar ? Andy ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
