Optionally shutdown Q2 on configuration error about jpos HOT 3 CLOSED

What if, while we work on a more sophisticated solution, we just add a strategy for handling the different exceptions/errors?

One could plug a strategy and the default one would do what it currently does. So we give total freedom to developers.

We can later implement other behaviors, or even as a strategy, a fail-on-errors (or the like) flag could activate a specific strategy, if we want to implement it. But then someone could choose to implement a strategy that only quits on errors, or only on dups, or even on a condition of the filename.

This comment was fired by a discussion on slack, link valid for 90 days.

from jpos.

Also, this issue is quite related to #553

from jpos.

What if, while we work on a more sophisticated solution, we just add a strategy for handling the different exceptions/errors?

I don't think we want to have a thousand ways to achieve a simple thing such as aborting on failing QBeans. The --exit-on-failed-deploy=startup|always is all we need. I'll close this issue and we can continue in #553.

from jpos.