December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6739) cannot create a ws from wsdl implementation class if user specifies no package

by Lukas Jungmann (JIRA)

cannot create a ws from wsdl implementation class if user specifies no package ------------------------------------------------------------------------------ Key: JBIDE-6739 URL: https://jira.jboss.org/browse/JBIDE-6739 Project: Tools (JBoss Tools) Issue Type: Bug Environment: v20100728-2128-H133-M2 Reporter: Lukas Jungmann Attachments: interfax.wsdl -create ws from attached WSDL => Failed to generate implementation class org.eclipse.core.runtime.CoreException: Failed to Generate Web Service code, please check the log for more details at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.getCompilationUnitForInterface(ImplementationClassCreationCommand.java:446) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.generateImplClass(ImplementationClassCreationCommand.java:133) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.execute(ImplementationClassCreationCommand.java:97) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419) ... -- 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, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6754) [restwizard] name should be changed to Path or URI

by Lukas Jungmann (JIRA)

[restwizard] name should be changed to Path or URI -------------------------------------------------- Key: JBIDE-6754 URL: https://jira.jboss.org/browse/JBIDE-6754 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -open Sample RESTful service wizard => Web Service -> Name label should be changed to either Path or URI since what user sets in this field is in fact Path/URI within the application where the resource will become available -- 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, 4 months

2
12
0 / 0

[JBoss JIRA] Created: (JBIDE-6831) cannot create sample web service with an existing name in a different package

by Lukas Jungmann (JIRA)

cannot create sample web service with an existing name in a different package ----------------------------------------------------------------------------- Key: JBIDE-6831 URL: https://jira.jboss.org/browse/JBIDE-6831 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Priority: Minor -have a dynamic web project -create a default sample web service -open the sample web service wizard again and set: set class name to: "HelloWorld" set package name to: "x.y.z" => wizard says that class HelloWorld already exists but what I'm trying to create is file "x.y.z.HelloWorld", not "org.jboss.samples.webservices.HelloWorld" -- 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, 4 months

3
15
0 / 0

[JBoss JIRA] Created: (JBIDE-7336) jBPM runtime defined at preferences puntime location page is not available during creating new jBPM project

by Jiri Peterka (JIRA)

jBPM runtime defined at preferences puntime location page is not available during creating new jBPM project ----------------------------------------------------------------------------------------------------------- Key: JBIDE-7336 URL: https://jira.jboss.org/browse/JBIDE-7336 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.Beta1 Environment: JBDS 4.0.0.beta1 #47 Reporter: Jiri Peterka 1. Add soem jBPM 3 runtime location (Preferences->Jboss jBPM -> Runtime Location) 2. Create new jBPM Project ERROR: On page 2 you're forced to define new jBPM runtime again although there are some of them already defined and these are not available for selection -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6960) jBPM project wizard does not offer runtimes set workspace preferences

by Jiri Peterka (JIRA)

jBPM project wizard does not offer runtimes set workspace preferences --------------------------------------------------------------------- Key: JBIDE-6960 URL: https://jira.jboss.org/browse/JBIDE-6960 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.M2 Environment: JBDS 4.0.0.v201008261621R-H420-M2, Linux 64, JDK 1.6 Reporter: Jiri Peterka Steps: 1. New workspace 2. Add jBM 3 Runtime Location in Preferences -> Jboss jBPM -> jBPM 3 -> Runtime Location page, OK 3. New jBPM 3 Project, Next, Next ERROR: jBPM runtime isn't present when creating new jbpm project and user is forced to define it again Note: I've used jBPM 3.2.5.GA runtime -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6590) Widget is disposed error when changing names of nodes in jBMP 3 editor

by Duncan Doyle (JIRA)

