Sebastian Koske wrote:
Hi Jason,
I understand the need for a clear configuration layout and a centralized configuration file is clearly an advantage, but I'm quite shocked about the rigidness of the implementation. Why not give developers the alternative to choose what fits best for them? Erasing any alternatives or options has a significant impact on the whole deployment process.
I think the important thing to note here is that we didn't actually "erase" anything. The capability to support deployable data sources/JMS queues/etc. is something we would have to commit extra resources to implement - resources we do not presently have available. This would be a great thing for some enthusiastic community members to take up however; that would change the picture dramatically.