[teiid-issues] [JBoss JIRA] (TEIID-3948) Provide a different mechanism to update odata wars

[ https://issues.jboss.org/browse/TEIID-3948?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3948: ------------------------------------- yes, this is happening by install scripts, but what we are talking about is by the user. My worry is web.xml is not the only thing that might require change. In the case of the oauth/saml there were certificates to be added, jboss-web.xml and additional keycloak configuration files etc. I do not like to set a different way to handle this simple case and then do the other way for rest of the usecases. These changes will not be part of the WAR file, but they will exist in the "deployments" folder some how. Now when one migrates to a different server or newer version then the burden is on us to move these appropriately. What I am saying let the user own the changes, in self contained WAR file, then it is matter of just moving their artifact to a newer server. This embedded option as you say is for different purpose than this, that is for us to promote ourselves as drop-in OData provider (in any JEE container) for any datasource. Here, I am just laying out a usecase as to why we would need to move OData project to a separate repo, not for this individual issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)