> I don't think anyone has suggested getting rid of Themes or > Freemarker, just making them optional for the folks that don't > need/want them. Right now, there's no way to use struts without > Freemarker, without writing your own tag library. Well - actually no. You can re-write all the theme files as JSPs and then change the extension in the struts.properties / struts.xml file. Then JSP template for the theme's would be used instead of Freemarker. It just hasn't been done, or has been done and not contributed back ;-) > We're just > suggesting adding choice, not removing functionality. > (*Chris*) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
- Re: [s2] Should tags be their own plugin? Antonio Petrelli
- Re: [s2] Should tags be their own plugin? Ted Husted
- Re: [s2] Should tags be their own plugin? Musachy Barroso
- Re: [s2] Should tags be their own plugin? Patrick Lightbody
- Re: [s2] Should tags be their own plugin? Patrick Lightbody
- Re: [s2] Should tags be their own plugin? Matt Raible
- Re: [s2] Should tags be their own plugin? Piero Sartini
- Re: [s2] Should tags be their own plugin? Ian Roughley
- Re: [s2] Should tags be their own plugin? Jim Cushing
- Re: [s2] Should tags be their own plugin? Chris Pratt
- Re: [s2] Should tags be their own plugi... Ian Roughley
- Re: [s2] Should tags be their own ... Chris Pratt
- Re: [s2] Should tags be their own plugi... Ted Husted
- Re: [s2] Should tags be their own plugin? Ted Husted
- Re: [s2] Should tags be their own plugin? Ian Roughley
- Re: [s2] Should tags be their own plugin? Martin Cooper
- Re: [s2] Should tags be their own plugin? Brian Pontarelli
- Re: [s2] Should tags be their own plugin? Martin Cooper
- Re: [s2] Should tags be their own plugin? Brian Pontarelli
- Re: [s2] Should tags be their own plugin? Chris Pratt
- Re: [s2] Should tags be their own plugin? Ted Husted