[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-3236) SeamGen - provide ability to customize generated class/page names and paths

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-3236:
---------------------------------------

    Fix Version/s: 3.2.next
                       (was: 3.1.0.CR1)


> SeamGen - provide ability to customize generated class/page names and paths
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-3236
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3236
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Seam
>            Reporter: Maksim Kaszynski
>            Assignee: Max Rydahl Andersen
>            Priority: Minor
>             Fix For: 3.2.next
>
>
> When using "Seam Generate Entities" ability in JBDS, it puts all generated pages and .page.xml files into view folder, and names them "FooList", "FooView", "FooEdit". This may be ok when there's up to 10 entities in the application, but when there's more, view folder becomes a bloody mess.
> It would be nice if there was possibliity to customize seam-gen output pattern, for example, "view/{class-name}/list.xhtml", so for Foo enity it would be "view/foo/list.xhtml", "view/foo/view.xhtml", "view/foo/edit.xhtml".
> Of course, it is possible to change view folder before launching "Generate Entities" for every entity, but it is not nice to do it 100 times when generating entities for hundred tables.
> When using console seam-gen, it is possible to co change that naming template in ant script, but JBDS has it all hard-coded.
> I propose to have some dialog for customizing output patterns.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira