[jbosstools-issues] [JBoss JIRA] (JBIDE-12446) Migrate CDI Tools model to SQL(?) DB instead of using Java collections

Alexey Kazakov (JIRA) jira-events at lists.jboss.org
Thu Aug 23 15:44:15 EDT 2012


     [ https://issues.jboss.org/browse/JBIDE-12446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kazakov updated JBIDE-12446:
-----------------------------------

        Parent: JBIDE-12479
    Issue Type: Sub-task  (was: Task)

    
> Migrate CDI Tools model to SQL(?) DB instead of using Java collections
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-12446
>                 URL: https://issues.jboss.org/browse/JBIDE-12446
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: CDI
>            Reporter: Alexey Kazakov
>            Assignee: Alexey Kazakov
>             Fix For: 4.0.x
>
>
> Right now we are using Java collections (Maps, Sets, Lists) to store model artifacts. It works ok for small projects. For big projects, we will probably face serious problems with performance and memory usage.
> Let's investigate what we can do there and what we can benefit of using SQL DB as a storage for big CDI projects.
> Here is the list of possible steps for this work:
> # Create a test project or rather a code which will be able to create big test projects. We will use those projects for testing performance/memore usage for different types of storages.
> # Research different DB/persistence frameworks to find options which are best for our goal.
> # Split CDI Tools core into core interfaces/services for the storage and storage implementations.
> # Implement DB storage and test it against our test projects (see step #1)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list