That seems like a reasonable bridge, James. A driving force behind plugins, and the new request processor, is being able to extend the core framework for extensions as radical as Tiles. It seems appropriate that we keep Tiles at arms-length, to show that something like this can be plugged in without being hardwired into the Core.
-Ted. On 9/13/05, James Mitchell <[EMAIL PROTECTED]> wrote: > > I'm not 100% sure of this myself yet, but it may be a good idea at > this time to pull out the Tiles dependencies from core and provide > them via a separate plugin (see struts/current/plugins). > > While this does add another jar to our applications, it would allow a > developer to use either classic Tiles or standalone Tiles for the > foreseeable future, or until classic is deprecated/removed. Core > shouldn't have to care one way or the other, and for the few people > who have extended Tiles, they can continue to use classic even if > 1.3.x ships with standalone. > > Your thoughts? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
