<div dir="ltr"><div dir="ltr">The DUPs in each Phase are executed in the start method of an MSC Service that represents that Phase for that deployment.[1] The start method executes the DUPs associated with the phase and then installs the service for the next phase.</div><div dir="ltr"><br></div><div dir="ltr">So, all DUPs for PARSE will have run before any DEPENDENCIES DUPs are run.<br><div><br></div><div>[1] <a href="https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/org/jboss/as/server/deployment/DeploymentUnitPhaseService.java#L85">https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/org/jboss/as/server/deployment/DeploymentUnitPhaseService.java#L85</a></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 18, 2018 at 11:01 AM, Peter Palaga <span dir="ltr"><<a href="mailto:ppalaga@redhat.com" target="_blank">ppalaga@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi *,<br>
<br>
I cannot find any info about what (if any) are the guarantees for <br>
ordering and exit of DeploymentUnitProcessors (DUPs) in case of an EAR <br>
that contains multiple WARs.<br>
<br>
I have a situation like this: MyDUP1 is registered for Phase.PARSE and <br>
MyDup2 is registered for Phase.DEPENDENCIES.<br>
I can see from the logs that MyDUP1.deploy(ear), <br>
MyDUP1.deploy(ear.war1), MyDUP1.deploy(war2), etc. are executed by <br>
distinct threads which is perfectly OK.<br>
I'd like to know if there is any guarantee that MyDup2.deploy(*) <br>
observes the completion of MyDUP1.deploy(ear), MyDUP1.deploy(ear.war1), <br>
MyDUP1.deploy(ear.war2), etc.?<br>
<br>
MyDUP1.deploy() collects some info from the EAR and the WARs and stores <br>
it as an attachment of the DeploymentUnit. MyDup2.deploy() is supposed <br>
to read that attachment and so it is important that the info is complete <br>
when MyDup2.deploy() reads it.<br>
<br>
Thanks,<br>
<br>
-- Peter<br>
______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div>
</div>