May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8995) Visual Page Editor: Wrong image on toolbar button which changes layout

by Daniel Azarov (JIRA)

Visual Page Editor: Wrong image on toolbar button which changes layout ---------------------------------------------------------------------- Key: JBIDE-8995 URL: https://issues.jboss.org/browse/JBIDE-8995 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Reporter: Daniel Azarov Assignee: Yahor Radtsevich Attachments: VPE_Horizontal.png, VPE_Vertical.png Toolbar button should show the image and tool tip text for next possible layout (not current layout) Image and tool tip should inform user what he will get if he press this button. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

10
18
0 / 0

[JBoss JIRA] Created: (JBIDE-8002) (incorrect) faces-config validation error upon project clean

by erik van altena (JIRA)

(incorrect) faces-config validation error upon project clean ------------------------------------------------------------ Key: JBIDE-8002 URL: https://issues.jboss.org/browse/JBIDE-8002 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.Beta2 Environment: Eclipse Helios Reporter: erik van altena Assignee: Alexey Kazakov Priority: Minor In my project (jsf 1.2 capabilities) I have multiple faces-config files, configured as follows in the web.xml file: <context-param> <param-name>javax.faces.CONFIG_FILES</param-name> <param-value>/WEB-INF/faces-config.xml,/WEB-INF/navigation.xml,/WEB-INF/form-config.xml,/WEB-INF/storage-config.xml,/WEB-INF/search-config.xml</param-value> </context-param> So far so good. However, each time I now clean the project, I get a validation error in the problems list (and the project is marked as having an error) on the fact that one of these files does not exist - it seems random which one it complains about but the error does happen consistently. This validation error is not shown in the web.xml file itself when I open it, and when I alter and save the web.xml file, the error disappears from the problems list and the project no longer has errors. I did not ever see this otherwise minor issue in beta 1. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6546) Can not enter multibyte character in JSF HTML Palette attribute dialog value field

by Hitoshi Ozawa (JIRA)

Can not enter multibyte character in JSF HTML Palette attribute dialog value field ---------------------------------------------------------------------------------- Key: JBIDE-6546 URL: https://jira.jboss.org/browse/JBIDE-6546 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.1 Environment: Windows Reporter: Hitoshi Ozawa Assignee: Alexey Kazakov When I drag a JSF HTML Palette, an Attribute dialog opens. In this dialog, I'm not able to enter multibyte characters (i.e. Japanese) value field. The current workaround is to leave it blank and create an HTML tag, and enter a Japanese text in the HTML tag but having a attribute dialog box open each time which I'm not able to use is really bothersome. -- 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

14 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7455) New JSF Project wizard creates web.xml 3.0 with incorrect namespaces.

by Alexey Kazakov (JIRA)

New JSF Project wizard creates web.xml 3.0 with incorrect namespaces. --------------------------------------------------------------------- Key: JBIDE-7455 URL: https://jira.jboss.org/browse/JBIDE-7455 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.Beta2 1. Open New JSF Project wizard. 2. Select JSF 2 & Servlet Version 3.0. Press Finish. 3. Open the created web.xml. It has <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" ...> But it should have <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"...> shouldn't it? And btw, could we use Servetl 3.0 as default value for JSF 2.0 projects in our wizard? Not it's 2.5. -- 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

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8225) Richfaces component installed on Eclipse SDK is not fully functional

by Denis Golovin (JIRA)

Richfaces component installed on Eclipse SDK is not fully functional -------------------------------------------------------------------- Key: JBIDE-8225 URL: https://issues.jboss.org/browse/JBIDE-8225 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Priority: Critical -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8150) XPCOM error during browsing on welcome page on Fedora 64b

by Jiri Peterka (JIRA)

