Philipp, sounds like what you want is already happening, given that XWork is partitioned into XWork and WebWork 2.0 already.
On Thu, 30 Jan 2003, Philipp Meier wrote: > On Thu, Jan 30, 2003 at 07:37:45AM -0800, Jason Carreira wrote: > > > Oh, other than the ThreadLocal thing, there are also remaining questions > > about Ognl and whether we can plug in our EL, or whether it should be > > undertaken to re-architect our existing EL for performance. > > I want to propose to partition the xwork in several (independent) modules. > Because I e.g. do not use jsp or velicity, and because I do not > contribute to the development, it would be nice to seperate them from > the core stuff. It makes sense to me to have the following cvs modules: > > * xwork (or xwork-core) > * xwork-web (ServletDispatcher and FilterDispatcher and so on.) > * xwork-view-el (used by jsp and velocity) > * xwork-view-jsp > * xwork-view-velocity > * xwork-view-xslt > * xwork-view-freemarker > * xwork-jms (Dispatcher and helpers for JMS) > * xwork-mail (Dispatcher and helpers for Mail) > > Does this make sense? I see xwork growing and growing and becoming more > and more confusing. On the other hand, size does matter and we must > consider that every view type needs it's supporting libraries. > > My €0.02, > -billy. > > --------------------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.com IT Consultant ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
