September 2008 - jbosstools-issues

[JBoss JIRA] Resolved: (JBIDE-2633) Error text is misleading for WS runtime

by Feng Qian (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-2633?page=com.atlassian.jira.plu... ] Feng Qian resolved JBIDE-2633. ------------------------------ Resolution: Done done > Error text is misleading for WS runtime > --------------------------------------- > > Key: JBIDE-2633 > URL: https://jira.jboss.org/jira/browse/JBIDE-2633 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.0.0.alpha > Reporter: Max Rydahl Andersen > Assignee: Feng Qian > Fix For: 3.0.0.beta1 > > > Create new webservices runtime and select a random directory (not jboss) and an error message says select either JBoss AS or JBoss EAP directory. > If I select the jboss-eap directory it still shows up. > I assume JBoss EAP is irrelevant here and users should just be told to select JBoss AS directory. > note: what if the runtime is in tomcat ? > Furthermore if I click "Customize runtime jars" it tells me there have to be at least one jar, but if it is not clicked there are no jars in the list - that is inconsistent. -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-2636) version number for jbossws runtimes are free-form, should be more controlled

by Feng Qian (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-2636?page=com.atlassian.jira.plu... ] Feng Qian resolved JBIDE-2636. ------------------------------ Resolution: Done done > version number for jbossws runtimes are free-form, should be more controlled > ---------------------------------------------------------------------------- > > Key: JBIDE-2636 > URL: https://jira.jboss.org/jira/browse/JBIDE-2636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.0.0.alpha > Reporter: Max Rydahl Andersen > Assignee: Feng Qian > Fix For: 3.0.0.beta1 > > > I see that I can write anything in the version field of the runtime for jbossws runtimes. > Aren't these supposed to be more specific ones (e.g. a list of supported values) so you can control the behavior of how you do different things depedent on the version / type of jbossws runtime ? -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-295) Ecllpse 3.2M6 breaks JBossAS adapters...

by Gaurav Sharma (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-295?page=com.atlassian.jira.plug... ] Gaurav Sharma commented on JBIDE-295: ------------------------------------- I could not able to download the file "org-jboss-ide-eclipse-launcher-ui.jar" from this post. IE is giving error as "The file could not be written to the cache". Please help! I need this file to fix this issue in my system. > Ecllpse 3.2M6 breaks JBossAS adapters... > ---------------------------------------- > > Key: JBIDE-295 > URL: https://jira.jboss.org/jira/browse/JBIDE-295 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 1.5.1 > Reporter: Marshall Culpepper > Assignee: Marshall Culpepper > Fix For: 2.0.0.GA > > Attachments: org-jboss-ide-eclipse-launcher-ui.jar > > > The relevant parts of the stack trace: > java.lang.NoClassDefFoundError: > org/eclipse/jdt/internal/debug/ui/launcher/JavaLaunchConfigurationTab > at java.lang.ClassLoader.defineClass0(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:539) > .............. > at > org.jboss.ide.eclipse.launcher.ui.configuration.jboss.JBoss40xTabGroup.creat > eTabs(JBoss40xTabGroup.java:60) > at > org.eclipse.debug.internal.ui.launchConfigurations.CreateLaunchConfiguration > Action.performAction(CreateLaunchConfigurationAction.java:70) > at > org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurati > onAction$1.run(AbstractLaunchConfigurationAction.java:103) > at > org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) > ..... -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-2611) auto layout for pages.xml needs to be better

by Max Rydahl Andersen (JIRA)

auto layout for pages.xml needs to be better -------------------------------------------- Key: JBIDE-2611 URL: https://jira.jboss.org/jira/browse/JBIDE-2611 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.alpha Reporter: Max Rydahl Andersen Assignee: Daniel Azarov Fix For: 3.0.0.alpha The current autolayout for pages.xml gets cluttered with just a few nodes. Maybe consider using just straight lines and a left to right layout based on target. -- 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

17 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (RHDS-161) Links on the title page

by Svetlana mukhina (JIRA)

Links on the title page ----------------------- Key: RHDS-161 URL: http://jira.jboss.com/jira/browse/RHDS-161 Project: Red Hat Developer Studio Issue Type: Sub-task Components: documentation Affects Versions: 1.0.0.beta2 Reporter: Svetlana mukhina Assigned To: Svetlana mukhina Fix For: LATER There should be links to other kind of versions on each title page guide e.g. links to PDF and Single Page should be placed on Multi page version -- 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

17 years, 6 months

2
13
0 / 0

[JBoss JIRA] Created: (JBIDE-2779) ClassCastException when adding the JBoss ESB facet

by Snjezana Peco (JIRA)

