January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10410) NullPointerException when closing a project where JAX-RS support is enabled

by Xavier Coulon (Created) (JIRA)

NullPointerException when closing a project where JAX-RS support is enabled --------------------------------------------------------------------------- Key: JBIDE-10410 URL: https://issues.jboss.org/browse/JBIDE-10410 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon for further investigation, here's the stacktrace I get: {code} !STACK 0 java.lang.NullPointerException at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.resourceChanged(JavaElementChangedListener.java:36) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) {code} -- 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

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBIDE-10586) Method CDICoreNature.getDelegate() returns null for dependent project just after restarting the JBDS

by Daniel Azarov (Created) (JIRA)

Method CDICoreNature.getDelegate() returns null for dependent project just after restarting the JBDS ----------------------------------------------------------------------------------------------------- Key: JBIDE-10586 URL: https://issues.jboss.org/browse/JBIDE-10586 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.Beta1 Reporter: Daniel Azarov Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 EXECUTE: Create two CDI projects: ProjectA and ProjectB. ProjectB depends on ProjectA. EXECUTE: Create a bean in ProjectA: {code} @Named("cdiBean") public class CDIBeanTest { } {code} EXECUTE: Create another bean in ProjectB: {code} public class TestBean { @Inject @Named("cdiBean") Object foo; } {code} EXECUTE: Restart the JBDS EXECUTE: Select CDIBeanTest class name in CDIBeanTest.java and press Ctrl+Shift+G FAIL: There is no search results CDIBeanQueryParticipant called method cdiProject.getNature().getAllDependentProjects() for ProjectA and got CDICoreNature related with ProjectB but CDICoreNature.getDelegate() returned null -- 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

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9725) EAP 6 Alpha 1 is recognized as AS 7

by Max Rydahl Andersen (JIRA)

EAP 6 Alpha 1 is recognized as AS 7 ----------------------------------- Key: JBIDE-9725 URL: https://issues.jboss.org/browse/JBIDE-9725 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers, runtime detection Affects Versions: 3.3.0.M3 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.3.0.M4 runtime detection detects EAP 6 alpha as an AS 7 runtime. Need to contact EAP team to ensure we are detecting on the right thing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
5
0 / 0

[JBoss JIRA] (JBIDE-10609) Hook up WS Tester to the JAX-RS tooling

by Brian Fitzpatrick (Created) (JIRA)

Hook up WS Tester to the JAX-RS tooling --------------------------------------- Key: JBIDE-10609 URL: https://issues.jboss.org/browse/JBIDE-10609 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.3.0.M5 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta1 Two different presentations today proved that there need to be more integration points to simplify access to the JBoss WS Tester. Currently in Eclipse with WTP installed, if you right-click on a WSDL file, you see "web services->test with web services explorer" We need to do the same thing for the JBT WS tester. -- 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

14 years, 1 month

6
12
0 / 0

[JBoss JIRA] (JBIDE-10522) No provider name for some hibernate plugins

by Jaroslav Jankovič (Created) (JIRA)

No provider name for some hibernate plugins ------------------------------------------- Key: JBIDE-10522 URL: https://issues.jboss.org/browse/JBIDE-10522 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M5 Reporter: Jaroslav Jankovič Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 Attachments: hibernatePlugins.png There is no provider name for following hibernate plugins: HibernateExtension3_5, HibernateExtension4_0 -- 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

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBIDE-10636) Add the code which is supposed to be inserted by the Quick Fix into its description

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-10636: -------------------------------------- Summary: Add the code which is supposed to be inserted by the Quick Fix into its description Key: JBIDE-10636 URL: https://issues.jboss.org/browse/JBIDE-10636 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: CDI Affects Versions: 3.4.x Reporter: Alexey Kazakov Assignee: Daniel Azarov -- 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

14 years, 1 month

4
8
0 / 0

[JBoss JIRA] (JBIDE-10503) Code generation fails when Hibernate 4 with reveng.xml file is used

by Jiri Peterka (Created) (JIRA)

Code generation fails when Hibernate 4 with reveng.xml file is used ------------------------------------------------------------------- Key: JBIDE-10503 URL: https://issues.jboss.org/browse/JBIDE-10503 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M5 Environment: JBDS 5.0.0.M5a, H62, L64 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 Code generation fails when Hibernate 4.0 and reveng.xml file is used Steps to reproduce: 1. Create Java project 2. Create Hibernate Configuration (version 4.0), add HSQLDB 1.8 driver 3. Create configuration, connect to HSQL database 5. Create reverse engineer (reveng.xml) file (can be empty) 4. Create Hibernate Code Generation Configuration, use Domain code exporter, reverse engineer from JDBC connection ERROR: errors and code is not generated java.lang.ClassNotFoundException: net.sf.cglib.core.KeyFactory at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.hibernate.cfg.reveng.OverrideRepository.<clinit>(OverrideRepository.java:588) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0$3.execute(ConsoleExtension4_0.java:234) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.jboss.tools.hibernate4_0.HibernateExtension4_0.execute(HibernateExtension4_0.java:248) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.buildConfiguration(ConsoleExtension4_0.java:224) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.runExporters(ConsoleExtension4_0.java:154) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.launchExporters(ConsoleExtension4_0.java:118) at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:268) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) HSQLDB 1.8, Server is used, works good with hibernate console 3.5 DB data: http://anonsvn.jboss.org/repos/jbosstools/trunk/hibernatetools/tests/org.... -- 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

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBIDE-10752) org.jboss.tools.seam.xml.test.SeamXMLModelTest failure

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-10752: -------------------------------------- Summary: org.jboss.tools.seam.xml.test.SeamXMLModelTest failure Key: JBIDE-10752 URL: https://issues.jboss.org/browse/JBIDE-10752 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 {code} Running org.jboss.tools.seam.xml.test.SeamXMLAllTests Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.647 sec <<< FAILURE! testDebugAttribute(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.507 sec <<< FAILURE! junit.framework.AssertionFailedError: Validator failed to report an error in component org.jboss.seam.core.init1 at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute(SeamXMLModelTest.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:72) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) Results : Failed tests: testDebugAttribute(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Tests run: 5, Failures: 1, Errors: 0, Skipped: 0 {code} -- 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

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] (JBIDE-10753) org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest failure

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-10753: -------------------------------------- Summary: org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest failure Key: JBIDE-10753 URL: https://issues.jboss.org/browse/JBIDE-10753 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 {code} Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 484.333 sec <<< FAILURE! testSettingsPage(org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest) Time elapsed: 0.004 sec <<< FAILURE! junit.framework.AssertionFailedError: TestSeamSettingsPreferencesPage project is not imported. at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest.setUp(SeamSettingsPreferencesPageTest.java:72) {code} -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (JBIDE-10732) org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest failure

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-10732: -------------------------------------- Summary: org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest failure Key: JBIDE-10732 URL: https://issues.jboss.org/browse/JBIDE-10732 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 {code} testSettingsPage(org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest) Time elapsed: 0 sec <<< FAILURE! junit.framework.AssertionFailedError: TestSeamSettingsPreferencesPage project is not imported. at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest.setUp(SeamSettingsPreferencesPageTest.java:72) {code} -- 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

14 years, 1 month

3
2
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 2012