The last wildfly update was to 15.0.1 - [TEIID-5629] Upgrade to WildFly 15.0.1 - JBoss Issue Tracker
Teiid 12.3 is where we would look to update the WildFly support again. Can you log Teiid JIRA issue for that?
Thanks for the responce.
I have created a JIRA issue https://issues.jboss.org/browse/TEIID-5738
I See the latest versions
we have currently Wildifly 15.0 building with Teiid 12.1.0
our Requirement is, Need to upgrade WildiFly to 6.0
So Can we upgrade wildFly separately? or Teiid version which supports WildFly 6.0 is only the option. What is the best possible solution. Please let us know
> So Can we upgrade wildFly separately?
Generally no. Teiid makes use of a lot of WildFly internals, such as the deployer, where there may be WildFly api changes that need to be accounted for from one version to the next.
That said, WildFly now releases with an aggressive cadence with fewer breaking changes between versions. You can certainly try the Teiid overlay on a WildFly 16 instance - but there's no guarantee that will work.
Is it possible to install Wildfly 16.0 in a completely separate directory structure from Teiid 12.1.1 ?
Or does it need to be in the same folder structure. We've mostly leveraged the one that has Wildfly with Teiid together.
I did read the documentation for running the install cli, and migration - it's possible I missed something. I also attempted to run them in separate folders but got this when trying to use relative path.
WFLYCTL0083: Failed to load module
More concisely, is there a way to keep the two separate in case we need to upgrade one or the other independently? I'm having trouble understanding how the overlay is managed for updates/upgrades
> More concisely, is there a way to keep the two separate in case we need to upgrade one or the other independently?
Given the close coupling the most likely upgrade is Teiid into the same version of WildFly. The overlay was simply designed as just that - an overlay. You could investigate keeping things separate, it would likely involve at least symlinks from WildFly to Teiid modules/system/layers/dv and modules/system/layers.conf. If you use the teiid standalone xml it would need to be linked as well. The other parts of the overlay, such as scripts and docs, are not required to be under the same directory structure as WildFly.
> I'm having trouble understanding how the overlay is managed for updates/upgrades
To upgrade Teiid you backup your Teiid configuration, then delete modules/system/layers/dv, then apply the new overlay, then restore your configuration.