September 2010 - jbosstools-issues

[JBoss JIRA] Created: (TOOLSDOC-78) WS guide restructuring

by Svetlana mukhina (JIRA)

WS guide restructuring ----------------------- Key: TOOLSDOC-78 URL: https://jira.jboss.org/browse/TOOLSDOC-78 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Sub-task Components: Documentation Affects Versions: 3.0.0.GA Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 3.0.1.GA - provide guide structure (as smooks guide) - restructure the guide - update if necessary -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6744) ArrayIndexOutOfBoundsException when opening a DSL Rule editor

by András Péteri (JIRA)

ArrayIndexOutOfBoundsException when opening a DSL Rule editor ------------------------------------------------------------- Key: JBIDE-6744 URL: https://jira.jboss.org/browse/JBIDE-6744 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.M2 Environment: - Windows XP - Eclipse Helios build 20100617-1415, SWT version 3.650 - JBoss Drools Core build 5.1.0.v20100728-2128-H133-M2 Reporter: András Péteri 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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

8
13
0 / 0

[JBoss JIRA] Created: (JBIDE-7028) New ODE deployment descriptor wizard should create deploy.xml file instead of bpel-deploy.xml

by Gary Brown (JIRA)

New ODE deployment descriptor wizard should create deploy.xml file instead of bpel-deploy.xml --------------------------------------------------------------------------------------------- Key: JBIDE-7028 URL: https://jira.jboss.org/browse/JBIDE-7028 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Gary Brown Fix For: 3.2.0.Beta Currently the ODE deployment descriptor new file wizard creates the descriptor in a file called 'bpel-deploy.xml'. This should be changed to create a file called 'deploy.xml' instead. However, the ODE deployment descriptor editor should support both bpel-deploy.xml and deploy.xml file names. -- 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

13 years, 9 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5448) No CA path proposals for img src="" for whatsnew project

by Maxim Areshkau (JIRA)

No CA path proposals for img src="" for whatsnew project -------------------------------------------------------- Key: JBIDE-5448 URL: https://jira.jboss.org/jira/browse/JBIDE-5448 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.1.0.GA Attachments: Screenshot.png #1 import https://svn.jboss.org/repos/jbosstools/trunk/documentation/whatsnew project #2 open page vpe-news-3.1.0.CR1.html #3 set cursor in 63 <img src="images/3.0|" .../> ASSERT PATH proposals should be in CA -- 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

13 years, 9 months

4
19
0 / 0

[JBoss JIRA] Created: (JBIDE-6178) releng update site, feature naming conventions

by Darryl Miles (JIRA)

releng update site, feature naming conventions ---------------------------------------------- Key: JBIDE-6178 URL: https://jira.jboss.org/jira/browse/JBIDE-6178 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: updatesite Affects Versions: 3.1.0.GA Reporter: Darryl Miles Priority: Minor Please consider the impact of users using the "All Update Site" view when installing JBoss plugins. Some rules to consider: 1) If JBoss creates a new top-level group (which consists entirely of JBoss features) then that top-level name should begin with the word "JBoss". 2) If JBoss reuses a top-level group which belongs to another vendor (for which JBT is built on top of, for example BIRT/Maven/DTP) then you can reuse the top-level group name of the outside vendor, but ensure your features underneath are prefixed with the word "JBoss"." In enclose a screen grab from 3.1.0.GA which indicates the discrepancy; BIRT is following the above rules, but "Maven Support" is not (and also "Data Services" top level group is not). The "All in one JBoss" top-level group doesn't really need to follow this convention, since the top level group clearly indicates it is from JBoss and entirely contains JBoss features and those features are a duplicated entrypoint for installation (i.e. each feature also exist somewhere else in the "features to install" tree view). The ambigiouty is over such names as "Maven Support" and "Data Services" in the context of the "all update site view" from the drop-down filter at the top of the page. -- 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

13 years, 9 months

10
26
0 / 0

[JBoss JIRA] Created: (JBIDE-2707) Extend seam functionality to cover webbeans core

by Max Rydahl Andersen (JIRA)

Extend seam functionality to cover webbeans core ------------------------------------------------ Key: JBIDE-2707 URL: https://jira.jboss.org/jira/browse/JBIDE-2707 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER We need to find a way to have Seam 3/webbeans support; hopefully using the exisiting infrastructure but updated to work with webbeans annotation based way of working. e.g. scopes are not limited, look for @ScopeType in classpath to find them -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6608) Ability to remove drools nature from project

by Libor Zoubek (JIRA)

Ability to remove drools nature from project -------------------------------------------- Key: JBIDE-6608 URL: https://jira.jboss.org/browse/JBIDE-6608 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: drools Affects Versions: 3.1.0.GA Reporter: Libor Zoubek Assignee: Kris Verlaenen Regarding to http://community.jboss.org/message/552490 at this time, there is no possibility to remove drools "nature" (as it is probably not the nature in sense of eclipse nature) We should be able to remove drools from project. Menu item 'Convert to drools project' should be called 'Add drools nature' and when a project has a drools nature it should be called 'Remove drools nature'. Maybe it would be good, not to have 'Convert to drools project' menu item in main context menu, but move it into 'Configure' submenu -- 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

13 years, 10 months

7
17
0 / 0

[JBoss JIRA] Created: (JBIDE-6958) Restore build results index.html page

by Denis Golovin (JIRA)

Restore build results index.html page ------------------------------------- Key: JBIDE-6958 URL: https://jira.jboss.org/browse/JBIDE-6958 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Assignee: Nick Boldt Priority: Critical Fix For: 3.2.0.Beta Build results page should look the same as we had in 3.1.X releases. Probably we need to mention not just required drivers here but update sites. It should contain zipped update sites for separate components and aggregated update site. -- 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

13 years, 10 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4442) Improve branding/skinning of What's New / N&N pages

by Nick Boldt (JIRA)

Improve branding/skinning of What's New / N&N pages --------------------------------------------------- Key: JBIDE-4442 URL: https://jira.jboss.org/jira/browse/JBIDE-4442 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Nick Boldt Assignee: Max Rydahl Andersen The N&N pages (http://docs.jboss.org/tools/whatsnew/)are very plain. At the very least, we could introduce some colour (as used on www.jboss.org/tools/ or http://download.jboss.org/jbosstools/updates/nightly/trunk/ ?) and perhaps use this banner: http://www.jboss.org/theme/images/banners/tools-banner.png Beyond that, we ought to have persistent navigation for downloads, update sites, browsing/reporting JIRAs, movies, docs, etc. so people can more easily find other useful resources. I'd be happy to take a crack at editing these pages if you let me know where they live in SVN. Are they generated by template? Seam? XSLT? -- 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

13 years, 10 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-6644) Offer quick fixes for CDI validations

by Pete Muir (JIRA)

Offer quick fixes for CDI validations ------------------------------------- Key: JBIDE-6644 URL: https://jira.jboss.org/browse/JBIDE-6644 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Pete Muir Assignee: Max Rydahl Andersen -- 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

13 years, 10 months

5
12
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 2010