January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7876) Problem with deploying JDBC driver to JBoss AS 6

by Snjezana Peco (JIRA)

Problem with deploying JDBC driver to JBoss AS 6 ------------------------------------------------ Key: JBIDE-7876 URL: https://issues.jboss.org/browse/JBIDE-7876 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS, UpStream Affects Versions: 3.2.0.Beta2 Reporter: Snjezana Peco Assignee: Rob Stryker The New Seam Web project wizard copies the JDBC driver to the server/lib directory. JBoss AS 6 doesn't load libraries from this directory. It loads them from server/<configuration_name>/lib. This is probably a problem in JBoss AS 6. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8071) External process for hibernate code generation cannot work with 3.2-3.5 and 3.6 at the same time

by Max Andersen (JIRA)

External process for hibernate code generation cannot work with 3.2-3.5 and 3.6 at the same time ------------------------------------------------------------------------------------------------ Key: JBIDE-8071 URL: https://issues.jboss.org/browse/JBIDE-8071 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Max Andersen Assignee: Max Andersen Priority: Critical Fix For: 3.3.x If you compile Hibernate Tools against 3.5 it cant run on 3.6; and if you compile against 3.6 it can't run on 3.5 (even though the code is source compatible) Since we want to support Hibernate JPA 2 we need to upgrade to 3.6 but then we cannot at the same time provide the "external process for hibernate code generation" since that will almost always collide with users classpath and thus you get errors like: java.lang.IncompatibleClassChangeError: Found class org.hibernate.cfg.Mappings, but interface was expected Because the interface Mappings in 3.6 is a class in 3.5 and previous versions. I don't know a good way to work around this thus for now we will have rollback JBIDE-6423 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7790) the selected cloud, that gets store to preferences, mixes up between Image- and Iage-View

by Andre Dietisheim (JIRA)

the selected cloud, that gets store to preferences, mixes up between Image- and Iage-View ----------------------------------------------------------------------------------------- Key: JBIDE-7790 URL: https://jira.jboss.org/browse/JBIDE-7790 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7789) image View: has exception while it is being created if you have invalid cloud connection selected on startup

by Andre Dietisheim (JIRA)

image View: has exception while it is being created if you have invalid cloud connection selected on startup ------------------------------------------------------------------------------------------------------------ Key: JBIDE-7789 URL: https://jira.jboss.org/browse/JBIDE-7789 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7934) Eclipse hogged when working on a fresh EAR project

by Miroslav Pavleski (JIRA)

Eclipse hogged when working on a fresh EAR project -------------------------------------------------- Key: JBIDE-7934 URL: https://issues.jboss.org/browse/JBIDE-7934 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299), JBossAS Affects Versions: 3.2.0.Beta2 Environment: Windows Vista 32 bit Eclipse Helios SR1 JBoss Tools 3.2 Beta 2 Reporter: Miroslav Pavleski Assignee: Alexey Kazakov Once a new project is created and CDI enabled property set on sub-projects everything stops to a crawl and the whole eclipse becomes too slow. The issue is manifesting itself with CDI validation off. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7780) name of tree elements is handled by parent instead of element itself

by Andre Dietisheim (JIRA)

name of tree elements is handled by parent instead of element itself -------------------------------------------------------------------- Key: JBIDE-7780 URL: https://jira.jboss.org/browse/JBIDE-7780 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 The current implementation of the CloudViewElement - the elements that are displayed in the cloud viewer tree - do not have their own implementation that returns their name. Their name is set by their parent. This is bad towards separation of concern and code readability/understandability. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7779) Cloud view: labels for instances are the image id

by Andre Dietisheim (JIRA)

Cloud view: labels for instances are the image id ------------------------------------------------- Key: JBIDE-7779 URL: https://jira.jboss.org/browse/JBIDE-7779 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 the cloud viewer displays the name it gets for an instance. unfortunately Deltacloud reports the image id as name for an instance. We need a workaround for this since instances cannot be distinguised in the cloud view if they were launched from the same image -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7774) NewConnectionWizard should remember hte last used deltacloud url

by Rob Stryker (JIRA)

NewConnectionWizard should remember hte last used deltacloud url ---------------------------------------------------------------- Key: JBIDE-7774 URL: https://jira.jboss.org/browse/JBIDE-7774 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.CR1 title says it all -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7769) launch instance wizard takes 10 seconds to load

by Rob Stryker (JIRA)

