December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7392) "New Seam Project" dialog wrongly validates empty project name

by Daniel Azarov (JIRA)

"New Seam Project" dialog wrongly validates empty project name -------------------------------------------------------------- Key: JBIDE-7392 URL: https://jira.jboss.org/browse/JBIDE-7392 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Beta1 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.2.0.Beta2 It should be something better then "EJB project '' already exists. Please select other name for new Seam project." in case of empty project name. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-122) Missing N&N for Smooks in JBT 3.2.Beta1

by Jiri Peterka (JIRA)

Missing N&N for Smooks in JBT 3.2.Beta1 --------------------------------------- Key: TOOLSDOC-122 URL: https://jira.jboss.org/browse/TOOLSDOC-122 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Smooks Affects Versions: 3.2.0.Final Reporter: Jiri Peterka Assignee: Isaac Rooskov There are news like Direct mapping without middle Java mapping, ... in Smooks and it's missing N&N for JBT 3.2.0.Beta1 in here http://docs.jboss.org/tools/whatsnew/ It should be added -- 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, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7310) Smooks Editor throws NPE when trying to create an empty connection list

by Brian Fitzpatrick (JIRA)

Smooks Editor throws NPE when trying to create an empty connection list ----------------------------------------------------------------------- Key: JBIDE-7310 URL: https://jira.jboss.org/browse/JBIDE-7310 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.2.0.Beta2 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.0.Beta2 While doing some testing, I discovered that if the direct source to target tried to map between the input and output and no connections were found, it would throw an NPE. -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7577) Seam Runtimes preference isn't imported correctly after SeamRuntimeRecognizer is created

by Snjezana Peco (JIRA)

Seam Runtimes preference isn't imported correctly after SeamRuntimeRecognizer is created ---------------------------------------------------------------------------------------- Key: JBIDE-7577 URL: https://jira.jboss.org/browse/JBIDE-7577 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Beta1 Reporter: Snjezana Peco Assignee: Alexey Kazakov Steps to reproduce: - start Eclipse - create Seam Runtimes - call File>Export>Preferences - choose the "JBoss Runtimes" preferences (or Export All Preferences) - export the preferences to a file (test.epf) - restart Eclipse in a new workspace - open the Seam perspective - open Window>Preferences>JBoss Tools>Seam and make sure that there aren't any Seam Runtime (the Seam preference page will instantiate SeamRuntimeRecognizer) - close the Preferences dialog - call File>Import>Preferences - choose the "JBoss Runtimes" preferences (or Import All Preferences) - point to the file you previously exported (test.epf) - import the preferences - open Window>Preferences>JBoss Tools>Seam There isn't any Seam Runtime. If you look at test.epf, you can see that the Seam Runtimes preference (/instance/org.jboss.tools.seam.core/org.jboss.tools.seam.core.runtime.list) is exported correctly. The problem is that SeamRuntimeManager, when it is once created, ignores the change to the Seam Runtimes preference. Attached is a patch. Restart Eclipse and Seam runtimes will appear (SeamRuntimeRecognizer is created again). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7615) builtin seam components not detected

by Marcel Å ebek (JIRA)

builtin seam components not detected ------------------------------------ Key: JBIDE-7615 URL: https://jira.jboss.org/browse/JBIDE-7615 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Beta1 Reporter: Marcel Å ebek Assignee: Alexey Kazakov The built-in seam components which are not mentioned in the custom components.xml are not recognized by JBoss Tools (eg. org.jboss.seam.core.interpolator). Thus, unknown context variable name warnings are reported when trying to inject such components. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7054) FreemarkerTemplateNodeGraphicalModel.isCollectionConnection doesn't take source collections into account

by Tom Fennelly (JIRA)

