]
Vitali Yemialyanchyk commented on JBIDE-3236:
---------------------------------------------
here I mean feature with right mouse btn click on .reveng.xml file -> then Run As ->
submenu should display all Hibernate Code Generation Configs which point to this
.reveng.xml file and should be possible to create new Hibernate Code Generation
Configuration which point to source .reveng.xml automatically.
Initially this issue was a source of idea... but description did not correspond to what I
imagine how this be implemented. i.e. it is possible to close this issue - cause there is
a feature which is in description, but create a new feature request for Run As for
.reveng.xml file - which I summarize above.
SeamGen - provide ability to customize generated class/page names and
paths
---------------------------------------------------------------------------
Key: JBIDE-3236
URL:
https://issues.jboss.org/browse/JBIDE-3236
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate, Seam
Reporter: Maksim Kaszynski
Assignee: Vitali Yemialyanchyk
Priority: Minor
Labels: new_and_noteworthy
Fix For: 3.3.x
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.
-
For more information on JIRA, see: