On Wed, 12 Jan 2005 08:30:09 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote: > > > I'd like to get them all consolidated (at least as much as can be done) > >> providing a single mailreader.jar for the variations. > > > >Do you mean one jar of the bits common to all flavours, and then > >separate apps for each variation? If so, I think this would be a good > >approach. If you mean combine the various mailreader apps into one, I > >think that would muddy the waters, and wouldn't work as well as > >examples of how to do things. > > I've seen talk before about bundling the "business app" part of > Mailreader into its own jar, which I think is what you meant in your > first sentence, Martin. I think this is a good idea, because I think > beginning struts users sometimes don't have a good sense of how to > arrange for good separation of Struts from a more generalized > framework. In so far as we can demonstrate this a little bit, that > would be a good thing.
Note that this particular separation (of the model APIs and DAO) has been done already ... core/trunk/struts-examples/mailreader. We'd only need to make all the incantations of mailreader use this common code base to reduce some of the duplication. However, you're going to end up with different implementations no matter what ... they exist to illustrate different technological approaches to building the same app, to facilitate comparisons. Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
