[JBoss JIRA] (TEIIDSB-162) Operator does not account for the transaction manager
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-162?page=com.atlassian.jira.plug... ]
Ramesh Reddy updated TEIIDSB-162:
---------------------------------
Summary: Operator does not account for the transaction manager (was: vdb codegen does not account for the transaction manager)
> Operator does not account for the transaction manager
> -----------------------------------------------------
>
> Key: TEIIDSB-162
> URL: https://issues.redhat.com/browse/TEIIDSB-162
> Project: Teiid Spring Boot
> Issue Type: Sub-task
> Components: OpenShift
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.4.0
>
>
> If you define a vdb in a cr, the generated vdb will just use the platformtransactionmanager.
> Since the materialization procedures use transaction blocks, we need a full transaction manager. By default with the platformtransactionmanager it will throw an exception - only spring managed transactions ...
> The workaround would be to add snowdrop to the cr dependencies, but it would be nice to either always use that in the generated, or detect materialization is being used, or address TEIIDSB-109
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-162) vdb codegen does not account for the transaction manager
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-162?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-162:
--------------------------------------
"pom.xml" is generated in the Operator, whereas class files as generated in "vdb-gen", so I will add this requirement into the Operator.
> vdb codegen does not account for the transaction manager
> --------------------------------------------------------
>
> Key: TEIIDSB-162
> URL: https://issues.redhat.com/browse/TEIIDSB-162
> Project: Teiid Spring Boot
> Issue Type: Sub-task
> Components: OpenShift
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.4.0
>
>
> If you define a vdb in a cr, the generated vdb will just use the platformtransactionmanager.
> Since the materialization procedures use transaction blocks, we need a full transaction manager. By default with the platformtransactionmanager it will throw an exception - only spring managed transactions ...
> The workaround would be to add snowdrop to the cr dependencies, but it would be nice to either always use that in the generated, or detect materialization is being used, or address TEIIDSB-109
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIID-5883) Move older infinispan dependency to wildfly
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5883?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5883:
----------------------------------
Description: The wildfly version of ispn is marked as having a cve. That dependency version should be isolated to wildfly. (was: When changing the infinispan dependencies to reference the property, which is v10, it fails with the following error:
{code}
[ERROR] /home/vhalbert/RedHat/github/repos_codeeng/teiid/cache-infinispan/src/main/java/org/teiid/cache/infinispan/EmbeddedInfinispanCacheFactoryBuilder.java:[43,80] method transactionManagerLookup in class org.infinispan.configuration.cache.TransactionConfiguration cannot be applied to given types;
[ERROR] required: no arguments
[ERROR] found: <anonymous org.infinispan.commons.tx.lookup.TransactionManagerLookup>
[ERROR] reason: actual and formal argument lists differ in length
{code})
> Move older infinispan dependency to wildfly
> -------------------------------------------
>
> Key: TEIID-5883
> URL: https://issues.redhat.com/browse/TEIID-5883
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
>
> The wildfly version of ispn is marked as having a cve. That dependency version should be isolated to wildfly.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIID-5883) Move older infinispan dependency to wildfly
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5883?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5883:
----------------------------------
Summary: Move older infinispan dependency to wildfly (was: Changing infinispan dependency to use V10 errors)
> Move older infinispan dependency to wildfly
> -------------------------------------------
>
> Key: TEIID-5883
> URL: https://issues.redhat.com/browse/TEIID-5883
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
>
> When changing the infinispan dependencies to reference the property, which is v10, it fails with the following error:
> {code}
> [ERROR] /home/vhalbert/RedHat/github/repos_codeeng/teiid/cache-infinispan/src/main/java/org/teiid/cache/infinispan/EmbeddedInfinispanCacheFactoryBuilder.java:[43,80] method transactionManagerLookup in class org.infinispan.configuration.cache.TransactionConfiguration cannot be applied to given types;
> [ERROR] required: no arguments
> [ERROR] found: <anonymous org.infinispan.commons.tx.lookup.TransactionManagerLookup>
> [ERROR] reason: actual and formal argument lists differ in length
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIID-5883) Changing infinispan dependency to use V10 errors
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5883?page=com.atlassian.jira.plugi... ]
Steven Hawkins reopened TEIID-5883:
-----------------------------------
> Changing infinispan dependency to use V10 errors
> ------------------------------------------------
>
> Key: TEIID-5883
> URL: https://issues.redhat.com/browse/TEIID-5883
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
>
> When changing the infinispan dependencies to reference the property, which is v10, it fails with the following error:
> {code}
> [ERROR] /home/vhalbert/RedHat/github/repos_codeeng/teiid/cache-infinispan/src/main/java/org/teiid/cache/infinispan/EmbeddedInfinispanCacheFactoryBuilder.java:[43,80] method transactionManagerLookup in class org.infinispan.configuration.cache.TransactionConfiguration cannot be applied to given types;
> [ERROR] required: no arguments
> [ERROR] found: <anonymous org.infinispan.commons.tx.lookup.TransactionManagerLookup>
> [ERROR] reason: actual and formal argument lists differ in length
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIID-5883) Changing infinispan dependency to use V10 errors
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5883?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5883.
-----------------------------------
Resolution: Rejected
There are two infinispan dependescies teiid tracks. The 9.x set matches what is in wildfly. The 10.x set are used by the resource adapter/translator. Teiid doesn't directly package the 9.x set.
> Changing infinispan dependency to use V10 errors
> ------------------------------------------------
>
> Key: TEIID-5883
> URL: https://issues.redhat.com/browse/TEIID-5883
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
>
> When changing the infinispan dependencies to reference the property, which is v10, it fails with the following error:
> {code}
> [ERROR] /home/vhalbert/RedHat/github/repos_codeeng/teiid/cache-infinispan/src/main/java/org/teiid/cache/infinispan/EmbeddedInfinispanCacheFactoryBuilder.java:[43,80] method transactionManagerLookup in class org.infinispan.configuration.cache.TransactionConfiguration cannot be applied to given types;
> [ERROR] required: no arguments
> [ERROR] found: <anonymous org.infinispan.commons.tx.lookup.TransactionManagerLookup>
> [ERROR] reason: actual and formal argument lists differ in length
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIID-5883) Changing infinispan dependency to use V10 errors
by Van Halbert (Jira)
Van Halbert created TEIID-5883:
----------------------------------
Summary: Changing infinispan dependency to use V10 errors
Key: TEIID-5883
URL: https://issues.redhat.com/browse/TEIID-5883
Project: Teiid
Issue Type: Bug
Affects Versions: 13.x
Reporter: Van Halbert
Assignee: Steven Hawkins
When changing the infinispan dependencies to reference the property, which is v10, it fails with the following error:
{code}
[ERROR] /home/vhalbert/RedHat/github/repos_codeeng/teiid/cache-infinispan/src/main/java/org/teiid/cache/infinispan/EmbeddedInfinispanCacheFactoryBuilder.java:[43,80] method transactionManagerLookup in class org.infinispan.configuration.cache.TransactionConfiguration cannot be applied to given types;
[ERROR] required: no arguments
[ERROR] found: <anonymous org.infinispan.commons.tx.lookup.TransactionManagerLookup>
[ERROR] reason: actual and formal argument lists differ in length
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIID-5882) Default cache name is no longer default
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5882:
-------------------------------------
Summary: Default cache name is no longer default
Key: TEIID-5882
URL: https://issues.redhat.com/browse/TEIID-5882
Project: Teiid
Issue Type: Quality Risk
Components: Infinispan
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 14.0
The infinispan default cache name is no longer default. It can instead be specified in the cache container and obtained by the getCache method that does not take a name. Our resource adapter defaults the value to "default", so that could be removed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months