September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6986) AddNextTaskNodeAction.addFreemarkerTemplateTask fails if Process Graph node is not properly selected

by Tom Fennelly (JIRA)

AddNextTaskNodeAction.addFreemarkerTemplateTask fails if Process Graph node is not properly selected ---------------------------------------------------------------------------------------------------- Key: JBIDE-6986 URL: https://jira.jboss.org/browse/JBIDE-6986 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.2.0.Beta This can happen if the little green + widget is used to add the next node but the target node is not selected in the Task Details panel. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7135) Seam Component N&N

by Max Andersen (JIRA)

Seam Component N&N ------------------ Key: JBIDE-7135 URL: https://jira.jboss.org/browse/JBIDE-7135 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Seam Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.2.0.M2 https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- 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, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6068) beanid is lost when adding a new Java Class in the Smooks editor

by Burr Sutter (JIRA)

beanid is lost when adding a new Java Class in the Smooks editor ---------------------------------------------------------------- Key: JBIDE-6068 URL: https://jira.jboss.org/jira/browse/JBIDE-6068 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Burr Sutter When adding a Java Class to the canvas, while creating a Java Mapping, you are prompted to set the required bean id field but it is lost when you finish with the pop-up dialog - it reverts back to the Java class name. Linked screencast: http://www.screencast.com/users/BurrSutter/folders/JBDS%20Feedback/media/... -- 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

15 years, 6 months

5
18
0 / 0

[JBoss JIRA] Created: (JBIDE-6792) Undo in rse editor section should reset the widgets properly

by Rob Stryker (JIRA)

Undo in rse editor section should reset the widgets properly ------------------------------------------------------------ Key: JBIDE-6792 URL: https://jira.jboss.org/browse/JBIDE-6792 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.M2 -- 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, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6863) NPE when selecting groovy script in groovy action

by Libor Zoubek (JIRA)

NPE when selecting groovy script in groovy action ------------------------------------------------- Key: JBIDE-6863 URL: https://jira.jboss.org/browse/JBIDE-6863 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.2.0.M2 Reporter: Libor Zoubek Assignee: Brian Fitzpatrick This issue is reproducible since ESB Editor 1.3. (I have updated my tools yesterday and I wonder. When I run bot tests I get ESB editor version 1.3, but when I create esb project in my workspace I get version 1.2) Steps to reproduce: 1. create esb project 2. create esb service 3. add Groovy action to service 4. navigate to groovy action in esb editor tree 5. click 'Browse' button (to select groovy script) 6. in browse dialog, select any subfolder of any .jar (This dialog should not allow you to select folder, when you are browsing for *.groovy file) and press 'Finish' 7. NPE appears in log, in editor, text field seem like change was done, but in xml file nothing changes -- 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, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6552) when attempting to launch jboss from eclipse i get this erro.

by Elhanan Maayan (JIRA)

when attempting to launch jboss from eclipse i get this erro. ------------------------------------------------------------- Key: JBIDE-6552 URL: https://jira.jboss.org/browse/JBIDE-6552 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.1 Reporter: Elhanan Maayan Assignee: Rob Stryker Priority: Minor What steps will reproduce the problem? 1. start eclipse 2. start jboss from server view 3. look at the error log -- Error Details -- Date: Tue Jun 29 08:40:56 GMT 2010 Message: Error opening console Severity: Error Product: Eclipse SDK 3.5.2.v201002111343 (org.eclipse.sdk.ide) Plugin: org.eclipse.wst.server.ui Session Data: eclipse.buildId=M20100211-1343 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=iw_IL Framework arguments: -mylyn.qcmylyn.dir.rtl -showlocation Command-line arguments: -os win32 -ws win32 -arch x86 -debug -mylyn.qcmylyn.dir.rtl -data c:\Workdir\clientworkspace\applications\ -showlocation Exception Stack Trace: java.lang.NullPointerException at org.eclipse.wst.server.ui.internal.view.servers.ShowInConsoleAction.perform(ShowInConsoleAction.java:55) at org.jboss.ide.eclipse.as.ui.console.ShowConsoleServerStateListener$1$1.run(ShowConsoleServerStateListener.java:48) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- 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, 6 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6805) Add additional templates for docbook editor.

by Maxim Areshkau (JIRA)

Add additional templates for docbook editor. -------------------------------------------- Key: JBIDE-6805 URL: https://jira.jboss.org/browse/JBIDE-6805 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.2.0.M1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: LATER Attachments: unknow-tags-in-docbook-editor.png Docbook have much more tags, than we now have supported in visual preview. For example try to open in docbook editor this page https://svn.jboss.org/repos/jbosstools/trunk/documentation/guides/Getting... . Almost all tags will be shown as unknown. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-106) JBDS40_014 Updated Guvnor plug-in for BRMS 5.1

by Isaac Rooskov (JIRA)

JBDS40_014 Updated Guvnor plug-in for BRMS 5.1 ---------------------------------------------- Key: TOOLSDOC-106 URL: https://jira.jboss.org/browse/TOOLSDOC-106 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Blocker Tracker for this issue. Status: Committed -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-115) JBDS40_040 Phone Home (Google Analytics)

by Isaac Rooskov (JIRA)

JBDS40_040 Phone Home (Google Analytics) ---------------------------------------- Key: TOOLSDOC-115 URL: https://jira.jboss.org/browse/TOOLSDOC-115 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Isaac Rooskov Assignee: Isaac Rooskov Tracker for this issue. Status: Uncommitted -> will contact Tom about scope of documentation work -- 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, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6913) Jboss Runtime recognition - improvements

by Libor Zoubek (JIRA)

Jboss Runtime recognition - improvements ---------------------------------------- Key: JBIDE-6913 URL: https://jira.jboss.org/browse/JBIDE-6913 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: integration, JBossAS Affects Versions: 3.2.0.M2 Reporter: Libor Zoubek Assignee: Snjezana Peco relating to JBIDE-6119 I ve found several things in 'Jboss Runtimes; preference page that should be improved. 1. Navigation to runtimes - When I click 'see Seam Runtime' or the others, whole preferences window get's into Filtered state and there is no way out of it. After navigating I am not able to selec any other preference page except for 'Jboss Runtimes' and the ones where I can navigate to. The only workaround is reopening whole Preferences window, which is not good. 2. Searching - I don't like the way it works. After I select directory to search in, whole 'Preferences' dialog freezes for a while (background job with progress listener should be used instead). Then, when it gets alive I can't know what runtimes were found/added. I would expect another window with search results forcing me to select runtimes I am interested in. Then these runtimes would be added. 3. Export/Import buttons do not work at all, I assume this is correct in current phase of development. -- 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, 6 months

4
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 September 2010