July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (TOOLSDOC-198) JBDS50_0031: Hibernate 3 documentation

by Isaac Rooskov (JIRA)

JBDS50_0031: Hibernate 3 documentation -------------------------------------- Key: TOOLSDOC-198 URL: https://issues.jboss.org/browse/TOOLSDOC-198 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Hibernate Tools Reference Guide Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0031: Hibernate 3 Current status: Committed Description: New documentation for Hibernate 3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-197) JBDS50_0030: Hibernate 4 documentation

by Isaac Rooskov (JIRA)

JBDS50_0030: Hibernate 4 documentation -------------------------------------- Key: TOOLSDOC-197 URL: https://issues.jboss.org/browse/TOOLSDOC-197 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Hibernate Tools Reference Guide Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0030: Hibernate 4 Current status: Uncommitted Description: New documentation for Hibernate 4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8553) Generation of Arquillian @Deployment method

by Nicklas Karlsson (JIRA)

Generation of Arquillian @Deployment method ------------------------------------------- Key: JBIDE-8553 URL: https://issues.jboss.org/browse/JBIDE-8553 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Nicklas Karlsson Trying to assemble a minimal Arquillian test archive can be lots of work when the dependencies add up and you only notice the problems at deployment time. I would love to have a feature that would create the @Deployment method for you. It could (in theory) work like this: Somewhere in your test class from the context menu you could a) generate a new @Deployment method if none exist or b) add to the deployment method if it exists You could then pick one or more files to start from. The imports and references would be analyzed and a minimal set of classes would be added to the deployment archive code generated. If run again, the new tree would be merged with the existing one. Then comes the tricky part. Analyze the archives on the classpath and dig out which archives provide which classes. Further use Aether or some other maven api to find out the dependecy tree until all jars to be included are discovered. Example: Foo.java references Bar.java Bar.java references Tar.java Tar.java references Worksheet.class Foo.java is included in the generated @Deployment Bar.java is included Tar.java is included jxl.jar from the local repo is included since it is determined from the pom.xml through further investigation to provide Worksheet.class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8064) Variable initializer does not generate content for messages which use type attribute instead of element to declare the part.

by Marek Baluch (JIRA)

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch If a message is declared the following way: <message name="moderateRequestMessage"> <part name="moderateRequest" type="tns:complexType"/> </message> or <message name="simpleResponseMessage"> <part name="payload" type="xsd:string"/> </message> In the second case there's no need to generate any content. The assignment will work anyway. In these cases the variable initializer should not be triggered. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

6
17
0 / 0

[JBoss JIRA] Created: (JBIDE-8514) Create xml schema for project-examples.xml files

by Snjezana Peco (JIRA)

Create xml schema for project-examples.xml files ------------------------------------------------ Key: JBIDE-8514 URL: https://issues.jboss.org/browse/JBIDE-8514 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.2.0.M1 Reporter: Snjezana Peco Assignee: Snjezana Peco -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
14
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-8905) Create Property Alias dialog not displaying XPath Query editor control

by Robert (Bob) Brodt (JIRA)

Create Property Alias dialog not displaying XPath Query editor control ---------------------------------------------------------------------- Key: JBIDE-8905 URL: https://issues.jboss.org/browse/JBIDE-8905 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Final Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.3.0.Final When creating correlations, the "Create Property Alias" dialog does not allow you to select an Expression Language and does not open an XPath Query editor control. This was working at some point... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
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: (JBDS-1606) offline hudson job config management

by Nick Boldt (JIRA)

offline hudson job config management ------------------------------------ Key: JBDS-1606 URL: https://issues.jboss.org/browse/JBDS-1606 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 5.0.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt 1. back up hudson config.xml files to svn 2. enable tooling for synching local config.xml files to remote server (HTTP POST via RSE or custom app or cmdline maven script) 3. config.xml editor in Eclipse? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8974) provide composite*.xml

by Nick Boldt (JIRA)

provide composite*.xml ---------------------- Key: JBIDE-8974 URL: https://issues.jboss.org/browse/JBIDE-8974 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M2 create clone of http://download.jboss.org/jbosstools/builds/staging/_composite_/3.3.indigo/* with relative paths to dirs on disk (~/trunk/jmx/site/target/site/) so that locally built files can be used to test installation. Place this in ~/trunk/build/aggregate/site/ ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
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