[teiid-issues] [JBoss JIRA] (TEIIDSB-162) vdb codegen does not account for the transaction manager

Ramesh Reddy (Jira) issues at jboss.org
Wed Jan 22 11:51:44 EST 2020


    [ https://issues.redhat.com/browse/TEIIDSB-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954716#comment-13954716 ] 

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)


More information about the teiid-issues mailing list