December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1467) NoSuchMethodError Trying to explore a DB from Hibernate Configurations

by Angus Mezick (JIRA)

NoSuchMethodError Trying to explore a DB from Hibernate Configurations ---------------------------------------------------------------------- Key: JBDS-1467 URL: https://issues.jboss.org/browse/JBDS-1467 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Angus Mezick Priority: Critical What steps will reproduce the problem? 1. Create a new hibernate configuration 2. Use the "Hibernate Configurations" view to explore the database 3. Notice the error popup. -- Error Details -- Date: Wed Dec 22 12:47:27 EST 2010 Message: An internal error occurred during: "Fetching children of Database". Severity: Error Product: Eclipse 1.3.1.20100913-1228 (org.eclipse.epp.package.jee.product) Plugin: org.eclipse.core.jobs Session Data: eclipse.buildId=M20100909-0800 java.version=1.6.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product Exception Stack Trace: java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

4
16
0 / 0

[JBoss JIRA] Updated: (JBIDE-7990) Display properties for Configuration node for Hibernate Console Configuration

by Vitali Yemialyanchyk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7990?page=com.atlassian.jira.plugin... ] Vitali Yemialyanchyk updated JBIDE-7990: ---------------------------------------- Attachment: screenshot-1.jpg screenshot-1 - current look > Display properties for Configuration node for Hibernate Console Configuration > ----------------------------------------------------------------------------- > > Key: JBIDE-7990 > URL: https://issues.jboss.org/browse/JBIDE-7990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Affects Versions: 3.2.0.Beta2 > Reporter: Vitali Yemialyanchyk > Assignee: Vitali Yemialyanchyk > Priority: Minor > Labels: new_and_noteworthy > Attachments: screenshot-1.jpg > > > currently for this node Properties View is empty - should display properties of Configuration. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-1468) Cannot export Teiid data model to Oracle DDL in JBDS beta2

by Len DiMaggio (JIRA)

Cannot export Teiid data model to Oracle DDL in JBDS beta2 ---------------------------------------------------------- Key: JBDS-1468 URL: https://issues.jboss.org/browse/JBDS-1468 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: SOA Platform Reporter: Len DiMaggio Priority: Blocker See SOA-P JIRA: https://issues.jboss.org/browse/SOA-2719 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-1230) JBoss Developer 3.0 Installing in a a newly installed RHEL 5.4 does not show up in the applications menu

by Jim Tyrrell (JIRA)

JBoss Developer 3.0 Installing in a a newly installed RHEL 5.4 does not show up in the applications menu -------------------------------------------------------------------------------------------------------- Key: JBDS-1230 URL: https://jira.jboss.org/browse/JBDS-1230 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 3.0.0.GA Environment: RHEL 5.4 with Sun JDK 5.4 Reporter: Jim Tyrrell When going through the installer on a clean RHEL 5.4 system, the Programming Tools Listing under the Applications in the main menu bar does not show up until a reboot. Once it has been installed at least once, this does not seem to be a problem -- 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, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBDS-1441) Product builds result in smaller executables than Uber builds -- verify this is correct

by Nick Boldt (JIRA)

