Re: Customizing the dynamic deployer chain

I'd like to kind of drop the hardcoded chain logic and freeze it until somebody get enough motivation and time to rework it in a sortable way (maybe even sortable events). Last one is an option but surprised there is no way to do it already - I know I did a couple of time but could have been a bit

Re: Customizing the dynamic deployer chain

The latest event that is fired before the AutoConfig deployer is the BeforeDeploymentEvent, which is fired too early and does not contain the AppModule object. A few ideas come to mind 1. Back to my original idea of extracting the deployer chain creation to a protected method. This should be safe

Re: Customizing the dynamic deployer chain

try this: @Observes Object you will spy them all ;) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: Customizing the dynamic deployer chain

Hi, That event is fired too late :) When it's fired, the AutoConfig deployer has already created the datasource. Is there an event fired just before the AutoConfig deployer ? Kind regards, Svetlin 2017-02-24 16:23 GMT+02:00 Svetlin Zarev : > This event is quite