[jira] Commented: (GERONIMO-3344) Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc.
[ https://issues.apache.org/jira/browse/GERONIMO-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516111 ] David Jencks commented on GERONIMO-3344: Openejb modified to use new jars in rev 560408. Ported to g. 2.0 branch in rev. 560411 Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc. - Key: GERONIMO-3344 URL: https://issues.apache.org/jira/browse/GERONIMO-3344 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector, transaction manager Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks Fix For: 2.0 Attachments: openejb-deps.patch.txt People have been asking for this for years wny not now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3344) Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc.
[ https://issues.apache.org/jira/browse/GERONIMO-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515929 ] David Blevins commented on GERONIMO-3344: - Heh. Love the description on the issue :) I gave the new jars a try with components built from r560047 (about 06:09 PM, PDT). Getting this compile issue: /Users/dblevins/work/openejb3/container/openejb-core/src/main/java/org/apache/openejb/resource/GeronimoConnectionManagerFactory.java:[158,53] cannot find symbol symbol : constructor GenericConnectionManager(org.apache.geronimo.connector.outbound.connectionmanagerconfig.TransactionSupport,org.apache.geronimo.connector.outbo und.connectionmanagerconfig.PoolingSupport,boolean,org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTrackingCoordinator,org.apache.geronimo.trans action.manager.RecoverableTransactionManager,java.lang.String,java.lang.ClassLoader) location: class org.apache.geronimo.connector.outbound.GenericConnectionManager Strange how we can get this now as I was certain we were running from trunk. Will attach a pom.xml diff for openejb for convenience. Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc. - Key: GERONIMO-3344 URL: https://issues.apache.org/jira/browse/GERONIMO-3344 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector, transaction manager Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks Attachments: openejb-deps.patch.txt People have been asking for this for years wny not now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3344) Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc.
[ https://issues.apache.org/jira/browse/GERONIMO-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515936 ] David Jencks commented on GERONIMO-3344: I'm not sure how to fix this in openejb myself because I don't know what you mean by containerManagedSecurity. I changed the API slightly so instead of specifying containerManagedSecurity as a boolean and if true extracting the next subject from geronimo's proprietary ContextManager class as we were doing before now you supply a SubjectSource that will actually supply the subjects if you want container managed security. If you don't, you supply null instead. Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc. - Key: GERONIMO-3344 URL: https://issues.apache.org/jira/browse/GERONIMO-3344 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector, transaction manager Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks Attachments: openejb-deps.patch.txt People have been asking for this for years wny not now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3344) Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc.
[ https://issues.apache.org/jira/browse/GERONIMO-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515220 ] David Jencks commented on GERONIMO-3344: New location for functional code is components/txmanager/trunk. Changes to server/trunk in rev 559333. This commit has versions for the new jars in the wrong place, I will fix this shortly. Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc. - Key: GERONIMO-3344 URL: https://issues.apache.org/jira/browse/GERONIMO-3344 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector, transaction manager Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks People have been asking for this for years wny not now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3344) Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc.
[ https://issues.apache.org/jira/browse/GERONIMO-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515228 ] David Jencks commented on GERONIMO-3344: Moved the versions into root pom dependency management. We need to decide if this goes into g. 2.0 as well. Split out non-kernel-dependent transaction and connector classes for use by openejb, jencks, etc etc. - Key: GERONIMO-3344 URL: https://issues.apache.org/jira/browse/GERONIMO-3344 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector, transaction manager Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks People have been asking for this for years wny not now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