ClassCastException when adding the JBoss ESB facet -------------------------------------------------- Key: JBIDE-2779 URL: https://jira.jboss.org/jira/browse/JBIDE-2779 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.beta1 Reporter: Snjezana Peco - call the New Dynamic Web Project wizard - click the Modify button - check the JBoss ESB facet - click OK You will get the following exception : !ENTRY org.eclipse.wst.common.project.facet.core 4 0 2008-09-17 10:19:39.718 !MESSAGE org.eclipse.jst.servlet.ui.project.facet.WebProjectWizard cannot be cast to org.jboss.tools.esb.project.ui.wizards.ESBProjectWizard !STACK 0 java.lang.ClassCastException: org.eclipse.jst.servlet.ui.project.facet.WebProjectWizard cannot be cast to org.jboss.tools.esb.project.ui.wizards.ESBProjectWizard at org.jboss.tools.esb.project.ui.wizards.pages.ESBFacetInstallationPage.getFacetedProjectWorkingCopy(ESBFacetInstallationPage.java:157) at org.jboss.tools.esb.project.ui.wizards.pages.ESBFacetInstallationPage.getSelectedESBVersion(ESBFacetInstallationPage.java:310) at org.jboss.tools.esb.project.ui.wizards.pages.ESBFacetInstallationPage.initializeRuntimesCombo(ESBFacetInstallationPage.java:300) at org.jboss.tools.esb.project.ui.wizards.pages.ESBFacetInstallationPage.createRuntimeGroup(ESBFacetInstallationPage.java:220) at org.jboss.tools.esb.project.ui.wizards.pages.ESBFacetInstallationPage.createTopLevelComposite(ESBFacetInstallationPage.java:77) at org.jboss.tools.esb.project.ui.wizards.pages.ESBFacetInstallationPage.createControl(ESBFacetInstallationPage.java:399) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.handleSelectedFacetsChangedEvent(ModifyFacetedProjectWizard.java:711) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.access$0(ModifyFacetedProjectWizard.java:653) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$1$1.run(ModifyFacetedProjectWizard.java:165) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:178) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4251) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$1.handleEvent(ModifyFacetedProjectWizard.java:169) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.notifyListeners(FacetedProjectWorkingCopy.java:1640) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.resumeEventNotification(FacetedProjectWorkingCopy.java:1685) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.mergeChanges(FacetedProjectWorkingCopy.java:1882) at org.eclipse.wst.common.project.facet.ui.internal.FacetsSelectionDialog.okPressed(FacetsSelectionDialog.java:75) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) 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.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.wst.common.project.facet.ui.internal.FacetsSelectionDialog.openDialog(FacetsSelectionDialog.java:83) at org.eclipse.wst.common.project.facet.ui.PresetSelectionPanel.handleModifyButtonPressed(PresetSelectionPanel.java:150) at org.eclipse.wst.common.project.facet.ui.PresetSelectionPanel.access$0(PresetSelectionPanel.java:148) at org.eclipse.wst.common.project.facet.ui.PresetSelectionPanel$1.widgetSelected(PresetSelectionPanel.java:91) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) 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.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) 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

17 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2777) clean up svn trunk

by Max Rydahl Andersen (JIRA)

clean up svn trunk ------------------ Key: JBIDE-2777 URL: https://jira.jboss.org/jira/browse/JBIDE-2777 Project: Tools (JBoss Tools) Issue Type: Task Components: common Affects Versions: 3.0.0.alpha Reporter: Max Rydahl Andersen Fix For: 3.0.0.beta1 The following should be moved to workspace/non-maintained: hibernate/ org.jboss.tools.hibernate.core org.jboss.tools.hibernate.veditor org.jboss.tools.hibernate.view org.jboss.tools.hibernate.updatesite cache/* netbeans/* The following should be deleted since it is out-of-date/not-used as far as I can see (we can always restore if it needed) update-site/* core/docs/* core/features/org.jboss.ide.eclipse.source/* -- 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBIDE-2633) Error text is misleading for WS runtime

by Feng Qian (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-2633?page=com.atlassian.jira.plu... ] Feng Qian commented on JBIDE-2633: ---------------------------------- en, you are right. I think we should support other runtime like tomcat in the future. But now we only support AS. > Error text is misleading for WS runtime > --------------------------------------- > > Key: JBIDE-2633 > URL: https://jira.jboss.org/jira/browse/JBIDE-2633 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.0.0.alpha > Reporter: Max Rydahl Andersen > Assignee: Feng Qian > Fix For: 3.0.0.beta1 > > > Create new webservices runtime and select a random directory (not jboss) and an error message says select either JBoss AS or JBoss EAP directory. > If I select the jboss-eap directory it still shows up. > I assume JBoss EAP is irrelevant here and users should just be told to select JBoss AS directory. > note: what if the runtime is in tomcat ? > Furthermore if I click "Customize runtime jars" it tells me there have to be at least one jar, but if it is not clicked there are no jars in the list - that is inconsistent. -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-409) Upgrade to EAP 4.3 w/seam 2 fp

by Max Rydahl Andersen (JIRA)

Upgrade to EAP 4.3 w/seam 2 fp ------------------------------ Key: JBDS-409 URL: https://jira.jboss.org/jira/browse/JBDS-409 Project: Developer Studio Issue Type: Task Components: Build Affects Versions: 2.0.0.alpha Reporter: Max Rydahl Andersen Assignee: Denis Golovin Priority: Critical Fix For: 2.0.0.alpha Update build to use EAP 4.3 with seam 2 fp. -- 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

17 years, 6 months

3
15
0 / 0

[JBoss JIRA] Commented: (JBIDE-2633) Error text is misleading for WS runtime

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-2633?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2633: -------------------------------------------- if you don't support tomcat and only jboss AS why do we have to have an additional runtime concept ? > Error text is misleading for WS runtime > --------------------------------------- > > Key: JBIDE-2633 > URL: https://jira.jboss.org/jira/browse/JBIDE-2633 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.0.0.alpha > Reporter: Max Rydahl Andersen > Assignee: Feng Qian > Fix For: 3.0.0.beta1 > > > Create new webservices runtime and select a random directory (not jboss) and an error message says select either JBoss AS or JBoss EAP directory. > If I select the jboss-eap directory it still shows up. > I assume JBoss EAP is irrelevant here and users should just be told to select JBoss AS directory. > note: what if the runtime is in tomcat ? > Furthermore if I click "Customize runtime jars" it tells me there have to be at least one jar, but if it is not clicked there are no jars in the list - that is inconsistent. -- 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

17 years, 6 months

1
0
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 2008