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] Closed: (JS2-30) Create a Jetspeed 2 "core" sub project
Date Thu, 29 Sep 2005 00:16:50 GMT
     [ http://issues.apache.org/jira/browse/JS2-30?page=all ]
Ate Douma closed JS2-30:

    Resolution: Fixed

We created jetspeed-api a (very) long time ago already.

> Create a Jetspeed 2 "core" sub project
> --------------------------------------
>          Key: JS2-30
>          URL: http://issues.apache.org/jira/browse/JS2-30
>      Project: Jetspeed 2
>         Type: Task
>   Components: Components Core
>     Versions: 2.0-a1
>     Reporter: Scott T Weaver
>     Assignee: Scott T Weaver

> What I had started doing in my branch was moving interfaces out of the component implementations
and portal/ and into commons.  This makes it easier to test components that may access these
other interfaces without having to specifically depend on the component implementation.  This
also makes our code more modular and extensible.  Say, for example, some one wants to implement
a persistence store using Hibernate.  As the current source layout is set up, the user would
have a dependency on the the current persistence store implementation built with OJB because
that is where the interfaces are leading them to having to have ALL the dependencies OJB required
also.  By moving all the persistence store interfaces up into commons, all the developer needs
as dependency is the jetspeed 2 commons jar.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

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

View raw message