On 4/23/06, Don Brown <[EMAIL PROTECTED]> wrote: > > I would think it would be Tiles' responsibility to support deployment > with Struts. In that view, Tiles would be its own project, yet part of > it would depend on struts-action.jar to provide the Struts hooks. In > the same way, they would provide Struts Action 2 hooks, if necessary.
This is a tough one - for me, at least. Should an independent Tiles have glue code for Struts, or should it be Struts' responsibility to provide the glue? If we look at Velocity, the glue is over there, but we've also talked about it coming here. If we look at Validator, the glue is here. If we look at Chain, the servlet and portlet glue is over there. My preference, at least at this time, would be for the Struts / Tiles glue to stay here. That will help Standalone Tiles stand on its own feet, and especially help with the notion that it's now independent of Struts. Any perception - real or otherwise - that Tiles is tied to Struts will be detrimental to Tiles as an independent library. -- Martin Cooper Don > > Wendy Smoak wrote: > > On 4/23/06, Don Brown <[EMAIL PROTECTED]> wrote: > > > >> Agreed. Would it be possible to do this by JavaOne? Moving Tiles > isn't > >> a huge deal, but it would make the new directions of Struts easier to > >> explain to users. > >> > > > > What happens to Struts Tiles, then? I'm not sure I understand why > > we're holding Struts Tiles out of the Struts Action distribution. > > > > Won't there always be a struts-tiles.jar of some kind, whether it's > > the current one with all the code, or a much lighter version that > > works with Standalone Tiles? > > > > -- > > Wendy > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
