On 5/25/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
This was added with the JPA commit and I think we should discuss a
little bit about the need for this component and how it will work.
To be honest though, at the end of the day I'm not really sure that it
makes much sense to try and manage a core component at this time. We
only have 2 apps and from what I see the amount of code that would be
appropriately shared between the two is fairly limited. I think it may
be more of an annoyance to maintain this core component, but of course
code reuse is something we should strive for.
I basically agree with all of your points. During development it was a
pain having to maintain two copies of the JPA strategy, so sharing
made sense for me.
I definitely agree that with only an exception class and a strategy
class in there it doesn't make much sense to have a core component,
but with Weblogger and Planet having almost identical architecture I
think we're going to want to do some significant sharing in the
future. And I really don't like having multiple copies of identical
classes in Planet and Roller. I think we need to consider the "core"
question as part of the larger "how do we wire things together"
question. Considering that question should make it easier to see how
things can be shared and plugged-in/injected.
- Dave
