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 Assignee: Vitali Yemialyanchyk 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...]. 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.

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 Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.2.next 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...]. 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.

Allow prefix / suffix for generated field names ----------------------------------------------- Key: JBIDE-5441 URL: https://jira.jboss.org/browse/JBIDE-5441 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Environment: eclipse hibernate tools Reporter: Olivier Cailloux Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.2.x Attachments: screenshot-1.jpg 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...]. 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.

Allow prefix / suffix for generated field names ----------------------------------------------- Key: JBIDE-5441 URL: https://jira.jboss.org/browse/JBIDE-5441 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Environment: eclipse hibernate tools Reporter: Olivier Cailloux Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.2.x Attachments: screenshot-1.jpg 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...]. 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.

Allow prefix / suffix for generated field names ----------------------------------------------- Key: JBIDE-5441 URL: https://issues.jboss.org/browse/JBIDE-5441 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Environment: eclipse hibernate tools Reporter: Olivier Cailloux Assignee: Dmitry Geraskov Priority: Minor Labels: code_style, compiler, configuration_property, prefix, suffix, templates Fix For: 3.4.x Attachments: screenshot-1.jpg 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...]. 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.

Allow prefix / suffix for generated field names ----------------------------------------------- Key: JBIDE-5441 URL: https://issues.jboss.org/browse/JBIDE-5441 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Environment: eclipse hibernate tools Reporter: Olivier Cailloux Assignee: Koen Aers Priority: Minor Labels: code_style, compiler, configuration_property, prefix, suffix, templates Fix For: 4.0.x Attachments: screenshot-1.jpg 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...]. 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.