December 2011 - jbosstools-issues

[JBoss JIRA] (JBIDE-10502) Could not embed cartridges to application

by Pavol Srna (Created) (JIRA)

Could not embed cartridges to application ----------------------------------------- Key: JBIDE-10502 URL: https://issues.jboss.org/browse/JBIDE-10502 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Environment: jbdevstudio-product-linux-gtk-5.0.0.v201112150534M-H62-M5.jar Reporter: Pavol Srna Assignee: Andre Dietisheim Fix For: 3.3.0.M5 Attachments: stack.txt See attached stack trace. -- 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

9
20
0 / 0

[JBoss JIRA] Created: (JBDS-856) Mac OSX Snow Leopard: Server cannot be saved for the following reasons: One or more ports have an invalid value

by Robert Morse (JIRA)

Mac OSX Snow Leopard: Server cannot be saved for the following reasons: One or more ports have an invalid value ---------------------------------------------------------------------------------------------------------------- Key: JBDS-856 URL: https://jira.jboss.org/jira/browse/JBDS-856 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Mac OS X 10.6 (Snow Leopard) JBoss AS 5.1.0.GA JDK 1.6 Reporter: Robert Morse When trying to create a new JBoss AS server, JBDS complains with: The server cannot be saved for the following reasons: One or more ports have an invalid value. This may adversely affect the tooling's ability to interact with the server. I've never seen this error before, and I'm not sure what the port values should be. Currently, the Automatically detect check boxes are checked -- 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

14 years, 1 month

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-8412) Layout for advanced properties tab is broken in for Choreography flow selected in Choreography Description Editor

by Denis Golovin (JIRA)

Layout for advanced properties tab is broken in for Choreography flow selected in Choreography Description Editor ----------------------------------------------------------------------------------------------------------------- Key: JBIDE-8412 URL: https://issues.jboss.org/browse/JBIDE-8412 Project: Tools (JBoss Tools) Issue Type: Bug Components: pi4soa Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Attachments: screenshot125.png !screenshot125.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

9
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8410) java.lang.ClassCastException: org.pi4soa.cdl.impl.SilentActionImpl cannot be cast to org.pi4soa.cdl.Assign in Choreography Description Editor

by Denis Golovin (JIRA)

java.lang.ClassCastException: org.pi4soa.cdl.impl.SilentActionImpl cannot be cast to org.pi4soa.cdl.Assign in Choreography Description Editor --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8410 URL: https://issues.jboss.org/browse/JBIDE-8410 Project: Tools (JBoss Tools) Issue Type: Bug Components: pi4soa Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Now it reports "Unhandled event loop exception" in error log view with exception: {noformat}java.lang.ClassCastException: org.pi4soa.cdl.impl.SilentActionImpl cannot be cast to org.pi4soa.cdl.Assign at org.pi4soa.designer.editor.properties.AssignParticipantPropertySection.getAssign(AssignParticipantPropertySection.java:49) at org.pi4soa.designer.editor.properties.AssignParticipantPropertySection.handleNew(AssignParticipantPropertySection.java:55) at org.pi4soa.designer.editor.properties.DefaultComboPropertySection$2.widgetSelected(DefaultComboPropertySection.java:164) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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: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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

9
13
0 / 0

[JBoss JIRA] Created: (JBIDE-9559) Schema Generation From DDlWizard doesn't reflect changes in the classes

by Elhanan Maayan (JIRA)

Schema Generation From DDlWizard doesn't reflect changes in the classes ----------------------------------------------------------------------- Key: JBIDE-9559 URL: https://issues.jboss.org/browse/JBIDE-9559 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.x Reporter: Elhanan Maayan Assignee: Max Rydahl Andersen when generating a schema from generate tables from entities, the file is only generated once,. if i change anything in the classes (like table name,columns etc..) attempting to generate again, will not change the file only restarting eclipse will do so. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

12
21
0 / 0

[JBoss JIRA] Created: (JBDS-1733) JBDS50_0060: [COMMIT] (Dev) Forge

by mark yarborough (JIRA)

JBDS50_0060: [COMMIT] (Dev) Forge --------------------------------- Key: JBDS-1733 URL: https://issues.jboss.org/browse/JBDS-1733 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9709) osgi deployments fails

by Max Rydahl Andersen (JIRA)

