February 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4534) Execution JUnit tests for VPE sometimes sleeps for long time

by Maxim Areshkau (JIRA)

Execution JUnit tests for VPE sometimes sleeps for long time ------------------------------------------------------------ Key: JBIDE-4534 URL: https://jira.jboss.org/jira/browse/JBIDE-4534 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Priority: Critical Fix For: 3.1.0.M3 Execution of junit tests sometimes sleeps. Hard to reproduce. In VpeController see line 266, place of main thread sleep. if (xm != null) { WebProject.getInstance(xm).getTaglibMapping().revalidate( WebAppHelper.getWebApp(xm)); } Method 'revalidate' is synchronized and blocked by other thread. See threads stacks in attachment. -- 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

16 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2990) Exception is occured when open inpuUserName.jsp from JSF KickStart project.

by Anton Klimkovich (JIRA)

Exception is occured when open inpuUserName.jsp from JSF KickStart project. --------------------------------------------------------------------------- Key: JBIDE-2990 URL: https://jira.jboss.org/jira/browse/JBIDE-2990 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.beta1 Reporter: Anton Klimkovich Assignee: Maxim Areshkau EXECUTE: Create jsf 1.2 kickstart project EXECUTE: Open inpuUserName.jsp FAILURE: Illegal character in authority at index 7: file://C:\jbdevstudio2.0Beta1\studio\eclipse\plugins\org.jboss.tools.vpe_3.0.0.Beta1-N200810231916\ve\EditorOverride.css An exception stack trace is not available. -- 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

16 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3061) Visual part of VPE does not react to any key-typing

by Max Rydahl Andersen (JIRA)

Visual part of VPE does not react to any key-typing --------------------------------------------------- Key: JBIDE-3061 URL: https://jira.jboss.org/jira/browse/JBIDE-3061 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.beta1 Reporter: Max Rydahl Andersen Assignee: Maxim Areshkau Priority: Critical Fix For: 3.0.0.beta1 As subject says - typing characters does not work, neither does delete key etc. -- 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

16 years, 1 month

6
10
0 / 0

[JBoss JIRA] Created: (JBIDE-3410) java.lang.NullPointerException when try to open page in CR1-20081215 nightly

by Yura Zhishko (JIRA)

java.lang.NullPointerException when try to open page in CR1-20081215 nightly ---------------------------------------------------------------------------- Key: JBIDE-3410 URL: https://jira.jboss.org/jira/browse/JBIDE-3410 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.cr1 Environment: jbdevstudio-win32-2.0.0.CR1-N200812150006 Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Critical 1) Open jbdevstudio-win32-2.0.0.CR1-N200812150006 2) Import attached project 3) Open allComponents.xhtml java.lang.NullPointerException at org.eclipse.core.internal.runtime.Activator.getURLConverter(Activator.java:313) at org.eclipse.core.runtime.FileLocator.resolve(FileLocator.java:186) at org.jboss.tools.jsf.vpe.ajax4jsf.Activator.getPluginResourcePath(Activator.java:68) at org.jboss.tools.jsf.vpe.ajax4jsf.template.Ajax4JSFMediaOutput.getAbsoluteResourcePath(Ajax4JSFMediaOutput.java:65) at org.jboss.tools.jsf.vpe.ajax4jsf.template.Ajax4JSFMediaOutput.create(Ajax4JSFMediaOutput.java:48) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:467) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:657) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:561) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:557) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:262) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:630) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:224) at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:314) at org.jboss.tools.vpe.editor.VpeEditorPart$16.load(VpeEditorPart.java:767) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:553) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$2(MozillaEditor.java:548) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$5.onLoadWindow(MozillaEditor.java:292) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.onStateChange(XulRunnerBrowser.java:407) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2371) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:341) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:773) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:247) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:447) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594) at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:263) at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1410) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:944) 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:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$27.runWithException(Workbench.java:1361) 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:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2293) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:32) 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:386) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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

16 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3588) Name off CSS style class is dublicated in CSS dialog combobox

by Yura Zhishko (JIRA)

Name off CSS style class is dublicated in CSS dialog combobox ------------------------------------------------------------- Key: JBIDE-3588 URL: https://jira.jboss.org/jira/browse/JBIDE-3588 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.CR2 Reporter: Yura Zhishko Assignee: Sergey Dzmitrovich Priority: Minor 1) Call CSS dialog on any CSS style class in CSS file 2) Check combobox for a style 3) Go to the end of list RESULT: Style class name is dublicated -- 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

