December 2008 - jbosstools-issues

[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-3131) Images from styles and styles class(doesn't shows in vpe) for relative paths

by Maxim Areshkau (JIRA)

Images from styles and styles class(doesn't shows in vpe) for relative paths ---------------------------------------------------------------------------- Key: JBIDE-3131 URL: https://jira.jboss.org/jira/browse/JBIDE-3131 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.cr1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.0.0.cr1 -- 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
8
0 / 0

[JBoss JIRA] Created: (JBIDE-1410) el resolution in visual editor

by Menashe (JIRA)

el resolution in visual editor ------------------------------ Key: JBIDE-1410 URL: http://jira.jboss.com/jira/browse/JBIDE-1410 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.CR1 Environment: seam2.0 eclipse 3.3.1.1 Reporter: Menashe When el is used (as image/css source) the visual editor doesn't resolve it. Here is what I mean (this is part of my template therefor it must be full path, since if it left as relative path it gets resolved based on the path of the page that is using the template and not of the actual template location.) <img src="#{facesContext.externalContext.requestContextPath}/images/header.gif"/> Visual editor should be able to figure out that #{facesContext.externalContext.requestContextPath} should be just dropped. Since <img src="/images/header.gif"/> works fine in visual editor but not in the seam2 (unless contextpath is '/') -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

7
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3013) DND supporting

by Yura Zhishko (JIRA)

DND supporting -------------- Key: JBIDE-3013 URL: https://jira.jboss.org/jira/browse/JBIDE-3013 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.beta1 Environment: OS XP, Eclipse 3.4 Reporter: Yura Zhishko Assignee: Maxim Areshkau Attachments: sources.zip <h:outputText> doesn't support DND methods at all (use attachment file) -- 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

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-3161) Equinox Transforms plugin for JBDS

by Rob Stryker (JIRA)

Equinox Transforms plugin for JBDS ---------------------------------- Key: JBIDE-3161 URL: https://jira.jboss.org/jira/browse/JBIDE-3161 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.beta1 Reporter: Rob Stryker Assignee: Snjezana Peco Priority: Critical Fix For: 3.0.0.cr1 Develop a plugin which will be able to transform / invalidate other plugins in an installation. First iteration could be just a core with a hard-coded list of plugins / extension points which we want invalidated. The goal here is to have all appropriate plugins in our installation, but disable the ones we do not want. Currently, JBDS removes the webtools jboss server-tools jar entirely, which makes the update site fail. What we need here is to have the webtools jboss server-tools jar IN hte installation, and loaded as a plugin, but have all of its extension points invalidated so it is effectively an empty non-contributing plugin. org.eclipse.jst.server.generic.jboss_1.5.205.v200805140145 is the plugin we need invalidated. We need it's plugin.xml to be essentially empty with just base <plugin></plugin> tags. -- 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

5
54
0 / 0

[JBoss JIRA] Created: (JBIDE-2820) Add supports for new jsf 2.0 elements

by Maxim Areshkau (JIRA)

Add supports for new jsf 2.0 elements -------------------------------------- Key: JBIDE-2820 URL: https://jira.jboss.org/jira/browse/JBIDE-2820 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.0.0.alpha Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.0.0.beta1 Add supports for new jsf 2.0 elements h:head, h:body ... -- 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: (JBDS-366) Welcome screen: view of Create New is incorrectly, and there is strange behavior

by Tatyana Romanovich (JIRA)

Welcome screen: view of Create New is incorrectly, and there is strange behavior -------------------------------------------------------------------------------- Key: JBDS-366 URL: http://jira.jboss.com/jira/browse/JBDS-366 Project: Developer Studio Issue Type: Bug Affects Versions: 1.1.0.CR1 Environment: JBoss Developer Studio Version: 1.1.0 Build id: 200806161541-nightly Build date: 06/16/2008 15:46 Reporter: Tatyana Romanovich Assigned To: Maxim Areshkau Priority: Trivial EXECUTE: Open JBDS with empty workspace EXECUTE: select Getting Started on the Welcome screen EXECUTE: move mouse over the each links 1. FAILURE: green badge on the icon appears only for "Viewlets and Tutorials" point (see Welcome1.png) EXECUTE: select any item (click on the right of link) EXECUTE: move mouse over another items icon 2. FAILURE: both icons have green badge at the same time (see Welcome2.png) EXECUTE: Select "Create New..." 3. FAILURE: "Create jBPM Process Project" is subitem of "Create Seam Project". Is it right? (see Welcome3.png) EXECUTE: Select "Perspectives" EXECUTE: Select any item -> Welcome window gets smaller EXECUTE: Verify Welcome window 4. FAILURE: Welcome to JBDS appears (Is it right? ) EXECUTE: Try to select Perspectives link 5. FAILURE: Perspectives can't be displayed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
20
0 / 0

[JBoss JIRA] Created: (JBDS-340) Intro/Welcome screen cleanup

by Max Rydahl Andersen (JIRA)

Intro/Welcome screen cleanup ---------------------------- Key: JBDS-340 URL: http://jira.jboss.com/jira/browse/JBDS-340 Project: Developer Studio Issue Type: Task Components: ui/branding Reporter: Max Rydahl Andersen Assigned To: Max Rydahl Andersen Fix For: 2.0.0.alpha Splashscreen support has improved in Ganymede, same has the intro and welcome screen setup. SWT did some changes to allow xulrunner to be configured at startup - we should make sure we do what is needede there. If that happens we should be able to remove our big code duplication and just use the normal welcome screen mechanism and hopefully create a JBDS branded version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-3290) sorting/filtering is not updating correctly in code completion of source page in VPE

by Max Rydahl Andersen (JIRA)

sorting/filtering is not updating correctly in code completion of source page in VPE ------------------------------------------------------------------------------------ Key: JBIDE-3290 URL: https://jira.jboss.org/jira/browse/JBIDE-3290 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.0.cr1 Reporter: Max Rydahl Andersen Assignee: Victor Rubezhny Priority: Critical Fix For: 3.0.0.cr1 The sorting seem to make all EL completion show above the more relevant properties of style attributes and when typing the EL completion stays there even though they do not match the filter. See attached video -- 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, 2 months

3
25
0 / 0

[JBoss JIRA] Created: (JBIDE-2763) Add plugin versioning check

by Max Rydahl Andersen (JIRA)

Add plugin versioning check --------------------------- Key: JBIDE-2763 URL: https://jira.jboss.org/jira/browse/JBIDE-2763 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Max Rydahl Andersen Fix For: LATER Our build should validate that A) version numbers only increases B) only increases when there are a change eclipse.org has some of these in place - maybe take a look there ;) -- 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, 2 months

3
2
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 December 2008