Makes perfectly sense.
It makes it easier to implement a different persistent storage if we decide to move away from OJB.
Roger
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.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
