September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-2419) can not get runtime location from project target runtime with eclipse 3.4

by Denny Xu (JIRA)

can not get runtime location from project target runtime with eclipse 3.4 ------------------------------------------------------------------------- Key: JBIDE-2419 URL: http://jira.jboss.com/jira/browse/JBIDE-2419 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.0.alpha Reporter: Denny Xu Assigned To: Denny Xu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2794) Project Preferences - WSruntime errors

by Aliaksey Nis (JIRA)

Project Preferences - WSruntime errors -------------------------------------- Key: JBIDE-2794 URL: https://jira.jboss.org/jira/browse/JBIDE-2794 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.0.beta1 Environment: WindowsXP SP2 JBoss Developer Studio Version: 3.0.0.Beta1 Build id: 200809160111-nightly Build date: 09/16/2008 01:19 JDK 1.5_08 Reporter: Aliaksey Nis EXECUTE: New > Project > Dynamic Web Project EXECUTE: Select configuration - Web project with Seam 2.0. Press Modify button, add WebServices facet. Project name: "test". Press Next. EXECUTE: In WS facet settings select AS server supported implementation. EXECUTE: Select Seam 2 FP runtime, EAR type, press Finish. ASSERT: Project parts (test, test-ejb, test-ear, test-test)) created succesfully. EXECUTE: Open "test"project Preferences. Select JBossWS runtime tab. FAILURE: Tab is empty. Error message box appears. Exception thrown in error log(WSexcept1.txt). EXECUTE: Open "test-ear"project Preferences. Select JBossWS runtime tab. ASSERT: WS Facet settings tab appears. EXECUTE: Select "server supplied...", press Ok. Then open preferences and this tab again. FAILURE: Selection wasn't saved. EXECUTE: Main Menu > Window > Preferences. EXECUTE: Find JBossWS runtime tab, add new runtime (name WS runtime, path = [JBoss AS server location]). EXECUTE: Open "test-ear"project Preferences. Select JBossWS runtime tab. ASSERT: WS Facet settings tab appears. EXECUTE: Select "server supplied..." or target runtime checkbox. FAILURE: 2 exceptions "test-ear project doen't exist" appears(WSexcept2.txt) each time, when check box selected. -- 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

15 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2369) NullPointerException when create a topdown web service without project target runtime

by Denny Xu (JIRA)

NullPointerException when create a topdown web service without project target runtime ------------------------------------------------------------------------------------- Key: JBIDE-2369 URL: http://jira.jboss.com/jira/browse/JBIDE-2369 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Denny Xu Assigned To: Denny Xu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2335) Failed to set JBossWS as the default WS runtime if the user don't JBoss web service facet

by Denny Xu (JIRA)

Failed to set JBossWS as the default WS runtime if the user don't JBoss web service facet ------------------------------------------------------------------------------------------- Key: JBIDE-2335 URL: http://jira.jboss.com/jira/browse/JBIDE-2335 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.alpha Reporter: Denny Xu Assigned To: Denny Xu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2343) JBossWS facet installation does not work when there has no any JBossWS runtime predefined at the first time

by Denny Xu (JIRA)

JBossWS facet installation does not work when there has no any JBossWS runtime predefined at the first time ----------------------------------------------------------------------------------------------------------- Key: JBIDE-2343 URL: http://jira.jboss.com/jira/browse/JBIDE-2343 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Denny Xu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2775) ClassCastException in the JbossWS Runtime property page

by Snjezana Peco (JIRA)

