[wildfly-dev] does Attachments.NEXT_PHASE_DEPS wait for async services or does the next DUP phase start as soon as the service.start returns...

Scott Marlow smarlow at redhat.com
Fri Jun 20 10:05:32 EDT 2014


On 06/20/2014 09:52 AM, Scott Marlow wrote:
> On 06/20/2014 09:25 AM, Stuart Douglas wrote:
>>
>>>>
>>>
>>> Thanks Stuart. Is there a way to get EAR subdeployments to run in the
>>> same phase? Seems like the .war subdeployment is reaching the
>>> POST_MODULE PHASE before the .jar subdeployment does.
>>
>> So they do actually run in the same phase, kinda. With an ear first the
>> top level deployment runs a phase, and then all sub deployments run the
>> same phase in parallel.
>>
>> I think the problem here is that NEXT_PHASE_DEPS only applies to the
>> current deployment. So all the modules will run FIRST_MODULE_USE, but
>> only the jar will actually wait for the PU to be installed before
>> running post module, the top level and war deployments will run
>> POST_MODULE to completion (but nothing more will happen until the jar
>> deployment has also run POST_MODULE).
>>
>> I think you need to make sure that every deployment/subdeployment ends
>> up with the NEXT_PHASE_DEP set up.
>
> Ah, excellent solution!  Thanks Stuart!

I created WFLY-3531 for this.

>
>>
>> Stuart
>>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>



More information about the wildfly-dev mailing list