In Struts 2, the action mapping names attributes still hash to URIs, so we still have the same problem. Though, I can understand why someone would want to give action mappings logical names that are not part of the "business logic".
Right now, the term "alias" is used in Struts 2 to indicate a "dispatch" method -- an alternative "execute" method. Using the same term to mean something else in the Struts 1 vernacular might be confusing. Following Struts 2 conventions, we might want to call the logical name "action-ref". I'd suggest that the action-ref default to the path, unless specified in the mapping, so that every action mapping is guaranteed to have an action-ref. I'm thinking of proposing class aliases for XWork 2, where we could give an internal logical name to FQNs. Then in the class (or type) element, we could refer to the alias rather than the full package and class name. Since the term "alias" was taken, my thought was to call these element "class-ref". If we apply the patch, we could add the set-properties capability to Struts 1.3, and then schedule a DTD change for Struts 1.4. Historically, we have not made DTD changes as part of a milestone (#.#.x) release. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