XPCOM error during browsing on welcome page on Fedora 64b --------------------------------------------------------- Key: JBIDE-8150 URL: https://issues.jboss.org/browse/JBIDE-8150 Project: Tools (JBoss Tools) Issue Type: Bug Components: core Affects Versions: 3.2.0.Beta2 Environment: JBDS 4.0.0.CR1 H65, Linux 64 (Fedora 14 - 2.6.35.10-74.fc14.x86_64) Reporter: Jiri Peterka During Browsing on Welcome page XPCOM error occured: org.eclipse.swt.SWTError: XPCOM error -2147467262 at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2414) at org.eclipse.swt.browser.Mozilla.OnStateChange(Mozilla.java:3346) at org.eclipse.swt.browser.Mozilla$10.method3(Mozilla.java:986) at org.eclipse.swt.internal.mozilla.XPCOMObject.callback3(XPCOMObject.java:266) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2229) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) org.eclipse.swt.SWTError: XPCOM error -2147467259 at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2414) at org.eclipse.swt.browser.Mozilla.onDispose(Mozilla.java:2429) at org.eclipse.swt.browser.Mozilla$5.handleEvent(Mozilla.java:891) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263) at org.eclipse.swt.widgets.Widget.release(Widget.java:1080) at org.eclipse.swt.widgets.Control.release(Control.java:3304) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1293) at org.eclipse.swt.widgets.Widget.release(Widget.java:1083) at org.eclipse.swt.widgets.Control.release(Control.java:3304) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1293) at org.eclipse.swt.widgets.Widget.release(Widget.java:1083) at org.eclipse.swt.widgets.Control.release(Control.java:3304) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1293) at org.eclipse.swt.widgets.Widget.release(Widget.java:1083) at org.eclipse.swt.widgets.Control.release(Control.java:3304) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:462) at org.eclipse.ui.internal.PartPane.dispose(PartPane.java:180) at org.eclipse.ui.internal.ViewPane.dispose(ViewPane.java:193) at org.eclipse.ui.internal.WorkbenchPartReference.dispose(WorkbenchPartReference.java:681) at org.eclipse.ui.internal.WorkbenchPage.disposePart(WorkbenchPage.java:1721) at org.eclipse.ui.internal.WorkbenchPage.partRemoved(WorkbenchPage.java:1713) at org.eclipse.ui.internal.ViewFactory.releaseView(ViewFactory.java:257) at org.eclipse.ui.internal.Perspective.hideView(Perspective.java:606) at org.eclipse.ui.internal.WorkbenchPage.hideView(WorkbenchPage.java:2387) at org.eclipse.ui.internal.ViewPane.doHide(ViewPane.java:213) at org.eclipse.ui.internal.PartStack.close(PartStack.java:541) at org.eclipse.ui.internal.PartStack.close(PartStack.java:524) at org.eclipse.ui.internal.PartStack$1.close(PartStack.java:120) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:83) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:269) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:278) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.access$1(DefaultTabFolder.java:1) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder$1.closeButtonPressed(DefaultTabFolder.java:71) at org.eclipse.ui.internal.presentations.PaneFolder.notifyCloseListeners(PaneFolder.java:631) at org.eclipse.ui.internal.presentations.PaneFolder$3.close(PaneFolder.java:206) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1595) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:261) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

5
16
0 / 0

[JBoss JIRA] Created: (JBIDE-1273) When hot code replace fails, offer "restart deployment "as an alternative

by Gavin King (JIRA)

When hot code replace fails, offer "restart deployment "as an alternative ------------------------------------------------------------------------- Key: JBIDE-1273 URL: http://jira.jboss.com/jira/browse/JBIDE-1273 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King The dialog box t hat eclipse pops up when hot code replace fails is very irritating, but it would be less irritating if it offered "restart deployment" as an alternative. Actually it should be smart enough to NOT pop this dialog at all for classes in src/action. So I think the Seam tools need to hijack this whole feature of eclipse. -- 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

14 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBDS-1662) Cannot deploy Seam Portlet Example to JBoss EPP 4.3

by Pavol Srna (JIRA)

Cannot deploy Seam Portlet Example to JBoss EPP 4.3 --------------------------------------------------- Key: JBDS-1662 URL: https://issues.jboss.org/browse/JBDS-1662 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.1.0.M1 Reporter: Pavol Srna Attachments: server.log See log attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

13
37
0 / 0

[JBoss JIRA] Created: (JBIDE-8427) Really slow deployment while dialog visible

by henk de boer (JIRA)

Really slow deployment while dialog visible ------------------------------------------- Key: JBIDE-8427 URL: https://issues.jboss.org/browse/JBIDE-8427 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.CR1 Environment: Mac OS X 10.6.4, Eclipse 3.6.1 (64 bits) Reporter: henk de boer When a project is deployed using the Jboss tools WTP adapter with the progress dialog visible the operation is really slow. As soon as the operation is send to the background it's fast again. It seems the code tries to display every file name on screen, which results in a maximum copy rate of 60 files/second (screen refresh). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
14
0 / 0

[JBoss JIRA] Created: (JBIDE-8919) Recognize and define ESB Runtime from SOA-P product

by Vlado Pakan (JIRA)

Recognize and define ESB Runtime from SOA-P product --------------------------------------------------- Key: JBIDE-8919 URL: https://issues.jboss.org/browse/JBIDE-8919 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.2.1.M1 Reporter: Vlado Pakan Assignee: Snjezana Peco When searching for runtimes (Menu Window > Preferences > JBoss Tools > JBoss Tools Runtimes) SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes. Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04. JBT should automatically detect ESB Runtime within SOA-P product and define it for later use. Has to be working also with SOA-P Standalone products. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

8
21
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 May 2011