[
https://issues.jboss.org/browse/TEIID-3948?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3948:
---------------------------------------
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.
There are two concerns:
- whatever we do should still work "out of the box"
- modifications to the app, especially context params, should be simplistic
After looking into things more, it does look like
https://docs.jboss.org/author/display/AS72/Deployment+Overlays would allow you to override
even all of the needed pieces for oauth/saml in a single cli command.
Provide a different mechanism to update odata wars
--------------------------------------------------
Key: TEIID-3948
URL:
https://issues.jboss.org/browse/TEIID-3948
Project: Teiid
Issue Type: Quality Risk
Components: Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.0, 8.12.5
Directly modifying the wars under the base modules is a bad practice. We need to have
users modify non-kit artifact files in a different location.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)