[JBoss JIRA] (JBDS-2337) Lack of positive/negative feedback to user when running queries
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-2337:
----------------------------------
Summary: Lack of positive/negative feedback to user when running queries
Key: JBDS-2337
URL: https://issues.jboss.org/browse/JBDS-2337
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Doc - VisualWebTools
Affects Versions: 6.0.0.Alpha2
Environment: Version: 6.0.0.Alpha2
Build id: Alpha2-v20120924-2110-B28
Build date: 20120924-2110
Reporter: Len DiMaggio
Priority: Minor
Fix For: 6.0.0.Beta1
See sequence of screenshots attached. If a user executes a bugzilla querysuccessfully, no feedback that the query was successful is displayed. The user must access the tasks view to see the query results - also - if the query fails and returns no records, no feedback is displayed, the user must access the task view to see the (empty) query results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBDS-2340) Move jbds.target to JBDS svn
by Mickael Istria (JIRA)
Mickael Istria created JBDS-2340:
------------------------------------
Summary: Move jbds.target to JBDS svn
Key: JBDS-2340
URL: https://issues.jboss.org/browse/JBDS-2340
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Build
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 6.0.0.Beta1
The jbds.target file should reside in JBDS SVN.
It must contain what we want in JBDS: latest versions of all 3rd-party dependencies.
No Birt, No GWT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (JBDS-1536) [Getting Started Guide] Typos
by Andrew Ross (JIRA)
[Getting Started Guide] Typos
-----------------------------
Key: JBDS-1536
URL: https://issues.jboss.org/browse/JBDS-1536
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: documentation
Affects Versions: 4.0.0.CR1
Reporter: Andrew Ross
Assignee: Matthew Casperson
Version: JBoss_Developer_Studio-Getting_Started_Guide-4.0-web-en-US-4.0.0-8.el5
1.1. What is JBDS?
"more pra JSPoductive reducing" -> productive?
3.2. JBoss Developer Studio Installation
"propmpted"
5.1.2. Stopping JBoss Server
"the the"
6.1.1. Start Development Database
"DataBase" (x2)
6.1.2. Create and deploy Seam Web Project
"desitination"
6.1.2. Create and deploy Seam Web Project
"worskhop" (x6)
7.2.5. Launch JSP Project
"the the"
8.7.1. Editing inputnumber.jsp page
"WYSIWIG"
"tothe"
8.9. Running the Application
"the the"
9.1. User Sites
"the the"
9.3. Quick Fixes
"dependences"
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-12070) CLONE - ArrayIndexOutOfBoundsException when opening a DSL Rule editor
by David Goldstein (JIRA)
David Goldstein created JBIDE-12070:
---------------------------------------
Summary: CLONE - ArrayIndexOutOfBoundsException when opening a DSL Rule editor
Key: JBIDE-12070
URL: https://issues.jboss.org/browse/JBIDE-12070
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Environment: - Windows XP
- Eclipse Helios build 20100617-1415, SWT version 3.650
- JBoss Drools Core build 5.1.0.v20100728-2128-H133-M2
Reporter: David Goldstein
Assignee: Kris Verlaenen
Stack trace snippet:
java.lang.ArrayIndexOutOfBoundsException: 1
at org.eclipse.swt.custom.StyledTextRenderer.calculateClientArea(StyledTextRenderer.java:230)
at org.eclipse.swt.custom.StyledText.handleResize(StyledText.java:6165)
at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5658)
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:1058)
at org.eclipse.swt.widgets.Control.WM_SIZE(Control.java:4813)
at org.eclipse.swt.widgets.Scrollable.WM_SIZE(Scrollable.java:291)
at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1653)
at org.eclipse.swt.widgets.Canvas.WM_SIZE(Canvas.java:454)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4234)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4873)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2454)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.WM_WINDOWPOSCHANGED(Control.java:4970)
at org.eclipse.swt.widgets.Canvas.WM_WINDOWPOSCHANGED(Canvas.java:460)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4244)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4873)
at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1456)
at org.eclipse.swt.widgets.Control.forceResize(Control.java:1018)
at org.eclipse.swt.widgets.ScrollBar.getThumbTrackBounds(ScrollBar.java:464)
at org.eclipse.jface.text.source.SourceViewer$RulerLayout.computeScrollArrowHeights(SourceViewer.java:217)
at org.eclipse.jface.text.source.SourceViewer$RulerLayout.getVerticalScrollArrowHeights(SourceViewer.java:196)
at org.eclipse.jface.text.source.SourceViewer$RulerLayout.layout(SourceViewer.java:155)
at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1275)
at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1261)
at org.eclipse.swt.widgets.Composite.layout(Composite.java:664)
at org.eclipse.swt.widgets.Composite.layout(Composite.java:622)
at org.eclipse.jface.text.source.CompositeRuler.layoutTextViewer(CompositeRuler.java:611)
at org.eclipse.jface.text.source.CompositeRuler.addDecorator(CompositeRuler.java:565)
at org.eclipse.jface.text.source.projection.ProjectionViewer.addVerticalRulerColumn(ProjectionViewer.java:1289)
at org.eclipse.jface.text.source.projection.ProjectionSupport.doEnableProjection(ProjectionSupport.java:310)
at org.eclipse.jface.text.source.projection.ProjectionSupport$ProjectionListener.projectionEnabled(ProjectionSupport.java:143)
at org.eclipse.jface.text.source.projection.ProjectionViewer.fireProjectionEnabled(ProjectionViewer.java:489)
at org.eclipse.jface.text.source.projection.ProjectionViewer.enableProjection(ProjectionViewer.java:537)
at org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation(ProjectionViewer.java:1441)
at org.drools.eclipse.editors.AbstractRuleEditor.createPartControl(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:241)
at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:325)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:211)
at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:308)
at org.drools.eclipse.dsl.editor.DSLRuleEditor2.addPages(Unknown Source)
at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
The issue seems to be platform-dependent, as I'm not getting any exceptions in a gtk.linux.x86 build.
Some debugging revealed that StyledTextRenderer's internal data structures assume a different number of lines present than what content.getLineCount() returns in calculateClientArea(); these two values are usually kept in sync with the use of TextChangeListeners. I think that because of TransformedDocument's lazy update mechanism, new state can be returned to the renderer without firing a corresponding text change event first.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-12506) Open Action Editor on doubleclick on the ScriptTask
by Jozef Chocholáček (JIRA)
Jozef Chocholáček created JBIDE-12506:
-----------------------------------------
Summary: Open Action Editor on doubleclick on the ScriptTask
Key: JBIDE-12506
URL: https://issues.jboss.org/browse/JBIDE-12506
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: BPEL, bpm, jbpm
Affects Versions: 3.3.1
Reporter: Jozef Chocholáček
Assignee: Robert (Bob) Brodt
Opening the Action Editor on doubleclick on a ScriptTask would spare a lot of time - to find the "..." icon at the end of the "Action" property line in the Properties tab is, ehm, uncomfortable (to stay decent).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month