You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2006/09/12 17:33:26 UTC

[jira] Created: (GERONIMO-2398) Tx/Connector support should be separated from j2ee-server and client

Tx/Connector support should be separated from j2ee-server and client
--------------------------------------------------------------------

                 Key: GERONIMO-2398
                 URL: http://issues.apache.org/jira/browse/GERONIMO-2398
             Project: Geronimo
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: general
    Affects Versions: 1.2
            Reporter: David Jencks
         Assigned To: David Jencks
             Fix For: 1.2


We should continue separating bits of geronimo into modules by moving the tx/connector support into separate runtime and deployer modules.  At the moment I have new modules (under configs):

transaction (contains the tx manager and connection tracker gbeans)
client-transaction (similar for  the client)
connector-deployer (contains the connector module builder and ref builder gbeans for both the server and client)

Among other things this has revealed that the dependencies are a big mess and the app client module builder isn't always using the right classloader to load client side connectors.

The dependency cleanup is definitely a bug fix... is completing the separation of bits also (e.g. a structure bug in little-g?) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (GERONIMO-2398) Tx/Connector support should be separated from j2ee-server and client

Posted by "Joe Bohn (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-2398?page=comments#action_12435373 ] 
            
Joe Bohn commented on GERONIMO-2398:
------------------------------------

intended to say "branch" rather than "snapshot" in the previous comment.

> Tx/Connector support should be separated from j2ee-server and client
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-2398
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2398
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: general
>    Affects Versions: 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2
>
>         Attachments: GERONIMO-2398-v1-openejb.patch, GERONIMO-2398-v1.patch
>
>
> We should continue separating bits of geronimo into modules by moving the tx/connector support into separate runtime and deployer modules.  At the moment I have new modules (under configs):
> transaction (contains the tx manager and connection tracker gbeans)
> client-transaction (similar for  the client)
> connector-deployer (contains the connector module builder and ref builder gbeans for both the server and client)
> Among other things this has revealed that the dependencies are a big mess and the app client module builder isn't always using the right classloader to load client side connectors.
> The dependency cleanup is definitely a bug fix... is completing the separation of bits also (e.g. a structure bug in little-g?) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (GERONIMO-2398) Tx/Connector support should be separated from j2ee-server and client

Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-2398?page=all ]

David Jencks updated GERONIMO-2398:
-----------------------------------

    Attachment: GERONIMO-2398-v1.patch
                GERONIMO-2398-v1-openejb.patch

About 90% of this is fixing a big bug in the app client builder where we use the wrong classloader when deploying client side rars.  The rest is pretty straightforward splitting up j2ee-server into that + transaction and j2ee-deployer into that + connector-deployer and similar changes on the client.  If I don't get votes pretty quick I'll see about splitting the bug fix out, but it changes mostly the same plans as the split-up under review :-(

> Tx/Connector support should be separated from j2ee-server and client
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-2398
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2398
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: general
>    Affects Versions: 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2
>
>         Attachments: GERONIMO-2398-v1-openejb.patch, GERONIMO-2398-v1.patch
>
>
> We should continue separating bits of geronimo into modules by moving the tx/connector support into separate runtime and deployer modules.  At the moment I have new modules (under configs):
> transaction (contains the tx manager and connection tracker gbeans)
> client-transaction (similar for  the client)
> connector-deployer (contains the connector module builder and ref builder gbeans for both the server and client)
> Among other things this has revealed that the dependencies are a big mess and the app client module builder isn't always using the right classloader to load client side connectors.
> The dependency cleanup is definitely a bug fix... is completing the separation of bits also (e.g. a structure bug in little-g?) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (GERONIMO-2398) Tx/Connector support should be separated from j2ee-server and client

Posted by "Joe Bohn (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-2398?page=comments#action_12435371 ] 
            
Joe Bohn commented on GERONIMO-2398:
------------------------------------

I wasn't able to apply this patch because it appears to have been created against a snapshot rather than trunk.   However, I'm in agreement with this improvement and fix.

> Tx/Connector support should be separated from j2ee-server and client
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-2398
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2398
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: general
>    Affects Versions: 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2
>
>         Attachments: GERONIMO-2398-v1-openejb.patch, GERONIMO-2398-v1.patch
>
>
> We should continue separating bits of geronimo into modules by moving the tx/connector support into separate runtime and deployer modules.  At the moment I have new modules (under configs):
> transaction (contains the tx manager and connection tracker gbeans)
> client-transaction (similar for  the client)
> connector-deployer (contains the connector module builder and ref builder gbeans for both the server and client)
> Among other things this has revealed that the dependencies are a big mess and the app client module builder isn't always using the right classloader to load client side connectors.
> The dependency cleanup is definitely a bug fix... is completing the separation of bits also (e.g. a structure bug in little-g?) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira