October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6784) IllegalArgumentException after deleting a BPEL Scope within Flow

by Robert (Bob) Brodt (JIRA)

IllegalArgumentException after deleting a BPEL Scope within Flow ---------------------------------------------------------------- Key: JBIDE-6784 URL: https://jira.jboss.org/browse/JBIDE-6784 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M1 Environment: All Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.x BPEL Editor throws an IllegalArgumentException during editing. java.lang.IllegalArgumentException: EObject does not have an eResource() at org.eclipse.bpel.ui.util.ModelHelper.getBPELEditor(ModelHelper.java:1297) at org.eclipse.bpel.ui.util.ModelHelper.isHorizontalLayout(ModelHelper.java:1308) at org.eclipse.bpel.ui.editparts.borders.ScopeBorder.calculate(ScopeBorder.java:197) at org.eclipse.bpel.ui.editparts.borders.ScopeBorder.getInsets(ScopeBorder.java:250) at org.eclipse.draw2d.Figure.getInsets(Figure.java:686) at org.eclipse.draw2d.FlowLayout.calculatePreferredSize(FlowLayout.java:156) at org.eclipse.draw2d.AbstractLayout.getPreferredSize(AbstractLayout.java:110) at org.eclipse.draw2d.AbstractHintLayout.getPreferredSize(AbstractHintLayout.java:90) at org.eclipse.draw2d.Figure.getPreferredSize(Figure.java:807) at org.eclipse.bpel.common.ui.layouts.AlignedFlowLayout.getChildSize(AlignedFlowLayout.java:169) at org.eclipse.bpel.common.ui.layouts.AlignedFlowLayout.calculatePreferredSize(AlignedFlowLayout.java:136) at org.eclipse.draw2d.AbstractLayout.getPreferredSize(AbstractLayout.java:110) at org.eclipse.draw2d.AbstractHintLayout.getPreferredSize(AbstractHintLayout.java:90) at org.eclipse.draw2d.Figure.getPreferredSize(Figure.java:807) at org.eclipse.bpel.common.ui.layouts.AlignedFlowLayout.getChildSize(AlignedFlowLayout.java:169) at org.eclipse.bpel.common.ui.layouts.AlignedFlowLayout.calculatePreferredSize(AlignedFlowLayout.java:136) at org.eclipse.draw2d.AbstractLayout.getPreferredSize(AbstractLayout.java:110) at org.eclipse.draw2d.AbstractHintLayout.getPreferredSize(AbstractHintLayout.java:90) at org.eclipse.draw2d.Figure.getPreferredSize(Figure.java:807) at org.eclipse.draw2d.StackLayout.calculatePreferredSize(StackLayout.java:72) at org.eclipse.draw2d.AbstractLayout.getPreferredSize(AbstractLayout.java:110) at org.eclipse.draw2d.AbstractHintLayout.getPreferredSize(AbstractHintLayout.java:90) at org.eclipse.draw2d.Figure.getPreferredSize(Figure.java:807) at org.eclipse.draw2d.Figure.getPreferredSize(Figure.java:797) at org.eclipse.bpel.ui.editparts.FlowEditPart.computeAutoLayoutGraph(FlowEditPart.java:420) at org.eclipse.bpel.ui.editparts.FlowEditPart.doAutoLayout(FlowEditPart.java:496) at org.eclipse.bpel.ui.editparts.FlowEditPart.addChildVisual(FlowEditPart.java:240) at org.eclipse.gef.editparts.AbstractEditPart.reorderChild(AbstractEditPart.java:951) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.reorderChild(AbstractGraphicalEditPart.java:855) at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:766) at org.eclipse.bpel.ui.editparts.BPELEditPart.refreshChildren(BPELEditPart.java:315) at org.eclipse.bpel.ui.editparts.FlowEditPart.handleModelChanged(FlowEditPart.java:535) at org.eclipse.bpel.ui.editparts.BPELEditPart$1.notify(BPELEditPart.java:102) at org.eclipse.bpel.ui.util.MultiObjectAdapter.doNotify(MultiObjectAdapter.java:89) at org.eclipse.bpel.ui.util.MultiObjectAdapter.notifyChanged(MultiObjectAdapter.java:105) at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:380) at org.eclipse.wst.wsdl.internal.impl.WSDLElementImpl.eNotify(WSDLElementImpl.java:477) at org.eclipse.emf.ecore.util.EcoreEList.dispatchNotification(EcoreEList.java:255) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.remove(NotifyingListImpl.java:719) at org.eclipse.emf.common.util.AbstractEList.remove(AbstractEList.java:466) at org.eclipse.bpel.ui.adapters.delegates.ReferenceContainer.removeChild(ReferenceContainer.java:146) at org.eclipse.bpel.ui.adapters.delegates.ReferenceContainer.removeChild(ReferenceContainer.java:1) at org.eclipse.bpel.ui.adapters.ContainerActivityAdapter.removeChild(ContainerActivityAdapter.java:43) at org.eclipse.bpel.ui.commands.DeleteChildCommand.doExecute(DeleteChildCommand.java:273) at org.eclipse.bpel.ui.commands.CompoundCommand.doExecute(CompoundCommand.java:63) at org.eclipse.bpel.ui.commands.util.AutoUndoCommand.execute(AutoUndoCommand.java:108) at org.eclipse.bpel.common.ui.editmodel.EditModelCommandStack.execute(EditModelCommandStack.java:123) at org.eclipse.gef.ui.actions.WorkbenchPartAction.execute(WorkbenchPartAction.java:83) at org.eclipse.bpel.ui.actions.BPELDeleteAction.run(BPELDeleteAction.java:157) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) 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.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.OutOfOrderListener.handleEvent(OutOfOrderListener.java:76) 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.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1294) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:730) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2839) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4794) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4372) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8163) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1239) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2224) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3169) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) 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) -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6640) Open Injected Class isn't aware of alternatives

