September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1034) ESB Node Properties for Input/Output variables grows larger than panel when panel is resized.

by Aaron Pestel (JIRA)

ESB Node Properties for Input/Output variables grows larger than panel when panel is resized. --------------------------------------------------------------------------------------------- Key: JBDS-1034 URL: https://jira.jboss.org/jira/browse/JBDS-1034 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: JBDS 3.0 M4 Reporter: Aaron Pestel Priority: Minor To reproduce: 1.) Drag an ESB Service node on jBPM Diagram Pallette 2.) Click on (select) the new ESB Service node 3.) Select the Properties view tab 4.) Click the ESB subtab of the ESB Properties panel 5.) Click the "Input" subsubtab of the ESB subtab of the ESB Properties panel 6.) Grab the left edge of the "Properties" panel and move it to the left (increasing the width of the Properties panel) 7.) Note that the ESB Input sub panel grows wide faster than its Properties panel container such that you can no longer see the "Add" button in the ESB Input sub panel without scrolling. -- 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

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-5910) jBPM processdefinition.xml renaming causes complete physical removal of process definition and related files

by Jiri Peterka (JIRA)

jBPM processdefinition.xml renaming causes complete physical removal of process definition and related files ------------------------------------------------------------------------------------------------------------ Key: JBIDE-5910 URL: https://jira.jboss.org/jira/browse/JBIDE-5910 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.CR2 Environment: JBDS 3.0.0 CR2 #173, Linux 64, Linxu 64, Sun JDK 1.6 Reporter: Jiri Peterka Fix For: 3.1.0.CR3 Steps to reproduce: 1. Create jBPM3 project 2. Create jbpm Process 3. Click on processdefinition.xml -> Refactor -> Rename and change to processdefinition2.xml ERROR: Entire process package with all files is physically removed from filesystem -- 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

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6468) Enablement of JPA Generate Annotations takes way too long

by Max Rydahl Andersen (JIRA)

Enablement of JPA Generate Annotations takes way too long --------------------------------------------------------- Key: JBIDE-6468 URL: https://jira.jboss.org/browse/JBIDE-6468 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.1 Reporter: Max Rydahl Andersen Assignee: Vitali Yemialyanchyk Priority: Blocker Fix For: 3.1.2 the code in JPAMapToolActionDelegate.setEnabled is collecting all compilationunits instead of just looking at subtype. When JBoss is hanging; it appears to be in the CompilationUnit Collector code - which is what we are seeing with Process Monitor where it is scanning the entire Workspace (I suspect). at org.hibernate.eclipse.jdt.ui.internal.jpa.collect.CompilationUnitCollector.addCompilationUnit(CompilationUnitCollector.java:86) at org.hibernate.eclipse.jdt.ui.internal.jpa.collect.CompilationUnitCollector.processJavaElements(CompilationUnitCollector.java:153) at org.hibernate.eclipse.jdt.ui.internal.jpa.collect.CompilationUnitCollector.processJavaElements(CompilationUnitCollector.java:168) at org.hibernate.eclipse.jdt.ui.internal.jpa.collect.CompilationUnitCollector.processJavaElements(CompilationUnitCollector.java:135)  JBoss DevStudio is unresponsive at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActor.processJavaElements(JPAMapToolActor.java:333) at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActionDelegate.setEnabled(JPAMapToolActionDelegate.java:101) at org.eclipse.ui.internal.handlers.HandlerProxy.setEnabled(HandlerProxy.java:233) at org.eclipse.core.commands.Command.setEnabled(Command.java:857) at org.eclipse.ui.menus.CommandContributionItem.isEnabled(CommandContributionItem.java:918) -- 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
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4717) JBoss Portlet facet is available only when there is no runtime selected

by Denis Golovin (JIRA)

JBoss Portlet facet is available only when there is no runtime selected ----------------------------------------------------------------------- Key: JBIDE-4717 URL: https://jira.jboss.org/jira/browse/JBIDE-4717 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.1.GA Reporter: Denis Golovin Assignee: Snjezana Peco Fix For: 3.0.2.GA -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-1183) JBDS ESB editor supports subset of NotifyEmail properties

by Len DiMaggio (JIRA)

