September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7012) Search runtimes gives no feedback to what it does/have done

by Max Andersen (JIRA)

Search runtimes gives no feedback to what it does/have done ----------------------------------------------------------- Key: JBIDE-7012 URL: https://jira.jboss.org/browse/JBIDE-7012 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.2.0.M2 Reporter: Max Andersen Assignee: Snjezana Peco Priority: Critical Fix For: 3.2.0.Beta I tried the "Search runtimes" and it asked me for a directory, I pointed to one with multiple runtimes in it press Ok and then it returned immediatly back to the preference page as if nothing had happened. Then I looked under the runtimes and it seem to have picked them all up - very impressive BUT as a new user I would have *no* idea what just happend. There shuold be some feedback to the user wether the search found anything or not, i.e. "The search found 4 runtimes while searching <thedir>." and then list their names. And similar if nothing were found say "The search found 0 runtimes while searching <thedir>." -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7038) Multiple redundant warning messages during defining seam runtime

by Jiri Peterka (JIRA)

Multiple redundant warning messages during defining seam runtime ---------------------------------------------------------------- Key: JBIDE-7038 URL: https://jira.jboss.org/browse/JBIDE-7038 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M2 Environment: JBT 3.2.0.v20100908-1606-H23-M2, Linux 64 Reporter: Jiri Peterka Steps: 1. Go through new Seam project wizard 2. In new Seam runtime definition dialog try to write a path manually by typing it ERROR: You will see multiple warning messages in your error log each time you write a letter. This infests Error log with similar useless messages. (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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7039) Wrong default seam name generation when specifying path manually

by Jiri Peterka (JIRA)

Wrong default seam name generation when specifying path manually ---------------------------------------------------------------- Key: JBIDE-7039 URL: https://jira.jboss.org/browse/JBIDE-7039 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M2 Environment: JBT 3.2.0.v20100908-1606-H23-M2, Linux 64 Reporter: Jiri Peterka Assignee: Alexey Kazakov Priority: Minor Attachments: new-seam-dlg.png Seam runtime definition dialog it creates default name according to last folder name in path if defined given by using Browse button or if it's written at once. But when writing char by char, it gives first written alphanumerical char and nothing more. It should be little bit more clever. I mean if should pre-define name only if seam folder is reached. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1245) Include updated Eclipse 3.6.1 (Helios+SP1)

by Max Rydahl Andersen (JIRA)

Include updated Eclipse 3.6.1 (Helios+SP1) ------------------------------------------- Key: JBDS-1245 URL: https://jira.jboss.org/browse/JBDS-1245 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Reporter: Max Rydahl Andersen How about other 3rd party dependencies ? TestNG/SpringIDE/others ? -- 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, 6 months

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-6997) Hibernate Ant CodeGem: preferBasicCompositeIds for jdbcconfiguration should not get into the generated file

by Vitali Yemialyanchyk (JIRA)

Hibernate Ant CodeGem: preferBasicCompositeIds for jdbcconfiguration should not get into the generated file ----------------------------------------------------------------------------------------------------------- Key: JBIDE-6997 URL: https://jira.jboss.org/browse/JBIDE-6997 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.2.0.Beta if this flag is true -> preferBasicCompositeIds should not be added as attribute to jdbcconfiguration (now it is), but should be warning message about this in Export wizard: The script can not be generated correctly with "Generate basic typed composite ids" flag set. links to initial forum discussions: https://forum.hibernate.org/viewtopic.php?f=6&t=964081&start=0 https://forum.hibernate.org/viewtopic.php?f=6&t=1006353&start=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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7083) New Seam Project Wizard - defining custom EAR subproject names do not work

by Dominik Pospisil (JIRA)

New Seam Project Wizard - defining custom EAR subproject names do not work -------------------------------------------------------------------------- Key: JBIDE-7083 URL: https://jira.jboss.org/browse/JBIDE-7083 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M2 Reporter: Dominik Pospisil Assignee: Alexey Kazakov On New Seam Project wizard - Seam Facet page there is an option to specify custom EJB, EAR and Test project names. However, after modifyng that names and pressing finish, those names are reverted to the default values. Steps to reproduce: 1) File -> New Seam Project 2) Choose a Project name, 4x press next 3) Modify EJB, EAR or Test project names 4) Press finish -- 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, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6504) Exceptions in modeshape when deleting a project

by Rob Stryker (JIRA)