ClassCastException in the JbossWS Runtime property page ------------------------------------------------------- Key: JBIDE-2775 URL: https://jira.jboss.org/jira/browse/JBIDE-2775 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.0.beta1 Reporter: Snjezana Peco - create a Java project - right-click the project and call Properties>JBossWS Runtime You will get a dialog showing "The currently displayed page contains invalid values" and the following exception : !ENTRY org.eclipse.jface 4 2 2008-09-16 21:28:56.015 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.ClassCastException: org.eclipse.ui.internal.views.markers.MarkerEntry cannot be cast to org.eclipse.core.resources.IProject at org.jboss.tools.ws.creation.ui.project.facet.JBossWSPropertyPage.createContents(JBossWSPropertyPage.java:29) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:235) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1466) at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1223) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) 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.preference.PreferenceDialog.showPage(PreferenceDialog.java:1217) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:570) at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:700) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:696) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:842) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) 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.firePostSelectionChanged(StructuredViewer.java:840) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1639) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1104) at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1019) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:624) at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:369) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:365) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:82) at org.eclipse.ui.internal.handlers.PropertyDialogHandler.execute(PropertyDialogHandler.java:53) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:619) at org.eclipse.ui.menus.CommandContributionItem.access$10(CommandContributionItem.java:605) at org.eclipse.ui.menus.CommandContributionItem$4.handleEvent(CommandContributionItem.java:595) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:382) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) -- 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

15 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration

by Martin Putz (JIRA)

ESB 4.7 runtime detection depends on default server configuration ----------------------------------------------------------------- Key: JBIDE-6483 URL: https://jira.jboss.org/browse/JBIDE-6483 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.1, 3.1.0.GA Reporter: Martin Putz Assignee: Brian Fitzpatrick When attempting to add SOA-P 5 as an ESB runtime to JBDS 3.0.0, this is only possible if a 'default' server configuration exists. If the 'default' server configuration is renamed to something else (like 'development' for example) then the runtime is not valid. org.jboss.tools.esb.core.runtime.ESBRuntimeResolver_47#getJarDirectories(..) has a hard-coded reference to the "default" directory. -- 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, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6847) wizard allows you to select Teiid as database type but there is no Teiid connection profile

by Isaac Rooskov (JIRA)

wizard allows you to select Teiid as database type but there is no Teiid connection profile ------------------------------------------------------------------------------------------- Key: JBIDE-6847 URL: https://jira.jboss.org/browse/JBIDE-6847 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M1 Environment: - JBoss Tools 3.2 :: Eclipse 3.6.0 -> Development Milestone - Teiid 7.0 - JBoss AS 6 - Java 1.6 - Fedora 13 Reporter: Isaac Rooskov Assignee: Alexey Kazakov Priority: Blocker When using the Seam Web Project wizard and you arrive at the Seam Facet dialog, you can select Teiid as the Database Type from the drop-down menu; but when creating a new connection profile (using the 'New" button beside the grayed out 'connection profile' drop-down box) there is no option to select a Teiid connection profile. This functionality should be added or the Teiid Database option should be removed. -- 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, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6087) Create a special plug-in in Struts project: empty submenu is displayed

by Svetlana Yasenovich (JIRA)

Create a special plug-in in Struts project: empty submenu is displayed ---------------------------------------------------------------------- Key: JBIDE-6087 URL: https://jira.jboss.org/jira/browse/JBIDE-6087 Project: Tools (JBoss Tools) Issue Type: Bug Environment: jbdevstudio-eap-win32-3.0.0.v201003100055R-H50-GA Reporter: Svetlana Yasenovich Attachments: Create_Special_Plug-in_video.zip EXECUTE: 1. Create Struts project 2. Go to Configuration > default > struts-config.xml 3. Right-click on a "plug-ins" node and choose the "Create Special Plug-in" FAILURE: the empty submenu is displayed for "Create Special Plug-in" (please find Create_Special_Plug-in_video in the attachment). -- 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

15 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1314) Questionable branding/provider name for modeshape feature

by Nick Boldt (JIRA)

Questionable branding/provider name for modeshape feature --------------------------------------------------------- Key: JBDS-1314 URL: https://jira.jboss.org/browse/JBDS-1314 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Modeshape Affects Versions: 4.0.0.M2 Reporter: Nick Boldt Assignee: Max Andersen Priority: Minor Modeshape's provider is Red Hat, Inc., not JBoss by Red Hat; also, the icon is different from rest of JBoss Tools / JBDS. Is this correct? Should it be changed? -- 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

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