commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CHAIN-85) Move CatalogFactory to API module
Date Mon, 08 Jul 2013 19:57:49 GMT

    [ https://issues.apache.org/jira/browse/CHAIN-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702346#comment-13702346
] 

Benedikt Ritter commented on CHAIN-85:
--------------------------------------

bq. it is not a factory, but rather a collection/registry/whatever, but definitively not a
factory; 

aggreed.

bq. its strong typing is IMHO wrong:

not sure how this will impact the API. I guess I'll have to see this in the code

bq. its definition/interface fits to APIs, not its default implementation, that belongs to
the base package; base implementation is the current "in memory" one, users can have potentially
limitless solutions (based on RDMS, on NoSQL, ...)

agreed. This is what I had in mind. I just structured it wrong in JIRA. First make it an interface
(CHAIN-86) then move the interface to API package.
                
> Move CatalogFactory to API module
> ---------------------------------
>
>                 Key: CHAIN-85
>                 URL: https://issues.apache.org/jira/browse/CHAIN-85
>             Project: Commons Chain
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 2.0
>            Reporter: Benedikt Ritter
>             Fix For: 2.0
>
>
> As discussed the CatalogFactory really belongs to the API module

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message