portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject Re: [J2] Proposed refactoring of Jetspeed 2 API interfaces
Date Thu, 20 May 2004 17:23:06 GMT

On May 19, 2004, at 7:48 AM, Ate Douma wrote:

> Scott T Weaver wrote:
>> 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.
> While I'm +1 on moving the interfaces out from the component 
> implementations, I'm not so sure about moving them into commons.
> As I see it, there are currently two different usages of the commons. 
> One is for building *on top of* J2 specific features like the 
> ServletPortlet or the StrutsServletContextProviderImpl.
> The other is for providing interfaces and base classes for assembling 
> and access to the J2 core itself.
Im proposing creating a component to house the ServletPortlet, 
StrutsServletContextProviderImpl and supporting classes.
Not sure on the name, what about "jetspeed-pa-core" -- since the jar is 
used to aid in handling internal portal to portlet application 

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

View raw message