by Pete Muir (JIRA)

Open Injected Class isn't aware of alternatives ----------------------------------------------- Key: JBIDE-6640 URL: https://jira.jboss.org/browse/JBIDE-6640 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Pete Muir Assignee: Max Rydahl Andersen If a class is an alternative, this should be shown (graphically?) in the list of possible implementing beans. If a class is an enabled alternative, this should be differentiated from non-enabled alternatives. -- 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

6
16
0 / 0

[JBoss JIRA] Created: (JBIDE-6950) Validation for CDI Injection Point fails if injectable bean is in another project

by Fabricio Lemos (JIRA)

Validation for CDI Injection Point fails if injectable bean is in another project --------------------------------------------------------------------------------- Key: JBIDE-6950 URL: https://jira.jboss.org/browse/JBIDE-6950 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.M1 Reporter: Fabricio Lemos Assignee: Alexey Kazakov Jboss Tools (3.2.0.M1) mistakenly gives this warning: "No bean is eligible for injection to the injection point". The bean eligible for injection exists but is in another project More details on: http://community.jboss.org/thread/155975 -- 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

4
6
0 / 0

[JBoss JIRA] Created: (JBDS-1248) Need updated splash, installer, etc. graphics for JBDS 4.0

by Nick Boldt (JIRA)

Need updated splash, installer, etc. graphics for JBDS 4.0 ---------------------------------------------------------- Key: JBDS-1248 URL: https://jira.jboss.org/browse/JBDS-1248 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 4.0.0.M1 Reporter: Nick Boldt Assignee: Lex Dmitriev We need new graphics for JBDS 4. Here is what we have in SVN for JBDS 3. --- Current source files (JBDS 3): http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.r... http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.r... http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.r... Resulting images (JBDS 3): http://svn.jboss.org/repos/devstudio/trunk/devstudio-installer/src/config... http://svn.jboss.org/repos/devstudio/trunk/devstudio-installer/src/config... http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds... JBDS 3 Splash screen fonts: "Arial Black", size 9px "Arial", size 8px -- 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

6
14
0 / 0

[JBoss JIRA] Created: (JBIDE-6964) ESB project making use of output reference resolver, which is not resolving due to wtp 3.2 changes

by Rob Stryker (JIRA)

ESB project making use of output reference resolver, which is not resolving due to wtp 3.2 changes --------------------------------------------------------------------------------------------------- Key: JBIDE-6964 URL: https://jira.jboss.org/browse/JBIDE-6964 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb, JBossAS Affects Versions: 3.2.0.M1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta -- 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
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6989) Archives plugins have hard-coded version dependencies

by Rob Stryker (JIRA)

