You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2010/06/11 00:23:15 UTC

[jira] Created: (CAY-1446) Remove DataContextFactory

Remove DataContextFactory
-------------------------

                 Key: CAY-1446
                 URL: https://issues.apache.org/jira/browse/CAY-1446
             Project: Cayenne
          Issue Type: Task
          Components: Core Library
    Affects Versions: 3.1M1
            Reporter: Andrus Adamchik
            Assignee: Andrus Adamchik
             Fix For: 3.1M1


DataContextFactory is no longer needed since we have injection, and the context is created via a factory (DI Provider) already. It should be easy for the users of custom factories to implement their own org.apache.cayenne.configuration.server.DataContextProvider. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (CAY-1446) Remove DataContextFactory, replace it with DI-enabled ObjectContextFactory

Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAY-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrus Adamchik closed CAY-1446.
--------------------------------

    Resolution: Fixed

> Remove DataContextFactory, replace it with DI-enabled ObjectContextFactory
> --------------------------------------------------------------------------
>
>                 Key: CAY-1446
>                 URL: https://issues.apache.org/jira/browse/CAY-1446
>             Project: Cayenne
>          Issue Type: Task
>          Components: Core Library
>    Affects Versions: 3.1M1
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.1M1
>
>
> DataContextFactory will be replaced by an ObjectContextFactory that can created regular and nested contexts and can be used on the server and client side. An ability to configure that via the Modeler will be removed, as DI will be the main place to configure it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAY-1446) Remove DataContextFactory, replace it with DI-enabled ObjectContextFactory

Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAY-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrus Adamchik updated CAY-1446:
---------------------------------

        Summary: Remove DataContextFactory, replace it with DI-enabled ObjectContextFactory  (was: Remove DataContextFactory)
    Description: DataContextFactory will be replaced by an ObjectContextFactory that can created regular and nested contexts and can be used on the server and client side. An ability to configure that via the Modeler will be removed, as DI will be the main place to configure it.  (was: DataContextFactory is no longer needed since we have injection, and the context is created via a factory (DI Provider) already. It should be easy for the users of custom factories to implement their own org.apache.cayenne.configuration.server.DataContextProvider. )

(changing the issue definition. we need DI-enabled ObjectContextFactory to created nested contexts)

> Remove DataContextFactory, replace it with DI-enabled ObjectContextFactory
> --------------------------------------------------------------------------
>
>                 Key: CAY-1446
>                 URL: https://issues.apache.org/jira/browse/CAY-1446
>             Project: Cayenne
>          Issue Type: Task
>          Components: Core Library
>    Affects Versions: 3.1M1
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.1M1
>
>
> DataContextFactory will be replaced by an ObjectContextFactory that can created regular and nested contexts and can be used on the server and client side. An ability to configure that via the Modeler will be removed, as DI will be the main place to configure it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.