[
https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42337
]
Don Brown commented on WW-2149:
-------------------------------
Switching between a portlet and servlet deployment is a major change, one I
wouldn't recommend for production usage. It will get even worse with JSR 286.
As for tags, if anything, I'd like to see Struts 2 getting rid of tags, or at
least, pushing them into plugins. The more tags we have, the more we have to
support, and the less time we have for core features, and let's be honest, we
don't have a lot of dev time being put into Struts 2 right now. A quick glance
at JIRA shows most of our tickets are around the tags, which frankly see little
work outside Musachy's heroic efforts with the Dojo tags.
I'm not saying I'm totally against putting this in, but I'd like to see a truly
compelling reason to justify the cost. At this point, I'm more -0
> Add new S2 tags for html, head and body
> ---------------------------------------
>
> Key: WW-2149
> URL: https://issues.apache.org/struts/browse/WW-2149
> Project: Struts 2
> Issue Type: Improvement
> Components: Views
> Reporter: Nils-Helge Garli
> Assignee: Tom Schneider
> Fix For: 2.0.12, 2.1.0
>
>
> Create new tags for html, head and body with support for different
> "renderers", like the url and form tags. There main reasons for this is:
> - We can control what's output, such as styles, scripts, doctypes etc
> - Rendering can be overridden. The portlet plugin would for instance not
> render the actual tags, since a portlet only should generate fragments. This
> way, the same JSPs can be used both when the application runs as a webapp and
> a portlet
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