Archives plugins have hard-coded version dependencies ----------------------------------------------------- Key: JBIDE-6989 URL: https://jira.jboss.org/browse/JBIDE-6989 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.2.0.M1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta It's hard to know exactly what previous versions are affected by this, and there's also no guarantee this will fix the bug experienced by user, but its clear to me those version dependencies do not belong there. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7017) Teiid sample welcome screen is broken

by Max Andersen (JIRA)

Teiid sample welcome screen is broken ------------------------------------- Key: JBIDE-7017 URL: https://jira.jboss.org/browse/JBIDE-7017 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.M2 Reporter: Max Andersen Priority: Critical Fix For: 3.2.0.Beta installed M2 from nightly updatesite. restarted and suddenly a welcome screen appeared with a "Import Teiid sample project" Clicked it and got weird non-informative wizard with errors in it. See screenshot. Comments: 1) Couldn't we put this in Project Examples instead of in welcome view ? (or at least somehow be able to control it showing up in welcome page so dominantly?) 2) The wizard doesn't actually say what it is about...no mention of teiid or whatnot. 3) The error message is cryptic...and the project seem to be a Maven project (based on the icon). How does that work in context of JBDS and non-maven installed jboss tools ? -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7073) Project Examples Should Provide The Option To Switch To A Specified Perspective

by Dan Florian (JIRA)

Project Examples Should Provide The Option To Switch To A Specified Perspective ------------------------------------------------------------------------------- Key: JBIDE-7073 URL: https://jira.jboss.org/browse/JBIDE-7073 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Reporter: Dan Florian Assignee: Snjezana Peco I used Project Examples to import a Teiid Designer project. The "Resource" perspective was open at the time. The first thing I did was open the "Teiid Designer" perspective so that appropriate actions, views, etc. would be available while working with that example project I just imported. It would be nice if the Project Examples framework, after the project was imported, either automatically switched to, or asked the user if they wanted to switch to, a specified perspective. This specified perspective could be identified in the examples XML file. Per Max, it might "be possible to reuse/mimic new project wizards preferred perspective option." -- 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

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6825) BPEL Validator throws NPE when saving an unrelated BPEL process

by Robert (Bob) Brodt (JIRA)

BPEL Validator throws NPE when saving an unrelated BPEL process --------------------------------------------------------------- Key: JBIDE-6825 URL: https://jira.jboss.org/browse/JBIDE-6825 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Environment: All Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.x If a BPEL project contains an invalid BPEL resource that fails XML parsing, the validator will report a problem when ANY other BPEL resource in the same project is saved during editing. The Builder throws an NPE when it tries to remove error markers in imported resource (i.e. WSDLs and XSDs) - this happens in Builder.deleteMarkersInReferencialResources(). -- 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
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7051) Move new project examples file to download site

by Brian Fitzpatrick (JIRA)

Move new project examples file to download site ----------------------------------------------- Key: JBIDE-7051 URL: https://jira.jboss.org/browse/JBIDE-7051 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Brian Fitzpatrick Assignee: Nick Boldt Fix For: 3.2.0.Beta Dan Florian has created a new examples xml file for JBT 3.2 as workspace/examples/project-examples-3.2.xml The examples file is here: http://anonsvn.jboss.org/repos/jbosstools/workspace/examples/project-exam... Nick, this new examples file should be copied up to http://download.jboss.org/jbosstools/examples/ like the other project-examples xml files and then it will be accessible for testing and users. Dan - To test whether the example is configured properly, you can: 1) Download http://anonsvn.jboss.org/repos/jbosstools/workspace/examples/project-exam... locally 2) In Eclipse, go to Preferences and look for JBoss Tools->Project Examples 3) Click Add and add a new "user site" pointing to your local copy of the project examples file 4) Click OK 5) Go to Help->Project Examples. Check the "Show experimental sites" box. 6) You should now see Teiid Designer show up as a category. Expand it, select the Parts example and click Finish. I made two tweaks to the project-examples-3.2.xml file. a) I changed the name of the project in the <included-projects> tag to be "Parts Project" instead of just "Parts". The name of the exported project in the zip file (http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...) is "Parts Project" and when the XML was set to just "Parts" it couldn't find the project name in the zip. b) I removed all the other examples and just left the Teiid example. If we need 3.2-specific examples for ESB, Seam, etc., we can add them later. At this point, they other examples will come from the 3.1 xml file. -- 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

4
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 October 2010