Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <15646348.1159753880059.JavaMail.root@brutus>
Date: Sun, 1 Oct 2006 18:51:20 -0700 (PDT)
From: "David Jencks (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Assigned: (GERONIMO-2143) ENCConfigBuilder blocks outside
 callers
In-Reply-To: <4506855.1150992869884.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-2143?page=all ]

David Jencks reassigned GERONIMO-2143:
--------------------------------------

    Assignee: Aaron Mulder

Aaron can you take a look at the current NamingBuilder stuff in trunk and see if it meets your needs?  If so... close this otherwise indicate something more about what you'd like.

> 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
>         Assigned To: 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