launch instance wizard takes 10 seconds to load ----------------------------------------------- Key: JBIDE-7769 URL: https://jira.jboss.org/browse/JBIDE-7769 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.CR1 Opening the "Launch Instance" wizard takes 10 seconds because it executes two remote commands in the UI thread. First it fetches hte profiles, then it fetches hte realms. This should be delayed out as much as possible. Combos should be created with only one item saying "Loading..." and combo should be disabled. Fetching commands should be launched in another thread, and, upon completion, update the combo with either the proper items or a none-available string. Updates should be done in UI thread of course. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7874) ESB tests fail when run outside all-in-one collection of tests

by Nick Boldt (JIRA)

ESB tests fail when run outside all-in-one collection of tests -------------------------------------------------------------- Key: JBIDE-7874 URL: https://issues.jboss.org/browse/JBIDE-7874 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Brian Fitzpatrick I've created a new ESB-only build job [0]. [0] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_trunk.component--esb/ Unfortunately, it's not passing all its tests (unlike when run in the all-in-one job) [1]. [1] http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2... Here's a snippet of the errors [2]. [2] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_trunk.component--esb... Running org.jboss.tools.esb.project.core.test.ESBProjectAllTests [ResourceUtils]:Target Import Location: /esbTestProject [ResourceUtils]:Full path to source: /qa/hudson_ws/workspace/jbosstools-3.2_trunk.component--esb/sources/tests/org.jboss.tools.esb.project.core.test/projects/esbTestProject/ [ResourceUtils]:Protocol: file [Fatal Error] :1:1: Premature end of file. [Fatal Error] :1:1: Premature end of file. [ResourceUtils]:Target Import Location: /esbTestProject_2 [ResourceUtils]:Full path to source: /qa/hudson_ws/workspace/jbosstools-3.2_trunk.component--esb/sources/tests/org.jboss.tools.esb.project.core.test/projects/esbTestProject_2/ [ResourceUtils]:Protocol: file [Fatal Error] :1:1: Premature end of file. Tests run: 7, Failures: 6, Errors: 0, Skipped: 0, Time elapsed: 12.279 sec <<< FAILURE! testUserCustomizedESBRuntime(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 8.246 sec <<< FAILURE! junit.framework.AssertionFailedError: unalbe to read User customized ESB runtime, jbossesb-rosetta.jar is not in classpath. expected:<true> but was:<false> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:143) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testUserCustomizedESBRuntime(ESBProjectDeploymentTest.java:233) testSOAP50Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.008 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testSOAP50Deployment(ESBProjectDeploymentTest.java:238) testSOAP43Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.008 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testSOAP43Deployment(ESBProjectDeploymentTest.java:243) testJBossServer50Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.008 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testJBossServer50Deployment(ESBProjectDeploymentTest.java:248) testJbossServer51Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.017 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testJbossServer51Deployment(ESBProjectDeploymentTest.java:253) testJbossServer42Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.012 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testJbossServer42Deployment(ESBProjectDeploymentTest.java:258) Results : Failed tests: testUserCustomizedESBRuntime(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testSOAP50Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testSOAP43Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testJBossServer50Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testJbossServer51Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testJbossServer42Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Tests run: 7, Failures: 6, Errors: 0, Skipped: 0 [INFO] org.jboss.tools.esb.project.core .................. SUCCESS [51.084s] [INFO] org.jboss.tools.esb.core .......................... SUCCESS [4.492s] [INFO] org.jboss.tools.esb.ui ............................ SUCCESS [3.644s] [INFO] org.jboss.tools.esb.project.ui .................... SUCCESS [4.373s] [INFO] org.jboss.tools.esb.validator ..................... SUCCESS [6.520s] [INFO] org.jboss.tools.esb.feature ....................... SUCCESS [2.651s] [INFO] org.jboss.tools.esb.core.test ..................... SUCCESS [1:41.159s] [INFO] org.jboss.tools.esb.project.core.test ............. FAILURE [54.543s] [INFO] org.jboss.tools.esb.validator.test ................ SUCCESS [28.226s] [INFO] org.jboss.tools.esb.test.feature .................. SKIPPED [INFO] esb.features ...................................... SUCCESS [0.065s] [INFO] esb.plugins ....................................... SUCCESS [0.006s] [INFO] esb.tests ......................................... SUCCESS [0.006s] [INFO] esb.site .......................................... SUCCESS [4.788s] [INFO] esb.all ........................................... SUCCESS [0.005s] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
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 January 2011