Product builds result in smaller executables than Uber builds -- verify this is correct --------------------------------------------------------------------------------------- Key: JBDS-1441 URL: https://jira.jboss.org/browse/JBDS-1441 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build, installer Affects Versions: 4.0.0.Beta2 Reporter: Nick Boldt Assignee: Denis Golovin Fix For: 4.0.0.CR1 Latest Beta2 product build: http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4.... jbdevstudio-win32-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 330.21 MB jbdevstudio-linux-gtk-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 330.16 MB jbdevstudio-linux-gtk-x86_64-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 334.26 MB jbdevstudio-macosx-carbon-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 332.93 MB jbdevstudio-macosx-cocoa-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 333.05 MB jbdevstudio-eap-win32-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 622.68 MB jbdevstudio-eap-linux-gtk-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 622.7 MB jbdevstudio-eap-linux-gtk-x86_64-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 626.74 MB jbdevstudio-eap-macosx-carbon-4.0.0.v201012030614R-H32-Beta2.jar md5 | filesize: 625.46 MB jbdevstudio-eap-macosx-cocoa-4.0.0.v201012030614R-H32-Beta2.jar Latest Beta 2 uber build: http://reports.qa.atl.jboss.com/binaries/RHDS/builds/nightly/4.0.0.Beta2/... jbdevstudio-win32-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 416.05 MB jbdevstudio-linux-gtk-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 415.75 MB jbdevstudio-linux-gtk-x86_64-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 419.87 MB jbdevstudio-macosx-carbon-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 418.31 MB jbdevstudio-macosx-cocoa-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 418.54 MB jbdevstudio-eap-win32-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 708.61 MB jbdevstudio-eap-linux-gtk-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 708.33 MB jbdevstudio-eap-linux-gtk-x86_64-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 712.35 MB jbdevstudio-eap-macosx-carbon-4.0.0.v201012030520R-H26-Beta2.jar md5 | filesize: 710.81 MB jbdevstudio-eap-macosx-cocoa-4.0.0.v201012030520R-H26-Beta2.jar So, why is the product build 330-334M and 622-626M, while the uber build is 415-419M and 708-712M ? is this difference the loss of things we don't need in the TP, or loss of things we SHOULD have in there? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Updated: (JBIDE-7988) CDI tools model is not updated after quick fix.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7988?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-7988: ---------------------------------- Priority: Critical (was: Major) > CDI tools model is not updated after quick fix. > ----------------------------------------------- > > Key: JBIDE-7988 > URL: https://issues.jboss.org/browse/JBIDE-7988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi (jsr-299) > Affects Versions: 3.2.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 3.2.0.CR1 > > > 1. Create the following class in CDI-enabled project: > class Goose_Broken { > @Inject > public Goose_Broken(String foo) {} > @Inject > public Goose_Broken(String foo, Double bar) {} > } > 2. Build the project. There is two error markers on the injections because a bean can have only one constructor annotated @Inject. > 3. Double click on any error marker. Select "Delete @Inject annotation from all the constructors but....". Press finish. > 4. Now there is the only one @Inject in the class but error markers didn't disappear. It's a problem of CDI model. It still has two @Inject methods. Try to modify the file and Ctrl+S. It helps to get rid of the markers. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-7986) Instance view: is not cleared if last cloud is removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7986?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-7986. ------------------------------------- Resolution: Done I resolved this when fixing JBIDE-7959 > Instance view: is not cleared if last cloud is removed > ------------------------------------------------------ > > Key: JBIDE-7986 > URL: https://issues.jboss.org/browse/JBIDE-7986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: deltacloud > Affects Versions: 3.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 3.2.0.CR1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7858) Teiid artifacts should respond more gracefully to Teiid project refactoring

by Brian Fitzpatrick (JIRA)

Teiid artifacts should respond more gracefully to Teiid project refactoring --------------------------------------------------------------------------- Key: JBIDE-7858 URL: https://issues.jboss.org/browse/JBIDE-7858 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.M2 Environment: RHEL, JBDS jbdevstudio-linux-gtk-4.0.0.v201012070137R-H33-Beta2.jar, SOA-P 5.1 ER5, Teiid 7.2 Reporter: Brian Fitzpatrick Assignee: Barry LaFond Priority: Critical While I was trying to figure things out with the Virtual Procedures test script, I received a newer copy of the Parts Project from Barry that included the data files for loading the database tables. As a result, I wanted to change the name of the Teiid Model Project that I had created for the test. Though the Teiid Designer Perspective (via the Model Explorer view) doesn't allow you to rename a project, I popped over to a different perspective (the Java EE Perspective) and renamed the project there. I was then able to import Barry's project and take a look. Well, I didn't realize that the VDB file (and potentially others) was hardwired to the project name as part of the path to the .xmi files. So that threw me into several problems I had to resolve. Eventually I did resolve them, but we need to provide some sort of refactoring capabilities for Teiid projects and respond to those changes more gracefully. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Updated: (JBIDE-7980) Launch instance wizard: launching instance from an existing image: image is not found

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7980?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7980: ------------------------------------ Fix Version/s: 3.2.0.CR1 Affects Version/s: 3.2.0.CR1 Component/s: deltacloud > Launch instance wizard: launching instance from an existing image: image is not found > ------------------------------------------------------------------------------------- > > Key: JBIDE-7980 > URL: https://issues.jboss.org/browse/JBIDE-7980 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: deltacloud > Affects Versions: 3.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 3.2.0.CR1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7976) content-type application/x-www-form-urlencoded : incorrect form parameter handling

by Juergen Zimmermann (JIRA)

content-type application/x-www-form-urlencoded : incorrect form parameter handling ---------------------------------------------------------------------------------- Key: JBIDE-7976 URL: https://issues.jboss.org/browse/JBIDE-7976 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.Beta2 Reporter: Juergen Zimmermann Assignee: Brian Fitzpatrick When I submit a POST request with "Web Services Tester", then the form parameters get corrupted as follows: a) In the "Request Header" section I insert: content-type=application/x-www-form-urlencoded b) In the "Request Body" section I insert e.g.: param_1=value_1 param_2=value_2 c) At the server side I receive just *1* form parameter, namely "param_1" having the value "value_1param_2=value_2". I also tried to separate the enumeration in the "Request Body" section by a comma ",". Then the comma is just part of the concatenated string value. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
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 December 2010