JBDS ESB editor supports subset of NotifyEmail properties --------------------------------------------------------- Key: JBDS-1183 URL: https://jira.jboss.org/jira/browse/JBDS-1183 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Program Affects Versions: 3.0.0.GA Environment: JBDS 3.0 Reporter: Len DiMaggio Attachments: Screenshot.png See: http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/rosetta/s... The full set of parameters is: * <target class="NotifyEmail" * host="localhost" * port="8801" * username="smtpUsername" * password="smtpPassword" * auth="true" * from="person(a)somewhere.com" * sendTo="person(a)elsewhere.com" * subject="theSubject"> * msgAttachmentName="theSubject"> * <attachment>attachThisFile.txt</attachment> * </target> The ESB editor supports: <target class="NotifyEmail" from="other(a)somewhere.com" sendTo="someone(a)somewhere.com" subject="test123"/> Other properties entered in the source view are removed when a change is made in the tree view. See attached screenshot. -- 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

6
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6502) Endless recursion for some improperly formed project archives

by Rob Stryker (JIRA)

Endless recursion for some improperly formed project archives ------------------------------------------------------------- Key: JBIDE-6502 URL: https://jira.jboss.org/browse/JBIDE-6502 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.1.1 Reporter: Rob Stryker Assignee: Rob Stryker Priority: Critical Fix For: 3.1.2, 3.2.0.M1 On some improperly formed archives, endless recursion is possible. In this case specifically, if the output file also matches a fileset inside that archive, recursion occurs unchecked. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4331) Exception when adding ESB library to class path

by Vincent Girard-Reydet (JIRA)

Exception when adding ESB library to class path ----------------------------------------------- Key: JBIDE-4331 URL: https://jira.jboss.org/jira/browse/JBIDE-4331 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.1.GA, 3.0.0.GA Environment: eclipse.buildId=M20090211-1700 java.version=1.6.0_12 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR Command-line arguments: -os win32 -ws win32 -arch x86 -clean Windows XP SP2 Reporter: Vincent Girard-Reydet Attachments: details.log When I want to add a ESB library to the buildpath of a ESB project (right-click on project -> Properties... -> Java Build Path -> Add Library... -> Jboss ESB library ), nothing happens after clicking on the "Next" button. When switching to the PDE development perspective, I see a lot of errors, some of them beeing related to JBossESB tools. I must precise that the ESB libraries are correctly added to the project's build path when I create a new ESB project. But if I want to change the ESB library, or add a dependency to an ESB library to any project (including non-ESB projects), I got systematically this exception. Please see the log in attachment for the full Eclipse log. I captured it right after the exception (got the problem, switched to the PDE perspective and exported the log). -- 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

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6516) wrong property name in SOAPClient

by jarkko Lietolahti (JIRA)

wrong property name in SOAPClient --------------------------------- Key: JBIDE-6516 URL: https://jira.jboss.org/browse/JBIDE-6516 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: esb Reporter: jarkko Lietolahti Assignee: Brian Fitzpatrick Currently the JBoss Tools ESB editor generates "wrong" XML when editing SOAPClient action: <actions> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="test"> <property name="wsdl" value="test"/> <property name="operation" value="testOperation"/> </action> </actions> correct xml: <actions> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="test"> <property name="wsdl" value="test"/> <property name="soapAction" value="testOperation"/> </action> </actions> -- 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
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5078) Studio does not start correctly afer VPE editor was opened in previous session

by Daniel Azarov (JIRA)

Studio does not start correctly afer VPE editor was opened in previous session ------------------------------------------------------------------------------ Key: JBIDE-5078 URL: https://jira.jboss.org/jira/browse/JBIDE-5078 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M3 Reporter: Daniel Azarov Priority: Critical Testcase: 1. Open Studio with new workspace 2. Create jsf kick start project 3. Open WebContent/index.jsp 4. Close Studio 5. Open Studio again FAIL: org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use] at org.eclipse.swt.SWT.error(SWT.java:3910) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:471) at org.eclipse.swt.browser.Browser.<init>(Browser.java:119) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:87) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$10.<init>(MozillaEditor.java:521) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:521) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:911) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:210) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:400) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271) at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1417) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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

9
34
0 / 0

[JBoss JIRA] Created: (JBIDE-3968) Create unittests for dali integration

by Max Rydahl Andersen (JIRA)

Create unittests for dali integration ------------------------------------- Key: JBIDE-3968 URL: https://jira.jboss.org/jira/browse/JBIDE-3968 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Priority: Blocker Fix For: 3.0.1.GA, 3.1.0 While fixing JBIDE-3960 I wanted to verify my fixes did not break anything but I had no way of verifying this except tiny manual tests to be ready for GA. I also believe if we had had any trivial tests they would had prevented JBIDE-3960 since it would have showed up instantly. We need to add tests for the Dali integration, especially when we have funky code like reflection for Dali 2.1 and Dali 2.0 -- 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

4
18
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