Oliver Zeigermann (JIRA) wrote:
[
https://issues.apache.org/jira/browse/TRANSACTION-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512556
]
Oliver Zeigermann commented on TRANSACTION-16:
--
I have now tried to set
Dennis Lundberg wrote:
Hi
Diagnostics, that was introduced in Commons Logging 1.1, is a great way
to troubleshoot classloading issues:
http://jakarta.apache.org/commons/logging/troubleshooting.html#Using_JCL_Diagnostics
I'm not really in doubt what's going on, so I don't think
Joerg Heinicke wrote:
Just answering that one at the moment:
http://jroller.com/page/pyrasun?entry=xa_exposed
That's a great article! I look forward to read part II and III.
I don't see anything about how the TransactionManager gets knowledge of
participating XAResource instances though.
Hello,
I'm having trouble with commons-logging in a scenario where I am
embedding tomcat's jasper in another servlet container.
I keep getting the exception about commons-logging being available from
multiple classloaders.
This seeems to be caused by LogFactory using the ContextClassLoader
Hi,
A bit more details below. I haven't had time to look in detail at the
existing implementation.
Some points on the inner workings:
*** Collections ***
- Typically working with a shared resource is done by creating a map
with the resource values, and then instantiating an XAMap, passing
Hello,
Oliver suggested that I post this mail here:
I would like to donate an implementation of some transaction enabled
collections and resources.
The implementation is (more or less) JTA compliant, and mostly finished.
It is not well-tested, robust or mature.
The code includes:
1) TX
