July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8829) ExpressionImpl cannot be cast to Activity while editing OnAlarm activity

by Robert (Bob) Brodt (JIRA)

ExpressionImpl cannot be cast to Activity while editing OnAlarm activity ------------------------------------------------------------------------ Key: JBIDE-8829 URL: https://issues.jboss.org/browse/JBIDE-8829 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Final Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.3.0.Final Create an Event Handler for a process, and add an OnAlarm. Then switch to Source view and select the <repeatEvery> element. Stack trace shown below: java.lang.ClassCastException: org.eclipse.bpel.model.impl.ConditionImpl cannot be cast to org.eclipse.bpel.model.Activity at org.eclipse.bpel.ui.properties.JoinConditionSection.getExpressionTarget(JoinConditionSection.java:65) at org.eclipse.bpel.ui.properties.ExpressionSection.getExprFromModel(ExpressionSection.java:536) at org.eclipse.bpel.ui.properties.ExpressionSection.updateExpressionLanguageWidgets(ExpressionSection.java:387) at org.eclipse.bpel.ui.properties.ExpressionSection.basicSetInput(ExpressionSection.java:432) at org.eclipse.bpel.ui.properties.JoinConditionSection.basicSetInput(JoinConditionSection.java:101) at org.eclipse.bpel.ui.properties.BPELPropertySection.setInput(BPELPropertySection.java:221) at org.eclipse.ui.views.properties.tabbed.TabContents$5.run(TabContents.java:181) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.ui.views.properties.tabbed.TabContents.setInput(TabContents.java:184) at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage$SelectionChangedListener.selectionChanged(TabbedPropertySheetPage.java:212) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:162) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2167) at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1190) at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1220) at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:229) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:223) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:393) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774) at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.select(TabbedPropertyList.java:664) at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyViewer.setSelectionToWidget(TabbedPropertyViewer.java:122) at org.eclipse.jface.viewers.StructuredViewer.setSelectionToWidget(StructuredViewer.java:1746) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1702) at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:394) at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.setInput(TabbedPropertySheetPage.java:736) at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.selectionChanged(TabbedPropertySheetPage.java:555) at org.eclipse.bpel.ui.BPELTabbedPropertySheetPage.selectionChanged(BPELTabbedPropertySheetPage.java:99) at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:365) at org.eclipse.ui.internal.AbstractSelectionService.firePostSelection(AbstractSelectionService.java:179) at org.eclipse.ui.internal.AbstractSelectionService$2.selectionChanged(AbstractSelectionService.java:71) at org.eclipse.ui.part.MultiPageSelectionProvider$1.run(MultiPageSelectionProvider.java:110) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.part.MultiPageSelectionProvider.fireEventChange(MultiPageSelectionProvider.java:108) at org.eclipse.ui.part.MultiPageSelectionProvider.firePostSelectionChanged(MultiPageSelectionProvider.java:102) at org.eclipse.ui.part.MultiPageEditorSite.handlePostSelectionChanged(MultiPageEditorSite.java:428) at org.eclipse.ui.part.MultiPageEditorSite$3.selectionChanged(MultiPageEditorSite.java:340) at org.eclipse.bpel.common.ui.tray.MultiViewerSelectionProvider.fireSelectionChanged(MultiViewerSelectionProvider.java:147) at org.eclipse.bpel.ui.BPELAdaptingSelectionProvider.setSelection(BPELAdaptingSelectionProvider.java:64) at org.eclipse.bpel.ui.BPELMultipageEditorPart$TextEditorSelectionListener.selectionChanged(BPELMultipageEditorPart.java:296) at org.eclipse.wst.sse.ui.StructuredTextEditor$4.run(StructuredTextEditor.java:592) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.fireSelectionChanged(StructuredTextEditor.java:590) at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.handlePostSelectionChanged(StructuredTextEditor.java:671) at org.eclipse.wst.sse.ui.StructuredTextEditor$3.selectionChanged(StructuredTextEditor.java:564) at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2746) at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2694) at org.eclipse.jface.text.TextViewer$5.run(TextViewer.java:2673) at org.eclipse.swt.widgets.Display.runTimer(Display.java:4227) at org.eclipse.swt.widgets.Display.messageProc(Display.java:3314) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2523) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3713) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2697) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2661) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2495) 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: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: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) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-1565) Installer should use numbering of the same server names simliar as in JBT/JBDS

by Jiri Peterka (JIRA)

