|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (CARGO-714) Tomcat transaction resource is defined globally, which doesn't work in tomcat 5.5 or 6Tomcat transaction resource is defined globally, which doesn't work in tomcat 5.5 or 6
-------------------------------------------------------------------------------------- Key: CARGO-714 URL: http://jira.codehaus.org/browse/CARGO-714 Project: Cargo Issue Type: Bug Components: Tomcat Affects Versions: 1.0 Reporter: James Roper In cargo 1.0, tomcats resources are all defined globally (in conf/context.xml). This doesn't work for transaction resources in tomcat 5.5 (or it seems 6). See this thread for some details: http://www.nabble.com/UserTransaction,-JOTM-and-Tomcat-5.5.x-td2793244.html Additionally, defining resources globally means that two deployments that require different datasources with the same name won't work. The resources should be defined locally. There's a comment in the source code saying "In Tomcat 5.5+, we use context.xml to avoid configuration problems.", but no explanation as to what these configuration problems are. If there really are configuration problems, then maybe the contexts should be defined in conf/Catalina/localhost/path.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-714) Tomcat transaction resource is defined globally, which doesn't work in tomcat 5.5 or 6[ http://jira.codehaus.org/browse/CARGO-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183744#action_183744 ] James Roper commented on CARGO-714: ----------------------------------- It's actually the <Transaction> tag that isn't supported globally, changing it to use <Resource> for transactions works. > Tomcat transaction resource is defined globally, which doesn't work in tomcat 5.5 or 6 > -------------------------------------------------------------------------------------- > > Key: CARGO-714 > URL: http://jira.codehaus.org/browse/CARGO-714 > Project: Cargo > Issue Type: Bug > Components: Tomcat > Affects Versions: 1.0 > Reporter: James Roper > > In cargo 1.0, tomcats resources are all defined globally (in conf/context.xml). This doesn't work for transaction resources in tomcat 5.5 (or it seems 6). See this thread for some details: > http://www.nabble.com/UserTransaction,-JOTM-and-Tomcat-5.5.x-td2793244.html > Additionally, defining resources globally means that two deployments that require different datasources with the same name won't work. The resources should be defined locally. There's a comment in the source code saying "In Tomcat 5.5+, we use context.xml to avoid configuration problems.", but no explanation as to what these configuration problems are. If there really are configuration problems, then maybe the contexts should be defined in conf/Catalina/localhost/path.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Updated: (CARGO-714) Tomcat transaction resource is defined globally, which doesn't work in tomcat 5.5 or 6[ http://jira.codehaus.org/browse/CARGO-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Roper updated CARGO-714: ------------------------------ Attachment: transaction.patch Attached a patch that fixes the problem. This doesn't solve the fact that everything is global when it shouldn't be, but it does make transactions work. > Tomcat transaction resource is defined globally, which doesn't work in tomcat 5.5 or 6 > -------------------------------------------------------------------------------------- > > Key: CARGO-714 > URL: http://jira.codehaus.org/browse/CARGO-714 > Project: Cargo > Issue Type: Bug > Components: Tomcat > Affects Versions: 1.0 > Reporter: James Roper > Attachments: transaction.patch > > > In cargo 1.0, tomcats resources are all defined globally (in conf/context.xml). This doesn't work for transaction resources in tomcat 5.5 (or it seems 6). See this thread for some details: > http://www.nabble.com/UserTransaction,-JOTM-and-Tomcat-5.5.x-td2793244.html > Additionally, defining resources globally means that two deployments that require different datasources with the same name won't work. The resources should be defined locally. There's a comment in the source code saying "In Tomcat 5.5+, we use context.xml to avoid configuration problems.", but no explanation as to what these configuration problems are. If there really are configuration problems, then maybe the contexts should be defined in conf/Catalina/localhost/path.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |