You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "James Holmes (JIRA)" <ji...@apache.org> on 2007/09/05 17:03:34 UTC
[jira] Created: (WW-2157) Update Struts1 plugin to support using
Struts 1 tag libraries in JSP pages
Update Struts1 plugin to support using Struts 1 tag libraries in JSP pages
--------------------------------------------------------------------------
Key: WW-2157
URL: https://issues.apache.org/struts/browse/WW-2157
Project: Struts 2
Issue Type: Improvement
Components: Plugins
Reporter: James Holmes
Fix For: 2.1.x
Currently the Struts1 plugin only provides the ability to run Struts 1 actions in a Struts 2 application. It would be much easier for existing applications to migrate to Struts 2 if they did not have to convert all of their JSPs to use the Struts 2 tag library tags instead of Struts 1 tag library tags.
The main issue is that the Struts 1 tags are expecting some of the Struts 1 infrastructure to be in place - mainly the ModuleConfig info I believe.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WW-2157) Update Struts1 plugin to support using
Struts 1 tag libraries in JSP pages
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown updated WW-2157:
--------------------------
Fix Version/s: (was: 2.1.x)
Future
> Update Struts1 plugin to support using Struts 1 tag libraries in JSP pages
> --------------------------------------------------------------------------
>
> Key: WW-2157
> URL: https://issues.apache.org/struts/browse/WW-2157
> Project: Struts 2
> Issue Type: Improvement
> Components: Plugin - Mechanism
> Reporter: James Holmes
> Fix For: Future
>
>
> Currently the Struts1 plugin only provides the ability to run Struts 1 actions in a Struts 2 application. It would be much easier for existing applications to migrate to Struts 2 if they did not have to convert all of their JSPs to use the Struts 2 tag library tags instead of Struts 1 tag library tags.
> The main issue is that the Struts 1 tags are expecting some of the Struts 1 infrastructure to be in place - mainly the ModuleConfig info I believe.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2157) Update Struts1 plugin to support using
Struts 1 tag libraries in JSP pages
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45938#action_45938 ]
Musachy Barroso commented on WW-2157:
-------------------------------------
James, do you know what tags break? I tried just a couple and they worked, like "bean:write" and "logic:equals"
> Update Struts1 plugin to support using Struts 1 tag libraries in JSP pages
> --------------------------------------------------------------------------
>
> Key: WW-2157
> URL: https://issues.apache.org/struts/browse/WW-2157
> Project: Struts 2
> Issue Type: Improvement
> Components: Plugin - Mechanism
> Reporter: James Holmes
> Fix For: Future
>
>
> Currently the Struts1 plugin only provides the ability to run Struts 1 actions in a Struts 2 application. It would be much easier for existing applications to migrate to Struts 2 if they did not have to convert all of their JSPs to use the Struts 2 tag library tags instead of Struts 1 tag library tags.
> The main issue is that the Struts 1 tags are expecting some of the Struts 1 infrastructure to be in place - mainly the ModuleConfig info I believe.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.