[jira] Updated: (NANO-42) allow using custom ContainerBuilder with NanoContainer

The following issue has been updated:

    Updater: Rafal Krzewski (mailto:[email protected])
       Date: Thu, 19 Feb 2004 9:53 AM
    Comment:
a patch that introduces the described change (i.e. extension -> builderClass in constructor parameters)
    Changes:
             Attachment changed to nanoContainerBuilder.diff
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=NANO-42&page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=NANO-42

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: NANO-42
    Summary: allow using custom ContainerBuilder with NanoContainer
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: NanoContainer

   Assignee: 
   Reporter: Rafal Krzewski

    Created: Thu, 19 Feb 2004 9:52 AM
    Updated: Thu, 19 Feb 2004 9:53 AM

Description:
it's no longer possible (since extensionsToComposers became private, which actually happens to be good design) to use a custom ContainerBuilder with NanoContainer. 

I think that it would be better if only the constructos that take File arguments used the filename extensions to resolve ScriptedContainerBuilder class. All constructors that currently take an extension argument, should take the builder's class name.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira