[JBoss JIRA] Created: (JBIDE-3236) SeamGen - provide ability to customize generated class/page names and paths
by Maksim Kaszynski (JIRA)
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
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
11 years, 8 months
[JBoss JIRA] Created: (JBIDE-5441) Allow prefix / suffix for generated field names
by Olivier Cailloux (JIRA)
Allow prefix / suffix for generated field names
-----------------------------------------------
Key: JBIDE-5441
URL: https://jira.jboss.org/jira/browse/JBIDE-5441
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Environment: eclipse hibernate tools
Reporter: Olivier Cailloux
Priority: Minor
When using hibernate tools to generate pojo from an existing database, it would be nice to be able to prefix the generated field names. That is, instead of e.g.
Code:
private String name;
public Criterion(String name) {
this.name = name;
}
//...
@Column(name = "name", nullable = false)
public String getName() {
return this.name;
}
Having
Code:
private String m_name;
public Criterion(String name) {
this.m_name = name; // (or even better, simply m_name = name, but I don't mind so much)
}
//...
@Column(name = "name", nullable = false)
public String getName() {
return this.m_name; // or return m_name;
}
Basically, the goal is to allow leaving the compiler option to error when a variable name overrides a field name.
Currently, it is possible to do so, but not very easy. You need to find somewhere the default templates (e.g. in the Hibernate Tools source code) and edit them and reference them in the Tools config. See the forum post for detailed steps [https://forum.hibernate.org/viewtopic.php?f=6&t=1001437&p=2422311#p2422311].
I think that the prefix functionality should be optionally available using a configuration property in hibernate tools, because I think it is good practice to enable the compiler complaint when a local variable name overrides a field name, and the current default behavior of hibernate tools (requiring to modify the template, which is not such an easy thing at least for a beginner, IMHO) rather encourages the user to simply uncheck the compiler warning.
Even more advanced, the hibernate tools, when used as an eclipse plug-in, could use the fields prefix and suffix properties which can be set in Window / Preferences, Java / Code style.
Thank you for your attention.
--
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
11 years, 8 months
[JBoss JIRA] Created: (JBIDE-2173) Performance problems with rather big db - Hibernate Console view can't process rather big amount of tables
by Vitali Yemialyanchyk (JIRA)
Performance problems with rather big db - Hibernate Console view can't process rather big amount of tables
----------------------------------------------------------------------------------------------------------
Key: JBIDE-2173
URL: http://jira.jboss.com/jira/browse/JBIDE-2173
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Reporter: Vitali Yemialyanchyk
Assigned To: Vitali Yemialyanchyk
Priority: Minor
For test purposes I create org.hibernate.eclipse.console.test -> org.hibernate.eclipse.console.db.test.BigDBCreateTest - the main goal of this class is creation test database with specified number of related tables. Then with help of BigDBCreateTest I create a big enough databases with different number of tables in it. And then I try to test hibernate plugins performance. I create a configuration for my test db.
In Hibernate Console I try to expand tree. Here is a time:
200 tables in db - takes 40 seconds;
300 tables in db - takes 2 minutes 45 seconds;
500 tables in db - too long I do not get results.
Remark: I use MySQL as test db. 3000 tables - too much for MySQL. Also - it is intresting - when I create such big db - I try to expand Hibernate Console tree - I get MySQL exception - but in this case Hibernate Console display all items quickly!
JBIDE-2162 is related;
JBIDE-2163 & JBIDE-2164 are related by implication - till the moment when I have fixed its in my test environment - I can't see performance problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] Created: (JBDS-1229) ESB binary export from JBDS doesn't include source
by Stelios Koussouris (JIRA)
ESB binary export from JBDS doesn't include source
--------------------------------------------------
Key: JBDS-1229
URL: https://jira.jboss.org/browse/JBDS-1229
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: libmanagement
Affects Versions: 3.0.0.GA
Reporter: Stelios Koussouris
Trying to export ESB binary along with the source code of
a) the esb actions
b) the referenced jars
The result of setting the references to other projects/jars via
ESB Project --> Properties --> Module Assembly and then
ESB Project --> Export --> ESB --> clicking the "export source files"
the jars of the referenced projects are included but no source code for nether the ESB classes or the referenced projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months