[ https://issues.jboss.org/browse/TEIID-3649?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3649: --------------------------------------- I don't think we're looking at this the same way. Underlying where you are coming from is something like "if I make assumptions x,y,z and include a new configuration framework, then for a class of embedded deployments people will have less work". While I'm saying that I don't want the project to assume responsibility for another configuration framework if possible, don't want to make assumptions about what dependencies are needed (especially if we just end up providing major portions of the AS anyway such as the JCA/pooling/transaction manager - as that would imply we should just embed the AS), and we can't really say that the class of embedded deployments that we'll end up addressing even represents a majority of what developers are trying to do. So I'm saying we should proceed with caution down this path. The more code that is being dedicated toward this on our end, the more likely it is that we are doing something wrong. -- This message was sent by Atlassian JIRA (v6.3.15#6346)