One deployment fails at boot, all deployments fail

[nickarls]

Hi,

    I noticed that https://issues.jboss.org/browse/AS7-783 was rejected but has the last year brought any new information that would allow this to be re-opened?

    Currently, all deployments are apparently deployed in a composite operation at boot and if one application fails to deploy, all deployments fail (regardless if they are related or not).

If I remove all .failed-markers, the same thing happens. If I remove all .failed-markers other than the broken one, the remaining applications deploy. Sure, you should know who deploys what

to your AS but the current behaviour carries the risk that a server boot could result in a running AS with no deployed applications.

[jaikiran]

Yeah, it's a known issue and I guess we decided to go with it because we didn't have anyone trying to patch it. I had tried once very early during 7.x days but by the time I could get it to a working state, the code got too diverged from the upstream version and then I got busy with other important stuff. Maybe it's time to rethink about this.

[nickarls]

I guess this also touches the issue of explicit deployment order (e.g. two EAR:s which prefer a specific deployment order) which is asked every now and then.

[jaikiran]

I don't think it does. From what I know, the deployment ordering is immaterial if there's a proper dependency being setup (implicitly or explicitly) for example a component using a datasource deployed from another application. This should work currently, I believe.

[jaikiran]

By the way, please raise this in the AS7 dev mailing list. I don't want this feature/requirement to be missed again just because I was lazy enough not to finish that early patch.