[forge-issues] [JBoss JIRA] (FORGE-114) Common methods in scaffold controller bean should abstracted to a supper class

Lincoln Baxter III (Commented) (JIRA) jira-events at lists.jboss.org
Mon Dec 12 15:17:09 EST 2011


    [ https://issues.jboss.org/browse/FORGE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650195#comment-12650195 ] 

Lincoln Baxter III commented on FORGE-114:
------------------------------------------

Well said, Richard. Thanks for all of your work cleaning up those beans. There is nothing stopping users from extracting these beans out into a separate class (perhaps a good place for an extension point.)

~Lincoln
                
> Common methods in scaffold controller bean should abstracted to a supper class
> ------------------------------------------------------------------------------
>
>                 Key: FORGE-114
>                 URL: https://issues.jboss.org/browse/FORGE-114
>             Project: Forge
>          Issue Type: Enhancement
>          Components: Scaffold
>    Affects Versions: 1.0.0.Beta2
>            Reporter: Liu Jianhong
>            Priority: Optional
>             Fix For: 1.0.0.Beta4
>
>         Attachments: scaffold-metawidget-lib.zip, second.zip
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Controller bean should as flowing:
> @Named
> @RequestScoped
> public class @{entity.getName()}Bean extends AbstractBean<@{entity.getName()}> implements MenuItem
> {
> }
> And we also can implement more than one AbstractBean such as FilterableBean and so on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the forge-issues mailing list