December 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1444) Hibernate Code Generation: when generating EJB3 annotations - compile errors because ejb3-persistence.jar is not in the classpath

by Alexander Chabatar (JIRA)

Hibernate Code Generation: when generating EJB3 annotations - compile errors because ejb3-persistence.jar is not in the classpath ---------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1444 URL: http://jira.jboss.com/jira/browse/JBIDE-1444 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Affects Versions: LATER Reporter: Alexander Chabatar Assigned To: Alexander Chabatar Priority: Minor Fix For: LATER -- 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, 7 months

6
8
0 / 0

[JBoss JIRA] Created: (JBIDE-1768) hbm2java: error generating collection of components

by Carsten Hoehne (JIRA)

hbm2java: error generating collection of components --------------------------------------------------- Key: JBIDE-1768 URL: http://jira.jboss.com/jira/browse/JBIDE-1768 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 2.0.0.GA Reporter: Carsten Hoehne Java code with annotations should be generated from a mapping file. This file contains a collection of components. Then an exception is thrown. See forum reference. The files will be attached. -- 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, 7 months

4
50
0 / 0

[JBoss JIRA] Created: (JBIDE-1882) org.hibernate.tool.hbm2x.ExporterException: File pattern not set on class org.hibernate.tool.hbm2x.GenericExporter

by Anton Klimkovich (JIRA)

org.hibernate.tool.hbm2x.ExporterException: File pattern not set on class org.hibernate.tool.hbm2x.GenericExporter ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-1882 URL: http://jira.jboss.com/jira/browse/JBIDE-1882 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 2.1 Reporter: Anton Klimkovich Attachments: exception1.txt EXECUTE: Create Seam EAR project EXECUTE: Add new Entity EXECUTE: Open Hibernate Code Generation Dialog EXECUTE: Select Seam-ejb configuration and select output folder EXECUTE: Open Exporters tab EXECUTE: Set checkbox to Generic Exporter (<hbmtemplate>) EXECUTE: Press Apply and Run buttons FAILURE: org.hibernate.tool.hbm2x.ExporterException: File pattern not set on class org.hibernate.tool.hbm2x.GenericExporter Log attached. -- 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, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1414) Synchronize labels/icons on Hibernate Configurations view (configuration and database part) and Mapping diagram editor (better)

by Alexander Chabatar (JIRA)

Synchronize labels/icons on Hibernate Configurations view (configuration and database part) and Mapping diagram editor (better) ------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1414 URL: http://jira.jboss.com/jira/browse/JBIDE-1414 Project: JBoss Tools Issue Type: Feature Request Reporter: Alexander Chabatar Assigned To: Alexander Chabatar -- 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, 7 months

4
6
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, 7 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, 7 months

5
10
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, 7 months

8
14
0 / 0

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

5
44
0 / 0

[JBoss JIRA] Created: (JBIDE-3314) Generic Exporter Option to on Create but do not Overwrite

by Francisco Jose Peredo Noguez (JIRA)

Generic Exporter Option to on Create but do not Overwrite --------------------------------------------------------- Key: JBIDE-3314 URL: https://jira.jboss.org/jira/browse/JBIDE-3314 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Francisco Jose Peredo Noguez In need an option to easily configure a Generic Exporter so that it creates the file if it does not exist, but if the file already exists, it should just silently skip it (not overwrite it). -- 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, 7 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-473) JBoss AS ignores context root property of dynamic web project

by Viacheslav Kabanovich (JIRA)

JBoss AS ignores context root property of dynamic web project ------------------------------------------------------------- Key: JBIDE-473 URL: http://jira.jboss.com/jira/browse/JBIDE-473 Project: JBoss Tools Issue Type: Feature Request Reporter: Viacheslav Kabanovich Open editor for Tomcat Server (double click Tomcat node in Servers view). The editor has two tabs - Overview and Modules. In Modules tab, it is possible to select a registered web project and call dialog for changing path (context root) property by Edit button. Then, for example, if project's name is MyProject but path is set to /OurProject, in order to access the application running on Tomcat server one has to type in browser an address like http://localhost:8080/OurProject rather than http://localhost:8080/MyProject. Red Hat studio defines menu action 'Register Web Context in Server', which invokes dialog that allows to set context root property. That works fine with Tomcat server, but fails with JBoss AS, because it seems that its implementation ignores this property of web project when deploying it. Hence, the request is to develop this functionality of JBoss AS to the level of Tomcat server. Context root property is accessible through class org.eclipse.wst.common.componentcore.internal.util.ComponentUtilities with methods public static void setServerContextRoot(IProject project, String contextRoot) public static String getServerContextRoot(IProject project) -- 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, 7 months

8
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2008