You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/02/02 20:08:20 UTC

[jira] Created: (JAMES-966) Refactor LoaderService to not create instances of class on its own

Refactor LoaderService to not create instances of class on its own
------------------------------------------------------------------

                 Key: JAMES-966
                 URL: https://issues.apache.org/jira/browse/JAMES-966
             Project: JAMES Server
          Issue Type: Improvement
            Reporter: Norman Maurer
             Fix For: 3.0-M1


The current LoaderService implementation create instances by using newInstance() which is a bad practice (IMHO). Instances should only get created by the container (spring). Using a BeanFactoryPostProcessor is prolly the way to go.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] Resolved: (JAMES-966) Refactor LoaderService to not create instances of class on its own

Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
     [ https://issues.apache.org/jira/browse/JAMES-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Maurer resolved JAMES-966.
---------------------------------

    Resolution: Fixed

done

> Refactor LoaderService to not create instances of class on its own
> ------------------------------------------------------------------
>
>                 Key: JAMES-966
>                 URL: https://issues.apache.org/jira/browse/JAMES-966
>             Project: JAMES Server
>          Issue Type: Improvement
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>             Fix For: 3.0-M1
>
>
> The current LoaderService implementation create instances by using newInstance() which is a bad practice (IMHO). Instances should only get created by the container (spring). Using a BeanFactoryPostProcessor is prolly the way to go.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] Assigned: (JAMES-966) Refactor LoaderService to not create instances of class on its own

Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
     [ https://issues.apache.org/jira/browse/JAMES-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Maurer reassigned JAMES-966:
-----------------------------------

    Assignee: Norman Maurer

> Refactor LoaderService to not create instances of class on its own
> ------------------------------------------------------------------
>
>                 Key: JAMES-966
>                 URL: https://issues.apache.org/jira/browse/JAMES-966
>             Project: JAMES Server
>          Issue Type: Improvement
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>             Fix For: 3.0-M1
>
>
> The current LoaderService implementation create instances by using newInstance() which is a bad practice (IMHO). Instances should only get created by the container (spring). Using a BeanFactoryPostProcessor is prolly the way to go.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org