[
https://issues.jboss.org/browse/TEIID-4895?page=com.atlassian.jira.plugin...
]
Tom Arnold commented on TEIID-4895:
-----------------------------------
For us the Teiid/Wildfly combination is useful because our main application runs in
Wildfly, so it's just more of the same thing WRT development and deployment. I
don't see this changing anytime soon.
Our usage is basically this:
We have a web app deployed in Teiid/Wildfly that configures data sources (using Teiid
Admin and DMR) and generates a VDB. We have several translator JARs as hot-deployments in
Teiid/Wildfly, and scripts to redeploy translator + VDB on change. We talk to Teiid over
JDBC from other JBoss/Wildfly servers.
We don't currently use the clustering/HA features that are out there but we may be
looking into this soon.
Determine community requirements for WildFly usage
--------------------------------------------------
Key: TEIID-4895
URL:
https://issues.jboss.org/browse/TEIID-4895
Project: Teiid
Issue Type: Task
Reporter: Steven Hawkins
Assignee: Steven Hawkins
WildFly is typically the runtime for Teiid. However we want feedback from the community
on what style of WildFly integration is important:
- The ability to deploy Teiid into a managed WildFly instance/cluster
- The combination Teiid/WildFly artifact
- A layered docker image
- Not full WildFly, just Swarm
- Not needed, just Embedded
Based upon this we can better tune our documentation, downloads, and examples.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)