You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Nils-Helge Garli (JIRA)" <ji...@apache.org> on 2007/08/30 10:12:34 UTC
[jira] Created: (WW-2149) Add new S2 tags for html, head and body
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
Create new tags for html, head and body with support for different "renderers", such as 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42068 ]
James Holmes commented on WW-2149:
----------------------------------
I don't think I chimed in on this topic on the dev@ list, but I support this. It would definitely help with the projects I'm working on.
> 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
>
> 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.
[jira] Updated: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schneider updated WW-2149:
------------------------------
Fix Version/s: 2.0.12
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42069 ]
Tom Schneider commented on WW-2149:
-----------------------------------
Isn't there one for head already? It doesn't render <head></head> but it does allow you to put in standard stuff that should go in all the <head>'s on your project.
> 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
>
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Nils-Helge Garli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42070 ]
Nils-Helge Garli commented on WW-2149:
--------------------------------------
Yes, there is one for what's inside head, but we should have one that outputs the actual <head> as well. This is particularly useful for the portlet use case I described.
> 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
>
> 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.
[jira] Updated: (WW-2149) Add new S2 tags for html, head and body
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Holmes updated WW-2149:
-----------------------------
Fix Version/s: 2.1.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
> Fix For: 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42333 ]
Tom Schneider commented on WW-2149:
-----------------------------------
Here's my thoughts on the head tag, we either need a new name for the head tag (a head tag already exists) or we need to modify the existing head tag to include the '<head></head>' part of the html. I'm not sure which way would be better. The second option means we can't port it back to 2.0.x.
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42330 ]
James Holmes commented on WW-2149:
----------------------------------
As long as it doesn't break the 2.0 branch or cause incompatibility with other 2.0 releases, I'm all for it.
> 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
> Fix For: 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42329 ]
Tom Schneider commented on WW-2149:
-----------------------------------
Before we move to struts 2 (which will be soon) I'll need to resolve this. There's some code I already have for the body tag that I can use. My question is, can I please backport it to 2.0.x? That or I'll have to create a separate googlecode project to support 2.0.x.
> 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
> Fix For: 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Nils-Helge Garli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42343 ]
Nils-Helge Garli commented on WW-2149:
--------------------------------------
Making it possible to extend the tags via plugins would definetively be the best in my opinion.
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42336 ]
James Holmes commented on WW-2149:
----------------------------------
It could be part of the portlet plugin in 2.1, however, putting it in a plugin sort of defeats the point. The point is that having these tags would allow you to easily switch between being a webapp or a portlet transparently. Nothing says that users need/have to use these tags, but if you do use them then you get the advantage of being able to move to portlets transparently. There would be no requirement or even (encouragement) to use them otherwise.
> 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.
[jira] Assigned: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schneider reassigned WW-2149:
---------------------------------
Assignee: Tom Schneider
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42335 ]
Don Brown commented on WW-2149:
-------------------------------
Hmm... I don't know about this feature. Would you really want a tag that generates your head and body tags? Even Struts 1 didn't do that. Could this be done as a plugin? I like the general idea of tags being as intrusive as possible, as opposed to something like the JSF model where the whole page is composed of tags.
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42334 ]
James Holmes commented on WW-2149:
----------------------------------
We may not necessarily need a new tag to output the <head> tags AND be backward compatible. We could an extra optional attribute to that tag that indicates to output the <head> tags.
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42340 ]
Tom Schneider commented on WW-2149:
-----------------------------------
Ok, I create the following project http://code.google.com/p/extratags/. I'll be checking my code into there over the next day or so. Let me know if anyone needs commit access.
Tom
> 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.
[jira] Resolved: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schneider resolved WW-2149.
-------------------------------
Resolution: Won't Fix
I think it's best to keep this as a seperate plugin project starting out. I'll be pulling out the work I've been doing from core and moving into http://code.google.com/p/extratags/. All struts2 committers are free join the project, just let me know and I'll add you.
> 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.
[jira] Updated: (WW-2149) Add new S2 tags for html, head and body
Posted by "Nils-Helge Garli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nils-Helge Garli updated WW-2149:
---------------------------------
Description:
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
was:
Create new tags for html, head and body with support for different "renderers", such as 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
> 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
>
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42339 ]
Tom Schneider commented on WW-2149:
-----------------------------------
I'm going to have to agree with Don on this one. I think it makes more sense to at least start it as a separate plugin. I don't really care much if it's in core or if it's a seperate plugin, but our project needs a struts 2 tag that can output <body></body> and hook into onload. We can always move it into core if there's a valid reason. (Besides, I think Don wants to keep me from working on the core code) :o)
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42342 ]
Don Brown commented on WW-2149:
-------------------------------
Damn, you have discovered my plan to keep you out of core! :) Actually, I'd like to keep my own code out of core as well. My thought is what is in core should be 100% actively supported and understood by its committers. What I don't like is situations like the Ajax tags, where before Musachy, we had no one "owning" them and even now, the fact that he is basically the only guy who maintains the tags worries me. Anyways, this is a separate discussion, but I want to be clear that my misgivings about this ticket had nothing to do with you or even this specific issue to some extent. I'd rather err on the side of keeping things out of the core than let it get bloated and unmaintainable.
> 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.
[jira] Commented: (WW-2149) Add new S2 tags for html, head and body
Posted by "Tom Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42353 ]
Tom Schneider commented on WW-2149:
-----------------------------------
Ok, the basic implementation of these tags has been added to the googlecode project and the junits are in place. I haven't tested these in a full blown webapp yet, but we'll be giving the body tag a whirl when we upgrade to s2.
> 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.