geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-2143) ENCConfigBuilder blocks outside callers
Date Wed, 26 Jul 2006 20:02:14 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2143?page=all ]

Aaron Mulder updated GERONIMO-2143:
-----------------------------------

    Description: 
ENCConfigBuilder makes strategic methods private and some methods require an EAR context,
module ID, JNDI builder, etc. that are only relevant for EAR callers.  For plugins, etc. that
want to create EJB/Resource/Service references, they need a lot of copy and paste and refactoring
of code that should be reusable.  The ENCConfigBuilder should be fixed to be equally useful
to internal (J2EE) and external (non-J2EE) callers.

Ideally, it would also take ConfigurationData instead of Configuration as arguments, which
would make it easier to reuse outside the normal deployment process.

  was:ENCConfigBuilder makes strategic methods private and some methods require an EAR context,
module ID, JNDI builder, etc. that are only relevant for EAR callers.  For plugins, etc. that
want to create EJB/Resource/Service references, they need a lot of copy and paste and refactoring
of code that should be reusable.  The ENCConfigBuilder should be fixed to be equally useful
to internal (J2EE) and external (non-J2EE) callers.


> ENCConfigBuilder blocks outside callers
> ---------------------------------------
>
>                 Key: GERONIMO-2143
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2143
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment, naming
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>             Fix For: 1.1.x
>
>
> ENCConfigBuilder makes strategic methods private and some methods require an EAR context,
module ID, JNDI builder, etc. that are only relevant for EAR callers.  For plugins, etc. that
want to create EJB/Resource/Service references, they need a lot of copy and paste and refactoring
of code that should be reusable.  The ENCConfigBuilder should be fixed to be equally useful
to internal (J2EE) and external (non-J2EE) callers.
> Ideally, it would also take ConfigurationData instead of Configuration as arguments,
which would make it easier to reuse outside the normal deployment process.

-- 
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

        

Mime
View raw message