February 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5926) *taglib.xml facelet tag libraries with .xsd defenition aren't displayed in Web Project view

by Yura Zhishko (JIRA)

*taglib.xml facelet tag libraries with .xsd defenition aren't displayed in Web Project view ------------------------------------------------------------------------------------------- Key: JBIDE-5926 URL: https://jira.jboss.org/jira/browse/JBIDE-5926 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1, 3.1.0.CR2 Reporter: Yura Zhishko Assignee: Viacheslav Kabanovich Priority: Minor Download an example here http://www.primefaces.org/downloads.html. During debug I have found that FaceletTaglibEntityRecognizer defines primefaces-p.taglib.xml and primefaces-i.taglib.xml as facelet-tag-libraries entities but they are not displayed in Web Project view. See the last comments in https://jira.jboss.org/jira/browse/JBIDE-5642. -- 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, 10 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5642) Taglibs defined in JAR files as facelets *.taglib.xml are not recognized in Web Projects View in Tag Libraries folder.

by Oleg Varaksin (JIRA)

Taglibs defined in JAR files as facelets *.taglib.xml are not recognized in Web Projects View in Tag Libraries folder. ---------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5642 URL: https://jira.jboss.org/jira/browse/JBIDE-5642 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Environment: Eclipse 3.5 and higher, JBossTools 3.1.0.CR1, OS Windows XP and higher Reporter: Oleg Varaksin If we have some JAR files in classpath of web project which contain *.taglib.xml files (under META-INF) they will be not recognized by JBoss Tools. I have imported such JAR as described in the related issue https://jira.jboss.org/jira/browse/JBIDE-4213. TLDs have been well recognized (displayed under Tag Libraries folder), but *.taglib.xml files not. There are no chances to add them to the JBoss Tools Palette. Note 1: *.taglib.xml files from external JARs don't have to be added in web.xml. That means, javax.faces.FACELETS_LIBRARIES is not needed in web.xml. JSF scans automatically META-INF folder of all JARs in classpath. Note 2: *.taglib.xml files should be also recognized in JAR project itself if we implement JSF 2 custom components in this JAR project (which reside under META-INF/resources/...) and want to add xmlns namespaces from *.taglib.xml's in some *.xhtml files. At the moment it's not possible and there isn't code autocompletion. This issue is very important for JSF 2.x. -- 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, 10 months

6
32
0 / 0

[JBoss JIRA] Created: (JBIDE-5963) Palette inserts taglib definition incorectly in xhtml file

by Daniel Azarov (JIRA)

Palette inserts taglib definition incorectly in xhtml file ---------------------------------------------------------- Key: JBIDE-5963 URL: https://jira.jboss.org/jira/browse/JBIDE-5963 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR2 Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich Priority: Minor Fix For: LATER When user inserts ordinary tag from palette in xhtml - all works fine. But when user inserts taglib definition - for jsp and xhtml files palette inserts construction like: <%@ taglib uri="http://richfaces.org/rich" prefix="rich" %> This is suitable for jsp file but not for xhtml 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

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5940) CA not shows jsf2 composition element attributes

by Maxim Areshkau (JIRA)

CA not shows jsf2 composition element attributes -------------------------------------------------- Key: JBIDE-5940 URL: https://jira.jboss.org/jira/browse/JBIDE-5940 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR2 Reporter: Maxim Areshkau Assignee: Alexey Kazakov #1 import https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... into workspace #2 open page https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... #3 try CA in rich:page element ASSERT there isn't proposals for attributes which defined in rich:page -- 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, 10 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5866) Errors occur during file Rename if the file is opened in the Editor

by Svetlana Yasenovich (JIRA)

Errors occur during file Rename if the file is opened in the Editor ------------------------------------------------------------------- Key: JBIDE-5866 URL: https://jira.jboss.org/jira/browse/JBIDE-5866 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Environment: Windows XP, java version "1.6.0_18" JBoss Developer Studio Version: 3.0.0.CR2 Build id: v201002140303M Reporter: Svetlana Yasenovich EXECUTE: 1. Create new JSF project 2. Open any faces-config.xml file in the Editor 3. On Web Projects view right click on this faces-config.xml and select rename from context menu. Enter another name in rename dialog. Press Ok. FAILURE: Exceptions thrown (The same errors occur during the renaming of struts-config.xml, TLD 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

15 years, 10 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5854) NullPointerException occures when openning JBoss Tools Properties Editor for a jar-packaged property file

by Victor Rubezhny (JIRA)

