ok, the packaging ordering/nesting is clearly defined in the current deployer (at least until jason removed ordering on his own).
clearly inner packages are deployed before outer. and there was an order at the same level xml>sar>rar>ear>war>ejb or something like this. btw jason, we really need this back, THEN, yes i agree that forcing order through containment needs to be enhanced by some explicit dependency order. Until we get the full xml dependency at the jsr77 or mbean level, we can use the deploy/first/second third which should cover most if not all cases. marcf |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott |M Stark |Sent: Tuesday, March 12, 2002 9:33 PM |To: [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] ordering proposal | | | |Ordering should not be a function of the packaging. I should |be able to create an ear with a flat hiearchy of sars, jars, |wars and specify the startup order. I don't see the need to |allow arbitrary composition of packages. We flattened the |class loader heirarchy because it was a pain to get right. Why |not do the same for deployment packages. The maxium packaging |depth would be ear/war/jar as this is allowed by the j2ee spec. | |The standard j2ee descriptor references are not sufficient to cover |the dependencies. The ejb has no direct knowledege that it is using a |custom JRMPInvoker service. Likewise, if a service is using an |ejb or servlet how is this specified? | |----- Original Message ----- |From: "David Jencks" <[EMAIL PROTECTED]> |To: <[EMAIL PROTECTED]> |Sent: Tuesday, March 12, 2002 7:39 PM |Subject: Re: [JBoss-dev] ordering proposal | | |> Are you sure it is that hard to understand or do? Usually the default |> order of peer subpackages works fine: if you want something else you can |> use nesting. |> |> I think that if we can convert jndi dependencies into mbean |dependencies a |> lot of problems will go away without any more deployment descriptors such |> as an explicit list of what order to deploy subpackages in. |> |> For instance, I would like to convert a resource-ref into an mbean |> dependency on the e.g. connection factory so the ejb won't deploy until |the |> connection factory is set up. Similarly, ejb-links can be converted into |> mbean dependencies so the ejb will just wait to start until all |the others |> it uses are available. |> |> david jencks |> |> On 2002.03.12 22:21:40 -0500 Scott M Stark wrote: |> > Having to nest jars in a particular manner to achieve the correct |> > deployment ordering certainly is not simple. Here your talking |> > about the static deployment directories while all of the current |> > issues are with self-contained deployment units of j2ee components |> > and services. We need a simple mechanism for handling the |> > ordering of component deployment within a xar. |> > | | | |_______________________________________________ |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
