[cjohn001]

Hello Steven,

understood So it looks like if will become no easy to fix. In the meantime I have added a issue for the topic

[TEIID-5763] GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files - JBoss Issue Tracker

Do you think you will get this working, even so it does not look easy?

Regarding the source build, thanks for the links!

[shawkins]

Just this aspect will be easy to fix.  The most difficult situation to address is allowing subsequent user statements to access previously generated keys, but that shouldn't be too bad.

[cjohn001]

Hello Steven,

ok great, there remains hope In the meantime I managed to build Teiid from git sources according your description. So let me know as soon as I can support with testing. I will close the issue here than, as I assume it will be better to  follow up the discussion in the related Jira issue.

[cjohn001]

Hello Steven,

I have just tried to build the current teiid version from git and use the overlay to build my docker image. When building the docker image I get the following error. Seems to be somethin wrong with the supplied standalone-teiid. Can I use the current snapshot with Wildfly 15.0.1? I ask this because in the build folder there is also a subfolder named wildfly-17.0.0.Beta1. In case the build generates an overlay for wildfly-17 only is there a way to configure a Wildfly 15 or 16 build as well? This is because I need a keycloak overlay as well, which is currently only available for wildfly 16.

Any ideas what is going wrong?

I used the file under teiid/wildfly/wildfly-build/target/teiid-wildfly-12.3.0-SNAPSHOT-dist.zip

As I assumed this to be the overlay that I usually download from teiid.io

17:01:31,846 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 15.0.1.Final (WildFly Core 7.0.0.Final) starting

17:01:33,623 ERROR [org.jboss.as.controller] (Controller Boot Thread)

OPVDX001: Validation error in standalone-teiid.xml -----------------------------

|

|  1: <?xml version='1.0' encoding='UTF-8'?>

|  2:

|  3: <server xmlns="urn:jboss:domain:10.0">

|     ^^^^ Unexpected element '{urn:jboss:domain:10.0}server'

|

|  4:     <extensions>

|  5:         <extension module="org.jboss.as.clustering.infinispan"/>

|  6:         <extension module="org.jboss.as.connector"/>

|

| The primary underlying error message was:

| > ParseError at [row,col]:[3,1]

| > Message: Unexpected element '{urn:jboss:domain:10.0}server'

|

|-------------------------------------------------------------------------------

17:01:33,628 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration

  at [e-mail]//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)

  at [e-mail]//org.jboss.as.server.ServerService.boot(ServerService.java:385)

  at [e-mail]//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:374)

  at java.base/java.lang.Thread.run(Thread.java:834)

17:01:33,632 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

[shawkins]

Master / 12.3 is tracking WildFly 17 - [TEIID-5738] Upgrade to WildFly 16 - JBoss Issue Tracker