Widget is disposed error when changing names of nodes in jBMP 3 editor ---------------------------------------------------------------------- Key: JBIDE-6590 URL: https://jira.jboss.org/browse/JBIDE-6590 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.1 Environment: Ubuntu Lucid Lynx x64, Eclipse WTP Galileo (3.5.2) Reporter: Duncan Doyle Assignee: Koen Aers When I change the name of a node in my jBPM 3 Process Definition editor, I often get this error: "Widget is Disposed" It seems only to occur when my process contains a Mail Node and I edit something on such a node (adding a Mail Node to the process, changing the name of a Mail Node, etc.). I can change names of all my other nodes in my process, but after I change the name of a mail node once or twice, every other change to any of the node names seems to result in this error. After I close the editor and reopen it (not exiting Eclipse, but just closing en re-opening the editor), I can again change the names of all nodes without issues, until I change the name of a Mail Node. See the "Steps to reproduce" section of this issue. The Eclipse error log is: !ENTRY org.eclipse.jface 4 2 2010-07-08 00:25:33.521 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.SWT.error(SWT.java:3799) at org.eclipse.swt.SWT.error(SWT.java:3770) at org.eclipse.swt.widgets.Widget.error(Widget.java:450) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:388) at org.eclipse.swt.widgets.Text.setText(Text.java:1979) at org.jbpm.gd.common.properties.NamedElementConfigurationComposite.propertyChange(NamedElementConfigurationComposite.java:111) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) at org.jbpm.gd.common.model.AbstractSemanticElement.firePropertyChange(AbstractSemanticElement.java:20) at org.jbpm.gd.common.model.AbstractNamedElement.setName(AbstractNamedElement.java:11) at org.jbpm.gd.common.command.ChangeNameCommand.execute(ChangeNameCommand.java:27) at org.eclipse.gef.commands.CommandStack.execute(CommandStack.java:170) at org.eclipse.gef.tools.DirectEditManager.commit(DirectEditManager.java:136) at org.eclipse.gef.tools.DirectEditManager$4.applyEditorValue(DirectEditManager.java:270) at org.eclipse.jface.viewers.CellEditor$1.run(CellEditor.java:333) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.CellEditor.fireApplyEditorValue(CellEditor.java:331) at org.eclipse.jface.viewers.TextCellEditor.handleDefaultSelection(TextCellEditor.java:295) at org.eclipse.jface.viewers.TextCellEditor$1.widgetDefaultSelected(TextCellEditor.java:148) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:113) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.views.log.EventDetailsDialog.open(EventDetailsDialog.java:175) at org.eclipse.ui.internal.views.log.EventDetailsDialogAction.run(EventDetailsDialogAction.java:98) at org.eclipse.ui.internal.views.log.LogView$15.doubleClick(LogView.java:535) at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:821) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:819) at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1419) at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1195) at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:238) at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:235) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:296) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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, 4 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-7762) BPEL Editor in latest NB hangs when opening PolicyQuoteProcess

by Jeff DeLong (JIRA)

BPEL Editor in latest NB hangs when opening PolicyQuoteProcess -------------------------------------------------------------- Key: JBIDE-7762 URL: https://jira.jboss.org/browse/JBIDE-7762 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Beta1 Environment: JBoss BPEL Editor 1.0.0.v20101129-1426-H13-Beta2 org.jboss.tools.bpel.feature.feature.group on Mac 10.6.4 Reporter: Jeff DeLong Assignee: Max Andersen I used the Eclipse Update feature to update to the latest NB. The BPEL Editor hangs when opening the PolicyQuoteProcess. I even tried creating a new project using the BPEL Project wizard and copying in the bpelContents folder but is still hanging on opening the file. When I hover my mouse over the editor window, some of the labels for the activities display. I deleted the bpelex file and was able to re-open the bpel file, but now even doing this does not work. When I try to open the file I get the following error: An error has occurred. See error log for more details. java.lang.NullPointerException At this point Eclipse is hung. I tried this on other process definitions with a similar result. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7166) NPE during editing XHTML file in whatsnew project

by Maxim Areshkau (JIRA)

NPE during editing XHTML file in whatsnew project ------------------------------------------------- Key: JBIDE-7166 URL: https://jira.jboss.org/browse/JBIDE-7166 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.Beta1 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 Attachments: NPE-KBE.png During editing xhtml file for whats new appeared NPE. -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7526) "Unknown Marker ID" exception being thrown by editor on mousehover over error decorator

by Robert (Bob) Brodt (JIRA)

"Unknown Marker ID" exception being thrown by editor on mousehover over error decorator --------------------------------------------------------------------------------------- Key: JBIDE-7526 URL: https://jira.jboss.org/browse/JBIDE-7526 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Reporter: Robert (Bob) Brodt Priority: Minor Fix For: 3.2.0.Beta2 The marker arrays for activities are not being cleaned up properly when markers are removed from a BPEL resource (e.g. when the error is corrected). This causes the editor to throw an exception when the user hovers the mouse over an error decorator. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7726) Unable to create JPA based Configuration due to java.lang.ClassNotFoundException: javax.validation.Validation

by Martin Gencur (JIRA)

Unable to create JPA based Configuration due to java.lang.ClassNotFoundException: javax.validation.Validation ------------------------------------------------------------------------------------------------------------- Key: JBIDE-7726 URL: https://jira.jboss.org/browse/JBIDE-7726 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.Beta2 Environment: JBoss Tools 3.2.0.v20101122-2055-H270-Beta2, Seam 2.2.1-SNAPSHOT from 2010-11-23 Reporter: Martin Gencur Assignee: Max Andersen Fix For: 3.2.0.Final Attachments: JPA.png Steps to reproduce the bug: 1) import a Seam project generated by SeamGen, enable Seam support on the project 2) open Window -> Show View -> Hibernate Configurations, click the project in the view 3) now you get the exception shown in the attached screenshot -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
47
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