RE: [JBoss-dev] init/create calls with subpackaging not in the same order
Hello David, I doubt it is essential, however... init usually just identifies the deployment descriptor and file to watch. There is some advantage to locating this as soon as possible, to help avoid runaway redeploys in case of failure later. If an expected deployment descriptor is missing, you could stop immediately. Create and start pretty much need to be done inside out since usually outside packages depend on whats inside (applications depending on their ejb modules for instance). OK, thank you for explaining. You may doubt it is essential but in fact it is when you build such compound packages that depend on others: you need to know what to package in what. If P1 depends on P2, do I need P1 in P2 or P2 in P1? Which is why I was asking. And you gave me a brillant answer! Cheers, Sacha ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] init/create calls with subpackaging not in the same order
Hello, In the MainDeployer code, when you deploy a package containing sub-packages: - init will be called on the wrapping package first, then on the inside packages - create will be called on the inside packages first, then on the wrapping package Why this logic? I don't mean I consider it to be wrong, it is just that I don't see the rational behind it. Thank you. Cheers, Sacha P.S.: I was reading version 1.22, maybe it has changed since Saturday. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] init/create calls with subpackaging not in the same order
On 2002.02.25 03:47:06 -0500 Sacha Labourey wrote: Hello, In the MainDeployer code, when you deploy a package containing sub-packages: - init will be called on the wrapping package first, then on the inside packages - create will be called on the inside packages first, then on the wrapping package Why this logic? I don't mean I consider it to be wrong, it is just that I don't see the rational behind it. I doubt it is essential, however... init usually just identifies the deployment descriptor and file to watch. There is some advantage to locating this as soon as possible, to help avoid runaway redeploys in case of failure later. If an expected deployment descriptor is missing, you could stop immediately. Create and start pretty much need to be done inside out since usually outside packages depend on whats inside (applications depending on their ejb modules for instance). Thanks david jencks Thank you. Cheers, Sacha P.S.: I was reading version 1.22, maybe it has changed since Saturday. ___ 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
