You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Ted Husted (JIRA)" <ji...@apache.org> on 2006/11/27 02:50:57 UTC
[jira] Created: (WW-1522) Create ActionConfigs for Action class
methods that do not already have aliases
Create ActionConfigs for Action class methods that do not already have aliases
------------------------------------------------------------------------------
Key: WW-1522
URL: http://issues.apache.org/struts/browse/WW-1522
Project: Struts 2
Issue Type: Improvement
Reporter: Ted Husted
Fix For: 2.0.2
The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1522) Automatic Alias ActionConfigs
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown updated WW-1522:
--------------------------
Fix Version/s: (was: 2.0.3)
2.0.x
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: https://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Assigned To: Ted Husted
> Fix For: 2.0.x
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1522) Automatic Alias ActionConfigs
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Husted updated WW-1522:
---------------------------
Fix Version/s: (was: 2.0.x)
2.1.x
Bumping issues to 2.1.x, except those that involve backward-compatability with Struts 1 or WebWork 2.
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: https://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Assigned To: Ted Husted
> Fix For: 2.1.x
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1522) Automatic Alias ActionConfigs
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1522?page=all ]
Ted Husted updated WW-1522:
---------------------------
Fix Version/s: 2.0.3
(was: 2.0.2)
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: http://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Assigned To: Ted Husted
> Fix For: 2.0.3
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1522) Automatic Alias ActionConfigs
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown updated WW-1522:
--------------------------
Fix Version/s: (was: 2.1.3)
Future
All the necessary hooks should now be in place, so we just need someone to make it happen.
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: https://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Fix For: Future
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-1522) Automatic Alias ActionConfigs
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39240 ]
Don Brown commented on WW-1522:
-------------------------------
To resolve this issue, we need to find a way to post-process a built configuration object, in order to scan for loaded action configs and build some more. The easiest solution would be to simply put the code in DefaultConfiguration. A close second would be to add a hook in the building of runtime configuration in DefaultConfiguration then subclass DefaultConfiguration for Struts, putting the code there. Another possibility would be to add a method to ConfigurationProvider so that a provider would have a chance at modifying the runtime configuration. Of the three, I like the second option.
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: http://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Assigned To: Ted Husted
> Fix For: 2.0.3
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (WW-1522) Automatic Alias ActionConfigs
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1522?page=all ]
Ted Husted reassigned WW-1522:
------------------------------
Assignee: Ted Husted
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: http://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Assigned To: Ted Husted
> Fix For: 2.0.2
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WW-1522) Automatic Alias ActionConfigs
Posted by "Brian Pontarelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40920 ]
Brian Pontarelli commented on WW-1522:
--------------------------------------
If the post-processing has to know all of the already loaded configuration than the options you listed are the only ones. However, if it doesn't this can be handled by a custom ConfigurationProvider which can simply add the aliases.
There is still one problem with configuration that I can't seem to find a way around. We need some mechanism for introducing new ConfigurationProviders and handling the configuration prior to the initialization process. I think that by fixing the configuration mechanism to have more lifecycle and for Struts to allow plug points at each stage we will effectively fix all of these issues.
Perhaps a new enhancement or changing this one makes the most sense.
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: https://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Fix For: 2.1.0
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WW-1522) Automatic Alias ActionConfigs
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1522?page=all ]
Ted Husted updated WW-1522:
---------------------------
Summary: Automatic Alias ActionConfigs (was: Create ActionConfigs for Action class methods that do not already have aliases)
Description:
Create ActionConfigs for Action class methods that do not already have aliases
The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
was:
The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: http://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Fix For: 2.0.2
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1522) Automatic Alias ActionConfigs
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Husted updated WW-1522:
---------------------------
Assignee: (was: Ted Husted)
> Automatic Alias ActionConfigs
> -----------------------------
>
> Key: WW-1522
> URL: https://issues.apache.org/struts/browse/WW-1522
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Ted Husted
> Fix For: 2.1.0
>
>
> Create ActionConfigs for Action class methods that do not already have aliases
> The initial "dynamic method invocation" implementation does not create an ActionConfig, but scans for a "!" and invokes the method directly. The implementation doesn't allow these alias methods to be browsed, overrridden with static actions, nor can they have their own validators, type convertors or resources.
> Rather than scan for dynamic method references at run time, an alternate approach would be to scan the configuration when it is first loaded and create ActionConfigs for all potential alias methods.
> See also http://www.mail-archive.com/dev%40struts.apache.org/msg25916.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.