osgi deployments fails ---------------------- Key: JBIDE-9709 URL: https://issues.jboss.org/browse/JBIDE-9709 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Reporter: Vlado Pakan Assignee: Rob Stryker Fix For: 3.3.0.M4 while testing JBIDE-9206: Deployment works for war deployments, but fails for OSGI deployments temporary dir gets created This is what server says: 16:40:06,375 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "testnull" 16:40:06,375 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit.testnull.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.testnull.STRUCTURE: Failed to process phase STRUCTURE of deployment "testnull" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to mount deployment content at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:82) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more Caused by: java.io.IOException: Could not create directory for original name 'testnull' after 10 attempts at org.jboss.vfs.TempFileProvider.createTempDir(TempFileProvider.java:103) at org.jboss.vfs.VFS.mountZip(VFS.java:406) at org.jboss.vfs.VFS.mountZip(VFS.java:434) at org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:75) at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:78) ... 6 more 16:40:06,377 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployment of "testnull" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.testnull.STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.testnull.STRUCTURE: Failed to process phase STRUCTURE of deployment \"testnull\""}} 16:40:06,378 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment testnull in 0ms 16:40:06,379 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.unit.testnull.STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.testnull.STRUCTURE: Failed to process phase STRUCTURE of deployment \"testnull\""}}}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
4
0 / 0

[JBoss JIRA] (JBIDE-10191) System properties are ignored

by Andre Dietisheim (Created) (JIRA)

System properties are ignored ----------------------------- Key: JBIDE-10191 URL: https://issues.jboss.org/browse/JBIDE-10191 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- 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] (JBDS-1982) Uninstaller demands administrator login on windows even if it was installed by regular user

by Radim Hopp (Created) (JIRA)

Uninstaller demands administrator login on windows even if it was installed by regular user ------------------------------------------------------------------------------------------- Key: JBDS-1982 URL: https://issues.jboss.org/browse/JBDS-1982 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.M5 Environment: Windows 7 Reporter: Radim Hopp Priority: Critical Fix For: 5.0.0.M5 When trying to uninstall JBDS using uninstaller, user is prompted for administrator password with message "Do you want to allow the following program to make changes to this computer?" Program location "\\path\to\javaw.exe" "-Dizpack.mode=privileged" "-jar" "\\path\to\Uninstaller.jar" Without admin rights, the uninstaller won't execute. -- 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

13
21
0 / 0

[JBoss JIRA] (JBIDE-10557) SWTException before code completion in HQL Editor with Hibernate 4

by Jiri Peterka (Created) (JIRA)

SWTException before code completion in HQL Editor with Hibernate 4 ------------------------------------------------------------------ Key: JBIDE-10557 URL: https://issues.jboss.org/browse/JBIDE-10557 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M5 Environment: JBDS 5.0.M5a, H62, L64,HSQLDB 1.8 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.LinkageError: loader constraint violation: when resolving method "org.hibernate.eclipse.console.workbench.HibernateWorkbenchHelper.getImage(Lorg/hibernate/mapping/Property;)Lorg/eclipse/swt/graphics/Image;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/jboss/tools/hibernate4_0/console/EclipseHQLCompletionRequestor, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/hibernate/eclipse/console/workbench/HibernateWorkbenchHelper, have different Class objects for the type org/hibernate/mapping/Property used in the signature) at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) 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:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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: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: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) Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.hibernate.eclipse.console.workbench.HibernateWorkbenchHelper.getImage(Lorg/hibernate/mapping/Property;)Lorg/eclipse/swt/graphics/Image;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/jboss/tools/hibernate4_0/console/EclipseHQLCompletionRequestor, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/hibernate/eclipse/console/workbench/HibernateWorkbenchHelper, have different Class objects for the type org/hibernate/mapping/Property used in the signature at org.jboss.tools.hibernate4_0.console.EclipseHQLCompletionRequestor.getImage(EclipseHQLCompletionRequestor.java:120) at org.jboss.tools.hibernate4_0.console.EclipseHQLCompletionRequestor.accept(EclipseHQLCompletionRequestor.java:59) at org.hibernate.tool.ide.completion.ConfigurationCompletion.addPropertiesToList(ConfigurationCompletion.java:187) at org.hibernate.tool.ide.completion.ConfigurationCompletion.getMatchingProperties(ConfigurationCompletion.java:80) at org.hibernate.tool.ide.completion.HQLCodeAssist.codeComplete(HQLCodeAssist.java:66) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.hqlCodeComplete(ConsoleExtension4_0.java:93) at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeProposals(HQLCompletionProcessor.java:122) at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeCompletionProposals(HQLCompletionProcessor.java:82) at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeCompletionProposals(HQLCompletionProcessor.java:65) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1830) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482) at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:377) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 23 more -- 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
7
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 2011