October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7380) Externalize String Dialog Shows not taking into account when we externalize string which value already exist in properties file

by Maxim Areshkau (JIRA)

Externalize String Dialog Shows not taking into account when we externalize string which value already exist in properties file ------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7380 URL: https://jira.jboss.org/browse/JBIDE-7380 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.Beta1 Reporter: Maxim Areshkau Assignee: Denis Maliarevich Fix For: 3.2.0.Beta2 Attachments: Externalize String Dialog.png When string which we want to externalize already exist in props file, dialog should use key that already exist and show to user info(or warning message). ExtDialog now shows error message, what absolutely inconvenient for user. -- 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

15 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7241) orm.xml version="2.0" doesn't work

by Juergen Zimmermann (JIRA)

orm.xml version="2.0" doesn't work ---------------------------------- Key: JBIDE-7241 URL: https://jira.jboss.org/browse/JBIDE-7241 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.M2 Environment: jbosstools-3.2.0.M2.aggregate-Update-2010-09-08_17-17-54-H243a.zip Reporter: Juergen Zimmermann Assignee: Max Andersen I'm using an orm.xml file with a JPA 2.0 declaration : <entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_2_0.xsd" version="2.0"> </entity-mappings> When I create a Hibernate configuration (database connection is reused from DTP and property file is an existing one), then I get the following stacktrace. I thought that https://jira.jboss.org/browse/JBIDE-6842 had fixed this issue. org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration Could not create JPA based Configuration <No message> java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException: <no message> java.lang.reflect.InvocationTargetException javax.persistence.PersistenceException: [PersistenceUnit: hskaPersistence] Unable to configure EntityManagerFactory [PersistenceUnit: hskaPersistence] Unable to configure EntityManagerFactory org.hibernate.MappingException: Error while parsing file: META-INF/orm.xml Error while parsing file: META-INF/orm.xml org.hibernate.MappingException: invalid mapping invalid mapping org.xml.sax.SAXParseException: cvc-complex-type.3.1: Value '2.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' has a fixed value of '1.0'. cvc-complex-type.3.1: Value '2.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' has a fixed value of '1.0'. -- 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

15 years, 4 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5703) Hibernate Reverse Engineering Editor should show multiple catalogs/schemas from a MySQL database

by Pieter Hartog (JIRA)

Hibernate Reverse Engineering Editor should show multiple catalogs/schemas from a MySQL database ------------------------------------------------------------------------------------------------ Key: JBIDE-5703 URL: https://jira.jboss.org/jira/browse/JBIDE-5703 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Pieter Hartog Priority: Minor MySQL is funny with catalogs and schemas. It doesn't support schemas like most other databases do. It's just called 'databases'. When you try to create a reveng.xml file using the Hibernate Reverse Engineering Editor, you can't get multiple databases / schemas to show up. It looks like the wizard looks at the hibernate.connection.url property in the hibernate-console.properties file. However, when I leave out the name of the database (e.g. jdbc:mysql://localhost:3306) without the database, the wizard does not return any tables. When you leave out the default database (i.e. schema) name in the connection.url, you should see all databases/ schemas for that one connection. When a user selects multiple schemas, the resulting reveng.xml file should have one <schema-selection ...> element for each schema the user wants to map tables from. -- 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

15 years, 4 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6622) [Designer] Search menus and toolbar buttons should only appear in Designer perspective

by Brian Fitzpatrick (JIRA)

[Designer] Search menus and toolbar buttons should only appear in Designer perspective -------------------------------------------------------------------------------------- Key: JBIDE-6622 URL: https://jira.jboss.org/browse/JBIDE-6622 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Barry LaFond Fix For: 3.2.x After installing Designer, I saw a couple of buttons on the toolbar: Find Model Object By Name and Open Metadata Search Page. Why do these seem to show up in every perspective? Same with the new items in the Search menu... Find Model Object, Metadata, Transformations. Does it make sense to have these everywhere or should they only appear in the Designer perspective? -- 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

15 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7381) Show extra page or some other proposal when externalization file not connected to page in ext dialog

by Maxim Areshkau (JIRA)

Show extra page or some other proposal when externalization file not connected to page in ext dialog ---------------------------------------------------------------------------------------------------- Key: JBIDE-7381 URL: https://jira.jboss.org/browse/JBIDE-7381 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.Beta1 Reporter: Maxim Areshkau Assignee: Denis Maliarevich Fix For: 3.2.0.Beta2 We connect ext properties file to page using following ways: #1 via faces-config globaly #2 via <f:loadbundle> for current page #3 via <ui:include> when we use facelets So in dialog we should warn user that resource not added to page and propose variants how it can be done. -- 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

