July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8234) Create JUnit test for hibernate schema/catalog passed to hibernate-tools.

by Dmitry Geraskov (JIRA)

Create JUnit test for hibernate schema/catalog passed to hibernate-tools. ------------------------------------------------------------------------- Key: JBIDE-8234 URL: https://issues.jboss.org/browse/JBIDE-8234 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.2.x See the fix for https://issues.jboss.org/browse/JBIDE-8189 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1611) hibernate reverce engeniering

by Vitali Yemialyanchyk (JIRA)

hibernate reverce engeniering ----------------------------- Key: JBIDE-1611 URL: http://jira.jboss.com/jira/browse/JBIDE-1611 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Vitali Yemialyanchyk Assigned To: Vitali Yemialyanchyk Priority: Minor Fix For: LATER Attachments: dialog.jpg GUI -> Package - as I think this should be obligatory field - so user should get some message about it. Of cource he could firstly run it - see result - then delete -> specify the package and run one again... reveng. strategy -> I can't get it work - so should be some more questions here. GUI -> Main & Exporters tab -> if the dialog small enough - some buttons and controls envisible -> in this case should be scrollbars were. Generation result -> all files in one place. Domain model classes should be in one separate package and POJO classes in other. User should get possibility to specify this. Other during generation process - generator simply rewrite my old files - should be some message here. rewrite all or just one - should be clear. -- 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, 12 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-1767) Generating Java Code drom hbm.xml faulty

by Carsten Hoehne (JIRA)

Generating Java Code drom hbm.xml faulty ---------------------------------------- Key: JBIDE-1767 URL: http://jira.jboss.com/jira/browse/JBIDE-1767 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 2.0.0.GA Reporter: Carsten Hoehne Problem with generating java code from hbm.xml. In the forum my original project is mentioned. In the meantime i have stripped down the problem to a one2one dependency and a one2many dependency. I will attach the files. -- 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, 12 months

5
10
0 / 0

[JBoss JIRA] (JBIDE-11438) Length import is not correct when using AS71 and HB4 seam generating entity

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11438: ------------------------------------ Summary: Length import is not correct when using AS71 and HB4 seam generating entity Key: JBIDE-11438 URL: https://issues.jboss.org/browse/JBIDE-11438 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate, Seam 2 Affects Versions: 3.3.0.Beta2 Environment: JBDS 5.0, Beta2, L64,HSQLDB 1.8 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta3 Attachments: length-annotation.png While generating entities (HB40,AS71), Length should be imported from: import org.hibernate.validator.constraints.Length; but it's imported non existing package: import org.hibernate.validator.Length; @Length(max = 200) public String getSurname() { return this.surname; } public void setSurname(String surname) { this.surname = surname; } Generated classes should lib according to defined runtime I guess -- 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

11 years, 12 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6096) Hibernate Console Configuration in standard Run Configuration list

by Jiri Peterka (JIRA)

Hibernate Console Configuration in standard Run Configuration list ------------------------------------------------------------------ Key: JBIDE-6096 URL: https://jira.jboss.org/jira/browse/JBIDE-6096 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.GA Reporter: Jiri Peterka Fix For: 3.2.next Hibernate Code generation configuration is separated from other run configuration. I can't see any reason why it's not part of other standard run configurations. It should be moved there. -- 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, 12 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8379) Create/Edit Configuration - Options - set/select SessionFactoryObserver

by Vitali Yemialyanchyk (JIRA)

Create/Edit Configuration - Options - set/select SessionFactoryObserver ----------------------------------------------------------------------- Key: JBIDE-8379 URL: https://issues.jboss.org/browse/JBIDE-8379 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.3.x Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Optional Fix For: 3.3.x should be possible to set SessionFactoryObserver in Hibernate Console Configuration - Options page JBIDE-8373 - similar issue -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

4
3
0 / 0

[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, 12 months

8
14
0 / 0

[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, 12 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6666) Run HQL query in HQL editor as external process functionality

by Vitali Yemialyanchyk (JIRA)

Run HQL query in HQL editor as external process functionality ------------------------------------------------------------- Key: JBIDE-6666 URL: https://jira.jboss.org/browse/JBIDE-6666 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.M1 Reporter: Vitali Yemialyanchyk Assignee: Max Rydahl Andersen Priority: Minor Fix For: 3.2.0.M2 -- 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, 12 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5147) Print Preview for Hibernate Diagram Viewer

by Vitali Yemialyanchyk (JIRA)

Print Preview for Hibernate Diagram Viewer ------------------------------------------ Key: JBIDE-5147 URL: https://jira.jboss.org/jira/browse/JBIDE-5147 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.CR1 initial discussion start here: JBIDE-4756 -- 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, 12 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2012