Installer should use numbering of the same server names simliar as in JBT/JBDS ------------------------------------------------------------------------------ Key: JBDS-1565 URL: https://issues.jboss.org/browse/JBDS-1565 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer, runtime Affects Versions: 4.0.0.CR3 Environment: JBDS 4.0.0.CR3 H162, Linux 64 Reporter: Jiri Peterka Attachments: installer-numbering.png, jbds-numbering.png Usual way is to have unique numbering for each name, something like this: jboss-eap-4.0 jboss-eap-4.0(1) jboss-eap-4.0(2) jboss-soa-p5 jboss-soa-p5 (1) jboss-soa-p5 (2) .. In JBDS installer there is numbering like this: jboss-eap-4.0 jboss-eap-4.0(1) jboss-eap-4.0(2) jboss-soa-p5 jboss-soa-p5 (3) jboss-soa-p5 (4) This should be changed and unified with that how runtimes are titled in JBT/JBDS via Runtime Detection. Add some brackits in JBDS would be better as well. For comparsion of the same runtime set in Installer and JBT/JBDS see screenshots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9136) mismatch between MANIFEST.MF and build.properties in org.jboss.ide.eclipse.as.archives.integration.test

by Nick Boldt (JIRA)

mismatch between MANIFEST.MF and build.properties in org.jboss.ide.eclipse.as.archives.integration.test ------------------------------------------------------------------------------------------------------- Key: JBIDE-9136 URL: https://issues.jboss.org/browse/JBIDE-9136 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS, testing Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Rob Stryker In http://anonsvn.jboss.org/repos/jbosstools/trunk/as/tests/org.jboss.ide.ec..., build.properties defines that this plugin will have a nested jar in it: jars.compile.order = jbossasarchivesintegrationtest.jar output.jbossasarchivesintegrationtest.jar = bin/ however, MANIFEST.MF points its classpath definition at the root, assuming there'll be a classes/*.class folder, not a rooted jar: Bundle-ClassPath: . You can't have it both ways -- suggest replacing "jbossasarchivesintegrationtest.jar" with "." in build.properties. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9100) Improve sepration of concerns when creating .dodeploy markers in JBoss7ServerBehavior and JBoss7JSTPublisher

by Andre Dietisheim (JIRA)

Improve sepration of concerns when creating .dodeploy markers in JBoss7ServerBehavior and JBoss7JSTPublisher ------------------------------------------------------------------------------------------------------------- Key: JBIDE-9100 URL: https://issues.jboss.org/browse/JBIDE-9100 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M2 When deploying to AS7 there are 2 components involved: * JBoss7JSTPublisher: adds markers that shall be created to the JBoss7ServerBehavior (see #markDeployed) * JBoss7ServerBehavior: creates the .dodeploy markers (see #publishFinish) IMHO what is not ideal here is that the list of markers that shall be created is passed around in form of an object (the publisher adds a list as a java.lang.Object and the server behavior then gets the java.lang.Object and then cast it to a List. If you would want to change the form that shall hold the marker you'd have to figure out and change both components. Both components have to know about the form, which is not ideal in terms of separation of concerns. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9090) DeploymentMarkerUtils methods should have consistent method parameters (always the same order of parameter types)

by Andre Dietisheim (JIRA)

DeploymentMarkerUtils methods should have consistent method parameters (always the same order of parameter types) ----------------------------------------------------------------------------------------------------------------- Key: JBIDE-9090 URL: https://issues.jboss.org/browse/JBIDE-9090 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M2 The different methods in DeploymentMarkerUtils have an inconsistent order of the method parameter: ex. the publish method which is used in most of them is 1st in some methods, 2nd in others. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8852) erroneous Deployments show up in 2nd server adapter

by Andre Dietisheim (JIRA)

erroneous Deployments show up in 2nd server adapter --------------------------------------------------- Key: JBIDE-8852 URL: https://issues.jboss.org/browse/JBIDE-8852 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.0.M2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9089) AS7: DeploymentMarkerUtils#removeDeployFailedMarkerIfExists does not remove .failed marker

by Andre Dietisheim (JIRA)

AS7: DeploymentMarkerUtils#removeDeployFailedMarkerIfExists does not remove .failed marker ------------------------------------------------------------------------------------------ Key: JBIDE-9089 URL: https://issues.jboss.org/browse/JBIDE-9089 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M2 DeploymentMarkerUtils#removeDeployFailedMarkerIfExists does not remove the .failed marker. It actually removes the .deployed marker: removeDeployedMarkerIfExists(method, deployableServer, module, monitor); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8908) browse buttons for server editor not working properly

by Rob Stryker (JIRA)

browse buttons for server editor not working properly ----------------------------------------------------- Key: JBIDE-8908 URL: https://issues.jboss.org/browse/JBIDE-8908 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Final, 3.3.0.M1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.1.CR1, 3.3.0.M2 On page 1, in rse mode, the browse buttons do nothing for deploy-only servers On page 2, the browse buttons always use local browsing, never rse. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-9130) Remote Server home should be checked for vailidity

by Andre Dietisheim (JIRA)

Remote Server home should be checked for vailidity -------------------------------------------------- Key: JBIDE-9130 URL: https://issues.jboss.org/browse/JBIDE-9130 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8920) clean warnings about internal classes in AS adapters

by Andre Dietisheim (JIRA)

clean warnings about internal classes in AS adapters ---------------------------------------------------- Key: JBIDE-8920 URL: https://issues.jboss.org/browse/JBIDE-8920 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M2 the current code uses quite an amount of internal wtp classes. We should clean those warnings. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
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 July 2011