You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/05/05 12:53:15 UTC

[jira] [Assigned] (SLING-3074) Repository, SerializationManager - make stateful based on RepositoryInfo

     [ https://issues.apache.org/jira/browse/SLING-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu reassigned SLING-3074:
--------------------------------------

    Assignee: Robert Munteanu

> Repository, SerializationManager - make stateful based on RepositoryInfo
> ------------------------------------------------------------------------
>
>                 Key: SLING-3074
>                 URL: https://issues.apache.org/jira/browse/SLING-3074
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.0.0
>
>
> Currently the Repository interface has a setRepositoryInfo method which is used to configure the repository in use. From a thread safety point of view, this is dangerous and will most likely result in problems when multiple repositories are used. The SerializationManager follows a similar pattern with the init/destroy methods.
> The DS components in use should rather be RepositoryFactory and SerializationManagerFactory, and implementations should invoke the factory methods on them, supplying the required arguments.
> Also, the SerializationManager is currently very slow since it has to mount a VaultFileSystem for  each operation. Making the Repository and SerializationManager stateful will help with this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)