[
https://issues.apache.org/jira/browse/DELTASPIKE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko reassigned DELTASPIKE-939:
Assignee: Thomas Andraschko
dswid=tempWindowId for every duplicated
Christian Kaltepoth created DELTASPIKE-950:
--
Summary: RequestResponseHolderListener fails if
requestInitialized() is called more than once
Key: DELTASPIKE-950
URL:
[
https://issues.apache.org/jira/browse/DELTASPIKE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Kaltepoth resolved DELTASPIKE-950.
Resolution: Fixed
Fix Version/s: 1.4.2
Gerhard,
Can I safely presume an elaboration of your message would be Worker Thread
Local? [As opposed to Main ThreadLocal]
_Marvin
hi marvin,
when it comes to concurrency both are similar.
the request- as well as the transaction-context store instances in a
ThreadLocal variable/storage.
Gerhard Petracek created DELTASPIKE-951:
---
Summary: validate the content of TestControl#startScopes
Key: DELTASPIKE-951
URL: https://issues.apache.org/jira/browse/DELTASPIKE-951
Project:
hi marvin,
@transaction-context:
yes (the TransactionalInterceptor starts/stops the context automatically)
@request-context:
yes - if it is a managed thread.
in case of an unmanaged thread you have to start/stop the context correctly
via ContextControl (per worker-thread).
regards,
gerhard
Using a TransactionScoped EntityManager producer does not allow a read method
to have a read only hint.
I would like all the read operations to be use a readonly connection.
But when I try it I get an error that there is no active scope.
Is it not possible to use readonly with a transaction
[
https://issues.apache.org/jira/browse/DELTASPIKE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Kaltepoth resolved DELTASPIKE-949.
Resolution: Fixed
Fix Version/s: 1.4.2
