April 2010 - jbosstools-issues - Jboss List Archives

[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, 7 months

6
15
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, 7 months

4
10
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, 7 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, 7 months

4
18
0 / 0

[JBoss JIRA] Created: (JBIDE-6137) JBoss ESB Runtimes preference page Version: label issue

by Brian Fitzpatrick (JIRA)

JBoss ESB Runtimes preference page Version: label issue ------------------------------------------------------- Key: JBIDE-6137 URL: https://jira.jboss.org/jira/browse/JBIDE-6137 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Reporter: Brian Fitzpatrick Assignee: Denny Xu Priority: Minor Fix For: 3.2.next, 3.1.x While testing the patch for JBIDE-5522, I noticed this issue with the column label on the JBoss ESB Runtimes preference page. The middle column is labeled "Version:" and it doesn't really need a colon and should just be "Version". -- 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, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5912) Error when moving jBPM process package in the project

by Jiri Peterka (JIRA)

Error when moving jBPM process package in the project ----------------------------------------------------- Key: JBIDE-5912 URL: https://jira.jboss.org/jira/browse/JBIDE-5912 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.CR2 Environment: JBDS 3.0.0 CR2 #173 Reporter: Jiri Peterka Fix For: 3.1.0.CR3 Steps: 1. Create jbpm3 process definition in the root of the project 2. Move (drag&drop) process definition package into src/main/jpdl 3. Edit process in GPD and save. ERROR: Save Failed, processimage.jpg is still expected in root directory (see 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, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6104) Save Local Server and Deployment Server Settings

by Rafael Liu (JIRA)

Save Local Server and Deployment Server Settings ------------------------------------------------ Key: JBIDE-6104 URL: https://jira.jboss.org/jira/browse/JBIDE-6104 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Reporter: Rafael Liu Usually Save Local Server and Deployment Server Settings doesn't change, but today we have to retype these addresses every time the JPDL is reopened. It would make developer's life easier to save those. -- 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, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3337) Exception is occured when delete Seam Ear web project

by Anton Klimkovich (JIRA)

Exception is occured when delete Seam Ear web project ----------------------------------------------------- Key: JBIDE-3337 URL: https://jira.jboss.org/jira/browse/JBIDE-3337 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.cr1 Reporter: Anton Klimkovich Attachments: exception.txt EXECUTE: Create seam EAR web project EXECUTE: Select all projects in Package Explorer View EXECUTE: Delete with content from workspace FAILURE: Exception is occured after deleting. -- 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, 7 months

5
18
0 / 0

[JBoss JIRA] Created: (JBIDE-6227) JMX Core Tests fails to find example project's .project file

by Nick Boldt (JIRA)

JMX Core Tests fails to find example project's .project file ------------------------------------------------------------ Key: JBIDE-6227 URL: https://jira.jboss.org/jira/browse/JBIDE-6227 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 3.2.next Reporter: Nick Boldt Running JMX tests on local or in Hudson, I get: [INFO] --- maven-osgi-test-plugin:0.9.0-SNAPSHOT:test (default-test) @ org.jboss.tools.jmx.core.test --- [INFO] Expected eclipse log file: /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work/data/.metadata/.log [INFO] Command line: /bin/sh -c cd /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test && /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86 -jar /home/nboldt/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.0.201.R35x_v20090715/org.eclipse.equinox.launcher-1.0.201.R35x_v20090715.jar -data /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work/data -dev file:/home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/dev.properties -install /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work -configuration /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work/configuration -application org.codehaus.tycho.surefire.osgibooter.uitest -testproperties /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/surefire.properties -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.sdk.ide ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.tools.jmx.core.test.JMXCoreAllTests Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.106 sec <<< FAILURE! testConnection(org.jboss.tools.jmx.core.test.DefaultProviderTest) Time elapsed: 0.009 sec <<< ERROR! org.eclipse.core.internal.resources.ResourceException()[567]: java.io.FileNotFoundException: /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work/data/JMX_EXAMPLE/.project (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:137) at org.eclipse.core.internal.resources.ProjectDescriptionReader.read(ProjectDescriptionReader.java:626) at org.eclipse.core.internal.resources.Workspace.loadProjectDescription(Workspace.java:1478) at org.jboss.tools.jmx.core.test.util.TestProjectProvider.importExistingProject(TestProjectProvider.java:109) at org.jboss.tools.jmx.core.test.util.TestProjectProvider.init(TestProjectProvider.java:97) at org.jboss.tools.jmx.core.test.util.TestProjectProvider.<init>(TestProjectProvider.java:65) at org.jboss.tools.jmx.core.test.DefaultProviderTest.testConnection(DefaultProviderTest.java:80) Results : Tests in error: testConnection(org.jboss.tools.jmx.core.test.DefaultProviderTest) Tests run: 7, Failures: 0, Errors: 1, Skipped: 0 ------------ Did some digging and it seems that the .../jmx/tests/org.jboss.tools.jmx.core.test/target/work/data/JMX_EXAMPLE/ folder is empty. However, the content that's supposed to be checked out into that dir is definitely in the target/org.jboss.tools.jmx.core.test-1.1.0-SNAPSHOT.jar jar, so I would think the problem is in how the test is doing its unpacking, rather than how the jar is being built. -------- Same error in Hudson: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-tycho-mod... To run test in Hudson: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-tycho-mod... -> Build Now -> only need these components to be built: tests,common,jmx; may need to use -Dbuild.if.sources.unchanged=true flag too. To run test locally from a fresh checkout: cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/ or cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/branches/modular_build/build/ then cd /tmp/build; ant -DCOMPONENTS=tests,common,jmx -- 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, 7 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-5933) Validation of XHTML files in Seam 2.2 project runs very slow

by Dominik Pospisil (JIRA)

Validation of XHTML files in Seam 2.2 project runs very slow ------------------------------------------------------------ Key: JBIDE-5933 URL: https://jira.jboss.org/jira/browse/JBIDE-5933 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR2 Reporter: Dominik Pospisil Validation of XHTML files in Seam 2.2 runs very slow. Project containing ~100 entities takes almost half an hour. Seems that resources required for validation are downloaded for each file over and over again. Without internet connectivity, validation is stucked. -- 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, 7 months

6
19
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 April 2010