[JBoss JIRA] Created: (JBDS-1813) EDS/Teiid issues for 5.2
by Brian Fitzpatrick (JIRA)
EDS/Teiid issues for 5.2
------------------------
Key: JBDS-1813
URL: https://issues.jboss.org/browse/JBDS-1813
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: teiid
Affects Versions: 4.1.0.GA
Reporter: Brian Fitzpatrick
Assignee: Barry LaFond
Priority: Critical
Fix For: 4.1.1
This is just a link back to the TEIIDES issues for JBDS 4.1.1. See TEIIDDES-1021 for the full list going into Teiid for JBDS 4.1.1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] (JBDS-1895) Add/Remove operations on a VDB should block other operations on the VDB
by Marc Shirley (Created) (JIRA)
Add/Remove operations on a VDB should block other operations on the VDB
-----------------------------------------------------------------------
Key: JBDS-1895
URL: https://issues.jboss.org/browse/JBDS-1895
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: teiid
Affects Versions: 4.1.0.GA
Reporter: Marc Shirley
Assignee: Barry LaFond
As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: 0
at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
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.Display.runDeferredEvents(Display.java:4066)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
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: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:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] (JBIDE-9945) Refactor the Command Recorder So That Post Processing Becomes Cleaner
by Koen Aers (Created) (JIRA)
Refactor the Command Recorder So That Post Processing Becomes Cleaner
---------------------------------------------------------------------
Key: JBIDE-9945
URL: https://issues.jboss.org/browse/JBIDE-9945
Project: Tools (JBoss Tools)
Issue Type: Task
Components: forge
Reporter: Koen Aers
Fix For: 3.3.0.M4
At this point, a CommandRecorder is responsible for keeping track of all the issued commands and do post processing after the command is executed. At the moment this is done by parsing the output stream and remembering the different commands that are executed. This should be changed in a more elegant solution:
- a CommandProcessor which keeps track of the commands by processing the 'hidden' input that comes from the runtime
- a series of PostProcessors that use the information provided in this 'hidden' input to perform the necessary post processing (such as importing project, opening editors, setting focus, etc)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9383) Remove menu item "New Business Rule (using the guided editor)" from Drools Toolbar button menu.
by Vlado Pakan (JIRA)
Remove menu item "New Business Rule (using the guided editor)" from Drools Toolbar button menu.
-----------------------------------------------------------------------------------------------
Key: JBIDE-9383
URL: https://issues.jboss.org/browse/JBIDE-9383
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.2.1.CR3
Environment: jbdevstudio-product-linux-gtk-4.1.0.v201107151650R-H633-CR3.
Reporter: Vlado Pakan
Assignee: Kris Verlaenen
Fix For: 3.2.1.Final
Attachments: DroolsMenuItemToRemove.png
This menu item has to be removed:
!DroolsMenuItemToRemove.png!
Guided Drools Rule Editor was removed from JBDS so also this menu item has to be removed from Drools Toolbar Menu because it's not running Guided Drools Rule Editor anymore. Eclipse text editor is run instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-8919) Recognize and define ESB Runtime from SOA-P product
by Vlado Pakan (JIRA)
Recognize and define ESB Runtime from SOA-P product
---------------------------------------------------
Key: JBIDE-8919
URL: https://issues.jboss.org/browse/JBIDE-8919
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.2.1.M1
Reporter: Vlado Pakan
Assignee: Snjezana Peco
When searching for runtimes (Menu Window > Preferences > JBoss Tools > JBoss Tools Runtimes) SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes.
Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04.
JBT should automatically detect ESB Runtime within SOA-P product and define it for later use.
Has to be working also with SOA-P Standalone products.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
by Brian Fitzpatrick (JIRA)
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Fix For: 3.2.2.M2
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4 server is defined as the runtime - the BPELInvoke action is not included in the OOTB action list.
I also tried explicitly adding the server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBDS-1655) Recognize and define Drools Runtime from SOA-P standalone product during installation
by Vlado Pakan (JIRA)
Recognize and define Drools Runtime from SOA-P standalone product during installation
-------------------------------------------------------------------------------------
Key: JBDS-1655
URL: https://issues.jboss.org/browse/JBDS-1655
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Affects Versions: 4.1.0.M1
Reporter: Vlado Pakan
When searching for runtimes during installation SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes when installed JBDS is run.
Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04.
JDBS should automatically detect ESB Runtime within SOA-P product during installation and define it for later use.
Has to be working also with SOA-P Standalone products.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months