portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-771) Refactor JetspeedSerializer to a pluggable component to be used by other components for import/export of (test) data
Date Fri, 18 Jul 2008 17:10:32 GMT

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

Ate Douma resolved JS2-771.

    Resolution: Fixed

This one has been fixed some time ago already

> Refactor JetspeedSerializer to a pluggable component to be used by other components for
import/export of (test) data
> --------------------------------------------------------------------------------------------------------------------
>                 Key: JS2-771
>                 URL: https://issues.apache.org/jira/browse/JS2-771
>             Project: Jetspeed 2
>          Issue Type: Sub-task
>          Components: Dependencies, Persistence and DAO, Project Build
>    Affects Versions: 2.2
>         Environment: Maven 2.0.7, Java 5
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>            Priority: Critical
>             Fix For: 2.2
> The JetspeedSerializer is a monolitic component which depends on all other components
for which it performs data serialization: capabilities, security, profiler and registry.
> This makes setting up a proper test environment without circular dependencies in the
build impossible.
> Furthermore, extending/improving upon the JetspeedSerializer is very difficult and cumbersome
to do right now.
> So, I'll turn the JetspeedSerializer "inside out", making it a "normal" Spring component
by itself, and breaking out the large serialization code in "pluggable" JetspeedComponentSerializer
> Then, each component for which serialization is needed, can provide its own (part of
the) serialization with a JetspeedComponentSerializer implementation scoped at the component
> Furthermore, and most important, because the main JetspeedSerializer(Impl) then can be
configured with one or more component serializers, and it no longer will depend on any of
> it can be used for seeding test data for a specific component (only).
> For the tests, I will also add a deleteData method to JetspeedComponentSerializer which
can be used for cleaning out (component specific) data before/after a test case run.
> One last remark:
> The current usage of the jetspeedSerializer is command line based through the JetspeedSerializerApplication.
> For now, I will remove the implementation code from this class because the new setup
requires a complete rehaul for it.
> Once we get all the database related components tests working properly again, this class
will need to be reimplemented.

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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message