15 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7094) No Mavenized project examples should appear in the JBDS project examples

by Brian Fitzpatrick (JIRA)

No Mavenized project examples should appear in the JBDS project examples ------------------------------------------------------------------------ Key: JBIDE-7094 URL: https://jira.jboss.org/browse/JBIDE-7094 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2.0.Beta Reporter: Brian Fitzpatrick Assignee: Snjezana Peco Priority: Critical Fix For: 3.2.x The RESTEasy example appears in JBDS as well as JBT, but should only appear in JBT because of the Maven aspect to it. We should remove it from JBDS along with any other examples that are Mavenized that appear in JBDS. If you let me know where the plug-in is that registers the project examples for JBDS, I can help with this. -- 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

15 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7217) Subtitle not found for keys in Hibernate Configuration Properties dialog

by Jiri Peterka (JIRA)

Subtitle not found for keys in Hibernate Configuration Properties dialog ------------------------------------------------------------------------ Key: JBIDE-7217 URL: https://jira.jboss.org/browse/JBIDE-7217 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.Beta1 Environment: JBT 3.2.0.beta-177, Linux 64 Reporter: Jiri Peterka Missing strings in Hibernate Configuration Properties dialog (see screenshot) -- 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

15 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7338) Lists in Hibernate Configuration Editor should have scrollbars

by Jiri Peterka (JIRA)

Lists in Hibernate Configuration Editor should have scrollbars -------------------------------------------------------------- Key: JBIDE-7338 URL: https://jira.jboss.org/browse/JBIDE-7338 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: JBDS 4.0.0.beta1 #47 Reporter: Jiri Peterka Fix For: 3.2.0.Beta1 Lists in Hibernate Configuration Editor aren't scrollable, instead that they are stretch (see screenshots). This is not user friendly (user has to scroll down to select and then scroll up to select button action). This could be improved. -- 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

15 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5826) Incorrect work of EL and CDI validator for action Validate

by Viacheslav Kabanovich (JIRA)

Incorrect work of EL and CDI validator for action Validate ---------------------------------------------------------- Key: JBIDE-5826 URL: https://jira.jboss.org/jira/browse/JBIDE-5826 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Viacheslav Kabanovich Assignee: Alexey Kazakov Fix For: 3.1.0.CR2 1. Switch off automatic build. 2. Create 2 seam projects. 3. Build them manually. 4. Open an xhtml of the first project. 5. Add some correct EL in it, and run Validate on that file. 6. Repeat that several times corrupting and fixing EL and running Validate to make sure that it is ok. 7. Open an xhtml of the second project. 8. Try to do the same as with the first xhtml. Make sure that action Validate does not work. 9. Return to the first xhtml. Make sure that action Validate works. It looks like action Validate works only for the project on which it was run first. -- 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

15 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6718) The import org.jboss.tools.cdi.text.ext.hyperlink.EventHyperlinkDetector cannot be resolved in org.jboss.tools.cdi.text.ext.test.EventHyperlinkDetectorTest.java

by Nick Boldt (JIRA)

The import org.jboss.tools.cdi.text.ext.hyperlink.EventHyperlinkDetector cannot be resolved in org.jboss.tools.cdi.text.ext.test.EventHyperlinkDetectorTest.java ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6718 URL: https://jira.jboss.org/browse/JBIDE-6718 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.M2 Reporter: Nick Boldt Assignee: Alexey Kazakov (default-compile) on project org.jboss.tools.cdi.text.ext.test: Compilation failure: Compilation failure: /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M2.continuous/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/src/org/jboss/tools/cdi/text/ext/test/EventHyperlinkDetectorTest.java (at line 6):[-1,-1] import org.jboss.tools.cdi.text.ext.hyperlink.EventHyperlinkDetector; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The import org.jboss.tools.cdi.text.ext.hyperlink.EventHyperlinkDetector cannot be resolved /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M2.continuous/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/src/org/jboss/tools/cdi/text/ext/test/EventHyperlinkDetectorTest.java (at line 26):[-1,-1] checkRegions("JavaSource/org/jboss/jsr299/tck/tests/event/bindingTypes/EventEmitter.java", regionList, new EventHyperlinkDetector()); ^^^^^^^^^^^^^^^^^^^^^^ EventHyperlinkDetector cannot be resolved to a type -- 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

15 years, 4 months

4
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2010