geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Commented: (GERONIMO-817) deploy-jsr88 module has dependency on openejb
Date Tue, 26 Jul 2005 15:36:21 GMT
    [ ] 

Aaron Mulder commented on GERONIMO-817:

The patch (to disable DConfigBean support) is not acceptable.

Reflection is fine for now.

Simple registration is not workable becuase a client/tool uses this API when the server is
not available (the DisconnectedDeploymentManager).  That would argue for a configuration-based
format where the config file lists the implementations to use.  It's possible that we could
have a GBean or Servlet that generates the necessary client JAR, including identifying DConfigBean
sources according to what's available in the server at the moment based on a registration
scheme, but that seems like it's going kind of a long way, considering we only support OpenEJB

A more straightforward solution might be pull the EJB configuration format into Geronimo like
we did for web, so this only depends on Geronimo code in any case.

> deploy-jsr88 module has dependency on openejb
> ---------------------------------------------
>          Key: GERONIMO-817
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M4, 1.0-M5
>     Reporter: David Jencks
>     Assignee: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.0-M4, 1.0-M5
>  Attachments: nobuilderdependencies
> Apparently in an attempt to support dconfig beans, the deploy-jsr88 module grew dependencies
on several builder modules including openejb builder.  This is a totally non-extensible archtecture
and prevents building geronimo and openejb in any semblance of a reasonable order.  I think
that some kind of registration scheme might be plausible but the current hard-coded dependencies
to specific builder implementations are not acceptable.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message