lolgab commented on issue #2200: URL: https://github.com/apache/jena/issues/2200#issuecomment-1903502954
Thank you for your answer! You are right in saying that the usage pattern goes deep inside the code. I tried to write a custom `TDBStorageBuilder` receiving a `TransactionalSystem` and it's not enough since I had a failure in [`TransactionalComponentLifecycle`](https://github.com/apache/jena/blob/cf7ea1c33af31cb117d463f601b7042954322eaf/jena-db/jena-dboe-transaction/src/main/java/org/apache/jena/dboe/transaction/txn/TransactionalComponentLifecycle.java#L48) which is deep inside of the implementation of TDB2. It would be nice if Jena stopped relying on `ThreadLocal`s but used parameter passing to access the current `Transaction`, but I understand this is a big change and I'm not sure it's worth it. For my use case I can work around the problem by using Thread Pool where I assign a `Thread` to the whole transaction. Which works correctly. -- 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]
