fjtirado commented on issue #1685:
URL: 
https://github.com/apache/incubator-kie-issues/issues/1685#issuecomment-2561034028

   @tkobayas @pjfanning 
   
   Kogito runtimes do not use JPA but Kogito Apps heavily use it, both for 
data_index and audit components. Therefore removing JPA is not a viable option 
without basically redeveloping both components. 
   
   On top of that, we recently start using Hibernate classes directly to allow 
querying ProcessInstance.variables property (which is json column in postgress) 
in postgresql. See 
[here](https://github.com/apache/incubator-kie-kogito-apps/blob/main/data-index/data-index-storage/data-index-storage-postgresql/src/main/java/org/kie/kogito/index/postgresql/ContainsSQLFunction.java#L24-L28)
   
   Therefore we have two options. 
   1) Replace Hibernate by OpenJPA, as was made in Drools (where this is not a 
problem because there is a JPA transaction manager, but not JPA entities) , and 
study how to achieve the custom function functionality. After a quick study of 
the OpenJPA documentation, it seems there might be a 
[way](https://openjpa.apache.org/builds/2.1.1/apache-openjpa/docs/ch13s03.html),
 but as you see the doc is sparse.
   2) Do as as @pjfanning (mainly because Hibernate License will be eventually 
updated and this will be a temporary fix) proposed. Do not distribute the 
binary (move the dependency as provided in the pom) and include instructions to 
add it. 
   
   I guess we can try OpenJPA as POC and if it works, go ahead, but @krisv, do 
we really want to get rid of Hibernate strategically?  
   
   In any case, before moving forward, we should wait to discuss the 
alternatives further. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to