16 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBDS-1116) JBDS 3.0 CR2 - Seam Doc link

by Gary Lamperillo (JIRA)

JBDS 3.0 CR2 - Seam Doc link ---------------------------- Key: JBDS-1116 URL: https://jira.jboss.org/jira/browse/JBDS-1116 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Doc - VisualWebTools Affects Versions: 3.0.0.CR1 Reporter: Gary Lamperillo The documentation in the splash screen for Seam points to an old version of Seam: http://docs.jboss.org/seam/1.2.1.GA/reference/en/html/index.html Should correspond to EAP 5 - Seam 2.2 from redhat.com, not jboss.org -- 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

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5920) OpenOn does not work for ui:composition template attribute

by Maxim Areshkau (JIRA)

OpenOn does not work for ui:composition template attribute ---------------------------------------------------------- Key: JBIDE-5920 URL: https://jira.jboss.org/jira/browse/JBIDE-5920 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR2 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.1, 3.2.next #1 import http://download.jboss.com/jboss-richfaces/richfaces-demo-4.0.0.ALPHA1-tom... project into workspace #2 open page welcome.xhtml #3 try open on template <ui:composition template="/templates/main.xhtml"> ASSERT IT should work, but doesn't -- 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

16 years, 1 month

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-3508) Validation of orphaned namespaced end tags, i.e. </...>, does not happen for xhtml in VPE

by Karl Philipp (JIRA)

Validation of orphaned namespaced end tags, i.e. </...>, does not happen for xhtml in VPE ----------------------------------------------------------------------------------------- Key: JBIDE-3508 URL: https://jira.jboss.org/jira/browse/JBIDE-3508 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing, Visual Page Editor core Affects Versions: 3.0.0.CR2 Environment: Windows XP SP3, Eclipse 3.4 "GANYMEDE", Web Tools 3.0.3, RichFaces-VPE-win32-3.0.0.CR2-N200901081811, RichFaces 3.2.2.SR1, JSF 1.2 RI, Facelets 1.1.14 Reporter: Karl Philipp Orphaned namedspaced end tags such as </rich:panel> are not detected by the validation algorithm in contrast to orphaned namedspaced start tags: <h:form id="searchForm"> <rich:panel> <f:facet name="header"> <h:outputText value="ServiceProvider" /> </f:facet> <a4j:commandButton value="Search" action="#{sps.search}" /> </rich:panel> </h:form> </rich:panel> The last end tag </rich:panel> above is orphaned but not detected as invalid by VPE. -- 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

16 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5957) Exception during generation entities: "Could not get list of suggested identity strategies from database"

by Aliaksey Nis (JIRA)

Exception during generation entities: "Could not get list of suggested identity strategies from database" --------------------------------------------------------------------------------------------------------- Key: JBIDE-5957 URL: https://jira.jboss.org/jira/browse/JBIDE-5957 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate, Seam Affects Versions: 3.1.0.CR2 Environment: WindowsXP SP2 JBoss Developer Studio Version: 3.0.0 Build id: jbdevstudio-eap-win32-3.0.0.v201002232140M-H180-CR2 JRE 1.6 Reporter: Aliaksey Nis Priority: Critical EXECUTE: Download and launch sample HSQL database(attached). EXECUTE: Create Seam 2.2 war project. In connection profile set target db - this sample db(hsql://localhost:1701). EXECUTE: Expand database node in Hibernate Configurations view. FAILURE: Exception thrown about "naming strategy". EXECUTE: Select this Seam project > New > Generate Entities > Reverse. FAILURE: Exception thrown about "naming strategy". Error log attached. -- 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

16 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-1117) Maven Integration JBDS 3.0 CR2

by Gary Lamperillo (JIRA)

Maven Integration JBDS 3.0 CR2 ------------------------------ Key: JBDS-1117 URL: https://jira.jboss.org/jira/browse/JBDS-1117 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 3.0.0.CR1 Reporter: Gary Lamperillo As listed in JBoss Tools some effort was made to test the maven plugin. Why wasn't the plugin included with JBDS 3.0 CR2? See : http://docs.jboss.org/tools/whatsnew/maven/maven-news-1.1.0.CR2.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

16 years, 1 month

2
1
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 February 2010