Exceptions in modeshape when deleting a project ----------------------------------------------- Key: JBIDE-6504 URL: https://jira.jboss.org/browse/JBIDE-6504 Project: Tools (JBoss Tools) Issue Type: Bug Components: modeshape Reporter: Rob Stryker This is the exception. It seems when resources are being deleted, the IFiles are still being checked even though they don't exist. !ENTRY org.jboss.tools.modeshape.rest 4 0 2010-06-21 16:48:45.776 !MESSAGE Error obtaining the "published" property from the resource "L/JP5/.classpath" !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/JP5/.classpath' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:326) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:200) at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:206) at org.eclipse.core.internal.resources.Resource.getPersistentProperty(Resource.java:1178) at org.jboss.tools.modeshape.rest.PublishedResourceHelper.getPublishedOnWorkspaces(PublishedResourceHelper.java:134) at org.jboss.tools.modeshape.rest.PublishedResourceHelper.isPublished(PublishedResourceHelper.java:193) at org.jboss.tools.modeshape.rest.views.ModeShapeContentProvider.decorate(ModeShapeContentProvider.java:147) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 org.eclipse.core.resources 4 368 2010-06-21 16:48:45.778 !MESSAGE Resource '/JP5/.classpath' does not exist. -- 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, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6854) NPE in SourceGenericGeneratorsAnnotation

by Dmitry Geraskov (JIRA)

NPE in SourceGenericGeneratorsAnnotation ---------------------------------------- Key: JBIDE-6854 URL: https://jira.jboss.org/browse/JBIDE-6854 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.2.0.M2 Exception occured for code: @GenericGenerators(@GenericGenerator{name = "gg", strategy = "v"}) java.lang.NullPointerException at org.jboss.tools.hibernate.jpt.core.internal.resource.java.SourceGenericGeneratorsAnnotation.syncAddNestedAnnotation(SourceGenericGeneratorsAnnotation.java:98) at org.eclipse.jpt.core.internal.resource.java.source.AnnotationContainerTools.synchronize(AnnotationContainerTools.java:257) at org.jboss.tools.hibernate.jpt.core.internal.resource.java.SourceGenericGeneratorsAnnotation.synchronizeWith(SourceGenericGeneratorsAnnotation.java:55) at org.eclipse.jpt.core.internal.resource.java.source.SourcePersistentMember.addOrSyncAnnotation_(SourcePersistentMember.java:349) at org.eclipse.jpt.core.internal.resource.java.source.SourcePersistentMember.addOrSyncAnnotation(SourcePersistentMember.java:339) at org.eclipse.jpt.core.internal.resource.java.source.SourcePersistentType.addOrSyncAnnotation(SourcePersistentType.java:210) at org.eclipse.jpt.core.internal.resource.java.source.SourcePersistentMember.addOrSyncAnnotation(SourcePersistentMember.java:330) -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6909) org.jboss.tools.hibernate.ui.test/HibernateUiTestSuite/testAction/ :: java.lang.NoSuchMethodError: org.eclipse.swt.widgets.Display.internal_new_GC(Lorg/eclipse/swt/graphics/GCData; )I

by Nick Boldt (JIRA)

org.jboss.tools.hibernate.ui.test/HibernateUiTestSuite/testAction/ :: java.lang.NoSuchMethodError: org.eclipse.swt.widgets.Display.internal_new_GC(Lorg/eclipse/swt/graphics/GCData;)I -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6909 URL: https://jira.jboss.org/browse/JBIDE-6909 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.M2, 3.2.0.Beta Reporter: Nick Boldt Assignee: Max Rydahl Andersen Priority: Minor http://hudson.qa.jboss.com/hudson/view/DevStudio_Tycho/job/jbosstools-3.2... Error Message org.eclipse.swt.widgets.Display.internal_new_GC(Lorg/eclipse/swt/graphics/GCData;)I Stacktrace java.lang.NoSuchMethodError: org.eclipse.swt.widgets.Display.internal_new_GC(Lorg/eclipse/swt/graphics/GCData;)I at org.jboss.tools.hibernate.ui.diagram.editors.actions.test.ExportImageActionTest$2.<init>(ExportImageActionTest.java:110) at org.jboss.tools.hibernate.ui.diagram.editors.actions.test.ExportImageActionTest.testAction(ExportImageActionTest.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) 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.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:25) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3527) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27) 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:369) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- 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, 6 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6931) Hibernate Valiodation is very slow

by Denis Golovin (JIRA)

Hibernate Valiodation is very slow ---------------------------------- Key: JBIDE-6931 URL: https://jira.jboss.org/browse/JBIDE-6931 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Priority: Blocker Fix For: 3.2.0.Beta -- 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, 6 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 September 2010