You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2008/06/14 06:19:05 UTC

[jira] Created: (WW-2677) Support multiple parent packages defined on package

Support multiple parent packages defined on package
---------------------------------------------------

                 Key: WW-2677
                 URL: https://issues.apache.org/struts/browse/WW-2677
             Project: Struts 2
          Issue Type: New Feature
          Components: Plugin - CodeBehind
    Affects Versions: 2.1.2
            Reporter: Don Brown
             Fix For: 2.1.3


Currently, it is pretty confusing how to set the parent package for an action in the codebehind plugin.  Basically, it gathers all the @ParentPackage annotations on all actions in the package, then sets the generated parent package list based on the created list.  This is confusing and unintuitive.

The better approach would be to allow the @ParentPackage annotation on the package via the package-info.java file, and let a list of parents be specified.  Then, it is no longer necessary to decorate any action in the package.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (WW-2677) Support multiple parent packages defined on package

Posted by "Don Brown (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/struts/browse/WW-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Don Brown resolved WW-2677.
---------------------------

    Resolution: Fixed
      Assignee: Don Brown

Fixed and added the appropriate docs

> Support multiple parent packages defined on package
> ---------------------------------------------------
>
>                 Key: WW-2677
>                 URL: https://issues.apache.org/struts/browse/WW-2677
>             Project: Struts 2
>          Issue Type: New Feature
>          Components: Plugin - CodeBehind
>    Affects Versions: 2.1.2
>            Reporter: Don Brown
>            Assignee: Don Brown
>             Fix For: 2.1.3
>
>
> Currently, it is pretty confusing how to set the parent package for an action in the codebehind plugin.  Basically, it gathers all the @ParentPackage annotations on all actions in the package, then sets the generated parent package list based on the created list.  This is confusing and unintuitive.
> The better approach would be to allow the @ParentPackage annotation on the package via the package-info.java file, and let a list of parents be specified.  Then, it is no longer necessary to decorate any action in the package.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.