FreemarkerTemplateNodeGraphicalModel.isCollectionConnection doesn't take source collections into account -------------------------------------------------------------------------------------------------------- Key: JBIDE-7054 URL: https://jira.jboss.org/browse/JBIDE-7054 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.2.0.CR1 A collection connection should be made if the source node is a collection node. Currently only takes the target into account, but should take both into account. Use the attached XML sample and XSD in JBIDE-7047. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7724) BPEL Editor throws SWTException on startup because color registry is not initialized

by Robert (Bob) Brodt (JIRA)

BPEL Editor throws SWTException on startup because color registry is not initialized ------------------------------------------------------------------------------------ Key: JBIDE-7724 URL: https://jira.jboss.org/browse/JBIDE-7724 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Beta2 Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Priority: Blocker Fix For: 3.2.0.Beta2 This is a threading issue: during startup, the color and image registries are initialized in the CommonUIPlugin, but two (or more) threads are using the color registry when the editor is started; one of these threads initiates the registry creation and is interrupted by the other thread which attempts to use it before it has been properly initialized. The result is that an SWT exception is thrown. Stack trace follows: org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null) at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3527) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) Caused by: java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:4064) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.graphics.GC.setBackground(GC.java:3073) at org.eclipse.bpel.common.ui.tray.TraySash$TrayTextureCanvas$1.paintControl(TraySash.java:71) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:223) 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.Control.gtk_expose_event(Control.java:2781) at org.eclipse.swt.widgets.Composite.gtk_expose_event(Composite.java:701) at org.eclipse.swt.widgets.Canvas.gtk_expose_event(Canvas.java:167) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1739) 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._gdk_window_process_all_updates(Native Method) at org.eclipse.swt.internal.gtk.OS.gdk_window_process_all_updates(OS.java:5327) at org.eclipse.swt.widgets.Display.update(Display.java:4325) at org.eclipse.ui.internal.LegacyAnimationFeedback.renderStep(LegacyAnimationFeedback.java:60) at org.eclipse.ui.internal.AnimationEngine.updateDisplay(AnimationEngine.java:134) at org.eclipse.ui.internal.AnimationEngine$1.run(AnimationEngine.java:122) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 23 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7231) usage reporting reports an illegal character

by Andre Dietisheim (JIRA)

usage reporting reports an illegal character -------------------------------------------- Key: JBIDE-7231 URL: https://jira.jboss.org/browse/JBIDE-7231 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: usage Affects Versions: 3.2.0.M2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 If you look at the reports in Google Analytics account, that our usage reporting hits, you'll notice a special character. it was in the "Keyword" in older versions and now is in the "User Defined Value" since we report the Linux Distro (see attached screenshot). We need to remove that. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7268) usage reporting does report ubuntu linux as debian

by Andre Dietisheim (JIRA)

usage reporting does report ubuntu linux as debian -------------------------------------------------- Key: JBIDE-7268 URL: https://jira.jboss.org/browse/JBIDE-7268 Project: Tools (JBoss Tools) Issue Type: Bug Components: usage Affects Versions: 3.2.0.M2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 The usage reporting plugin currently recognizes Ubuntu linux as debian. This is wrong and should be corrected. The reason is the following: - the recogintion code checks the presence of certain files: /etc/lsb-release for Ubuntu and /etc/debian_version for Debian. - Debian is checked before Ubuntu, so it finds /etc/debian_version and thinks the Ubuntu distro is a debian distro. - Furthermore this file contains no numerical verison (contains "squeeze/sid") in it, so Ubuntu distros get reported as Debian without version. -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7256) usage reporting has message keys that are not used any more, they should be removed

by Andre Dietisheim (JIRA)

usage reporting has message keys that are not used any more, they should be removed ----------------------------------------------------------------------------------- Key: JBIDE-7256 URL: https://jira.jboss.org/browse/JBIDE-7256 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Andre Dietisheim There are message keys left, that are not used any longer in <snip> org.jboss.tools.usage.tracker.internal/message.properties </snip> -- 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, 4 months

3
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 December 2010