October 2011 - jbosstools-issues - Jboss List Archives

[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-9233) Exception in log while quick editing a file

by Lukas Jungmann (JIRA)

Exception in log while quick editing a file ------------------------------------------- Key: JBIDE-9233 URL: https://issues.jboss.org/browse/JBIDE-9233 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Final Reporter: Lukas Jungmann Assignee: Daniel Azarov Fix For: 3.3.0.M1 I have created method @Inject public String getX( @Named String a) { return a; } which was the last method in a class file. Then I manually reformatted it to @Inject public String getX( @Named String a) { return a; } } with 10 empty lines instead of 1 left here for readability. Then I deleted each set of spaces by selecting it all and using Delete button. Finally, I started quickly repeat Undo-Save-Redo-Save with fast keys. Several rounds resulted in the exception. That kind of intensive 'work' may result in other exceptions as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-9638) Default directory of New XHTML Page inside target folder

by George Gastaldi (JIRA)

Default directory of New XHTML Page inside target folder -------------------------------------------------------- Key: JBIDE-9638 URL: https://issues.jboss.org/browse/JBIDE-9638 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: George Gastaldi In a Maven WAR project, when I create a XHTML file, it always suggests it to be under *target/m2e-wtp/web-resources*. This is annoying, cause this folder is derived and building the project will clean it. It should use the folder I selected before opening the wizard. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
5
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-9785) File storage for KB model is too big.

by Viacheslav Kabanovich (JIRA)

File storage for KB model is too big. ------------------------------------- Key: JBIDE-9785 URL: https://issues.jboss.org/browse/JBIDE-9785 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: CDI, common/jst/core Affects Versions: 3.3.0.M3 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 File %workspace%/.metadata/.plugins/org.jboss.tools.jst.web.kb/projects/%project_name%.xml keeps serialized KB model and linked resources detected by CDI and other builders and validators. The file is an easy readable xml, but it is too long. 1) Tag libraries are saved in such details that only those loaded from standard.jar take as much as 100K of memory. At the same time, when KB project is restored at Eclipse start, KB model is being bound to underlying XModel so that the serialized objects do not provide any advantage comparing to direct loading from XModel. Therefore, we should serialize only first-level link between tag library and XModel file object. 2) Linked resources include full path references, each may be repeated many times. I suggest generating short alias for each path, then the table for linking alias to path will reference each of them just once, and the list of linked resources will reference short aliases only. These two suggestions will reduce the file storage 3-5 times. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
6
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-9791) Add JUnit Tests for CDI Packages Without Coverage

by Denis Golovin (JIRA)

Add JUnit Tests for CDI Packages Without Coverage ------------------------------------------------- Key: JBIDE-9791 URL: https://issues.jboss.org/browse/JBIDE-9791 Project: Tools (JBoss Tools) Issue Type: Task Components: CDI Affects Versions: 3.3.0.M4 Reporter: Denis Golovin Assignee: Daniel Azarov Priority: Critical Fix For: 3.3.0.M4, 3.3.0.Beta1 Attachments: screenshot113.png Some CDI packages are not covered by JUnit Tests: org.jboss.tools.cdi.internal.core.project.facet org.jboss.tools.cdi.xml.beans.model.handlers org.jboss.tools.cdi.ui.wizard.facet org.jboss.tools.cdi.seam.config.ui.preferences org.jboss.tools.cdi.internal.core.refactoring org.jboss.tools.cdi.ui.refactoring org.jboss.tools.cdi.seam.config.ui.marker -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9732) CDI Project should provide a built-in bean with type InjectionPoint

by Alexey Kazakov (JIRA)

CDI Project should provide a built-in bean with type InjectionPoint ------------------------------------------------------------------- Key: JBIDE-9732 URL: https://issues.jboss.org/browse/JBIDE-9732 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 {quote} *5.5.7. Injection point metadata* ... The container must provide a bean with scope @Dependent, bean type InjectionPoint and qualifier @Default, allowing dependent objects, as defined in Section 6.4.1, "Dependent objects", to obtain information about the injection point to which they belong. The built-in implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies". {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
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 October 2011