November 2009 - jbosstools-issues

[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: (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-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

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

5
18
0 / 0

[JBoss JIRA] Created: (JBIDE-4088) Can workspace directories with existing projects not be opened if they do not have the right signature.

by Jim Tyrrell (JIRA)

Can workspace directories with existing projects not be opened if they do not have the right signature. ------------------------------------------------------------------------------------------------------- Key: JBIDE-4088 URL: https://jira.jboss.org/jira/browse/JBIDE-4088 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jim Tyrrell -- 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
15
0 / 0

[JBoss JIRA] Created: (JBIDE-3706) Incorrect insertion using a4j:include

by Yura Zhishko (JIRA)

Incorrect insertion using a4j:include ------------------------------------- Key: JBIDE-3706 URL: https://jira.jboss.org/jira/browse/JBIDE-3706 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.0.0.CR2 Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) Import attached file from JBIDE-3705 2) Go to Ajax2.jsp and find a4j:include 3) Run project on server compare visual viewing in VPE to server side RESULT: VPE inserts page from new line, but browsers insert components and tags from included page in one line after last component before a4j:include -- 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
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5198) Add proposals for attributes of seam mail tags to CA

by Yura Zhishko (JIRA)

Add proposals for attributes of seam mail tags to CA ---------------------------------------------------- Key: JBIDE-5198 URL: https://jira.jboss.org/jira/browse/JBIDE-5198 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.0.CR1 Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Minor 1) Insert next code into source path <m:message xmlns="http://www.w3.org/1999/xhtml" xmlns:m="http://jboss.com/products/seam/mail" xmlns:h="http://java.sun.com/jsf/html"> <m:from name="Peter" address="yzhishko(a)exadel.com" /> <m:to name="Yura Zhishko">yzhishko(a)mail.ru</m:to> <m:subject>Try out Seam!</m:subject> <m:attachment/> <m:body> <h:outputText value="Dear Yura" />, You can try out Seam by visiting <a href="http://labs.jboss.com/jbossseam">http://labs.jboss.com/jbossseam</a>. Regards, Pete </m:body> </m:message> 2) Select any tag, and try to add attribute using CA RESULT: There are no CA proposals for attributes. -- 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-5231) Add proposals for attributes of seam-pdf tags to CA

by Yura Zhishko (JIRA)

Add proposals for attributes of seam-pdf tags to CA --------------------------------------------------- Key: JBIDE-5231 URL: https://jira.jboss.org/jira/browse/JBIDE-5231 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.0.M4 Reporter: Yura Zhishko Assignee: Alexey Kazakov http://docs.jboss.com/seam/2.0.0.GA/reference/en/html/itext.html http://docs.jboss.com/seam/1.2.1.GA/reference/en/html/itext.html -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3188) Value of outcome and action from navigation case is abcent in CA on jsp page.

by Anton Klimkovich (JIRA)

Value of outcome and action from navigation case is abcent in CA on jsp page. ----------------------------------------------------------------------------- Key: JBIDE-3188 URL: https://jira.jboss.org/jira/browse/JBIDE-3188 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, JSF Affects Versions: 3.0.0.cr1 Reporter: Anton Klimkovich Assignee: Alexey Kazakov Priority: Minor EXECUTE: Create JSF 1.2 Kickstart project EXECUTE: Open inputUserName.jsp EXECUTE: Type <h:commandButton action="" value="" /> EXECUTE: Set cursor into action (<h:commandButton action="{cursor}" value="" />) EXECUTE: Call CA ASSERT: Value of outcome should be present in CA FAILURE: Value of outcome and action from navigation case is abcent in CA. For JSF 1.2 with Facelets project it works. -- 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
16
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 November 2009