NullPointerException occures when openning JBoss Tools Properties Editor for a jar-packaged property file ---------------------------------------------------------------------------------------------------------- Key: JBIDE-5854 URL: https://jira.jboss.org/jira/browse/JBIDE-5854 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.1.0.CR1 Reporter: Victor Rubezhny Assignee: Viacheslav Kabanovich Priority: Minor Fix For: 3.1.1 NullPointerException occures when openning JBoss Tools Properties Editor for a jar-packaged property file Steps to reproduce: EXECUTE: Create a project (Struts/JSF/Seam - doesn't matter which, but it should contain some JAR libraries). For example, create Seam project. EXECUTE: Expand Web App Libraries in Package explorer and one of existing JAR libraries. Search for a property file and then open it with JBoss Tools Properties Editor (It must be openned by default) ASSERT: File is openned in editor. (FAILURE. See Exception below) java.lang.NullPointerException at org.jboss.tools.common.model.ui.texteditors.PropertiesTextEditorComponent.createPartControl(PropertiesTextEditorComponent.java:58) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:242) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:212) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createTextPage(ObjectMultiPageEditor.java:274) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createUnloadedPage(ObjectMultiPageEditor.java:261) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:226) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:357) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:659) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:459) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorReference.getPart(EditorReference.java:821) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:283) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2857) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2676) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:374) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:178) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:229) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:208) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:373) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:526) at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:842) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:840) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1101) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1205) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) 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(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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, 10 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5160) Update Seam Component or Manage Bean class references in EL while class renaming

by Daniel Azarov (JIRA)

Update Seam Component or Manage Bean class references in EL while class renaming -------------------------------------------------------------------------------- Key: JBIDE-5160 URL: https://jira.jboss.org/jira/browse/JBIDE-5160 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, Seam Affects Versions: 3.1.0.M3 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.1.0.CR1 We need class rename participant to update Seam Component or Manage Bean class references in EL. -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-974) Some Features has missing License

by Vlado Pakan (JIRA)

Some Features has missing License --------------------------------- Key: JBDS-974 URL: https://jira.jboss.org/jira/browse/JBDS-974 Project: JBoss Developer Studio Issue Type: Bug Components: ui/branding Affects Versions: 2.1.1 Environment: Linux 32 bit Reporter: Vlado Pakan These features has missing License: JBoss Archive Tools - org.jboss.ide.eclipse.archives.feature JBoss AS Tools - org.jboss.ide.eclipse.as.feature Hibernate Tools - org.hibernate.eclispe.feature JBoss Tools Rich Faces - org.jboss.tools.richfaces.feature (Choose Menu Help > About > About JBoss Developer Studio > Feature Details Button > License Button) -- 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, 10 months

7
23
0 / 0

[JBoss JIRA] Created: (JBDS-1091) Installer does not always import all found App servers to newly created workspace

by Libor Zoubek (JIRA)

Installer does not always import all found App servers to newly created workspace --------------------------------------------------------------------------------- Key: JBDS-1091 URL: https://jira.jboss.org/jira/browse/JBDS-1091 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 3.0.0.CR2 Environment: Fedora 12, x86_64 Reporter: Libor Zoubek Priority: Minor Is seem that installer has problem with finding servers. It finds it during installation process, but when I then run JBDS with new workspace, I can't see servers found during installation in Server View. There are quite strange conditions to make this happen. Requirements: * JBDS CR2 * jboss-eap-noauth-5.0.0.GA.zip unzip jboss-eap-noauth-5.0.0.GA.zip /tmp/ cp -a /tmp/jboss-eap-5.0/jboss-as /tmp Now we have EAP5 plattform in /tmp/jboss-eap-5.0/ and jboss 5 AS in /tmp/jboss-as Steps to reproduce: * Run JBDS CR2 installer * When adding servers, the order DOES matter (If you find servers in reverse order, everything works as expected) * Find -> Select path /tmp/jboss-as * Find -> Select path tmp/jboss-eap-5.0/ After installation run JBDS and point workspace to some new/empty dir Result : No servers or only one of them (always eap) can be found in Server View. The installer behaviour is really strange. I've tried it almost 30times ( delete installation and workspace, than install again) at this issue does not happen every time. Secondly, I've figured out, that installer is probably creating Server configurations in the latest step of installation (when it creates shortcuts). One can leave installation process at this step (I do not need to have shortcut on my desktop, so I quit installation), then absolutely no app server configurations appear in JBDS afterwards. Can we move this step to some earlier phase of installation? -- 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, 10 months

7
33
0 / 0

[JBoss JIRA] Created: (JBIDE-5892) NPE - seam core validation

by Vitali Yemialyanchyk (JIRA)

NPE - seam core validation -------------------------- Key: JBIDE-5892 URL: https://jira.jboss.org/jira/browse/JBIDE-5892 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR2 Reporter: Vitali Yemialyanchyk java.lang.NullPointerException at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.init(SeamCoreValidator.java:162) at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateAll(SeamCoreValidator.java:271) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:99) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:78) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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, 11 months

4
12
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