September 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-3563) Code assist for "class" and "styleClass" attributes for html and jsf tags.

by Alexey Kazakov (JIRA)

Code assist for "class" and "styleClass" attributes for html and jsf tags. -------------------------------------------------------------------------- Key: JBIDE-3563 URL: https://jira.jboss.org/jira/browse/JBIDE-3563 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0 It should show proposals for all classes that are defined in linked css which are available in design time. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4866) After Eclipse restart all opened editor are restored beside Mapping Diagram

by Vitali Yemialyanchyk (JIRA)

After Eclipse restart all opened editor are restored beside Mapping Diagram --------------------------------------------------------------------------- Key: JBIDE-4866 URL: https://jira.jboss.org/jira/browse/JBIDE-4866 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.M4 Mapping Diagram should also be restotred in this case. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBDS-358) Screenshots

by Svetlana mukhina (JIRA)

Screenshots ------------ Key: JBDS-358 URL: http://jira.jboss.com/jira/browse/JBDS-358 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Priority: Minor Fix For: 2.0.0.alpha Sometime screen name (title in guide) doesn't correspond its content, plz try to make titles more informative -- 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, 5 months

2
10
0 / 0

[JBoss JIRA] Created: (JBDS-787) Context menu unification for the VPE and for the text editor

by Svetlana mukhina (JIRA)

Context menu unification for the VPE and for the text editor ------------------------------------------------------------ Key: JBDS-787 URL: https://jira.jboss.org/jira/browse/JBDS-787 Project: Developer Studio Issue Type: Task Components: Doc - VisualWebTools, Doc - RHDS GSG Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 3.0.0.M2 The menu is redesigned, check that menu screens are up-to-date and if there are menu descriptions make sure only the existing menu items are described. see the subtasks of the linked dev tasks. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4150) When creating a new dataset the fields default to any and thus cannot be used in reports (Might just be just the strings)

by Mark Nuttall (JIRA)

When creating a new dataset the fields default to any and thus cannot be used in reports (Might just be just the strings) ------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4150 URL: https://jira.jboss.org/jira/browse/JBIDE-4150 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Mark Nuttall When creating a new dataset the fields default to any and thus cannot be used in reports. This might just be for strings. I did use a number field in my select statement and it did default to Integer. When the dataset or a single field is dragged to the report, end error occurs that says that fields cannot be of type "any". The report xml can be edited to set the correct type but if the dataset is edited, they seem to revert to any. This may only happen if the query is edited. The type cannot be changed in the dataset editor though. -- 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, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-816) Resource bundle completion don't work in template clients

by Adrian Mitev (JIRA)

Resource bundle completion don't work in template clients --------------------------------------------------------- Key: JBIDE-816 URL: http://jira.jboss.com/jira/browse/JBIDE-816 Project: JBoss Tools Issue Type: Bug Components: JSF Environment: rhds beta1, jdk 1.5_0.12, windows XP Reporter: Adrian Mitev I have facelets template page and template client page. If i define <f:loadBundle> in the template page i get code completion for the bundle in it, but i don't get it in the template client page. If i redefine the same <f:loadBundle> in the template client i get completion in it, but this means that i'll have the same component defined twice in the component tree. I guess that the template should be traversed too. -- 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, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-688) Reference of tech-writing terms and phrases

by Svetlana mukhina (JIRA)

Reference of tech-writing terms and phrases -------------------------------------------- Key: JBDS-688 URL: https://jira.jboss.org/jira/browse/JBDS-688 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Priority: Optional Fix For: 2.0.1 It will be useful to create a reference of terms and phrases we use in all guides or should use. The document will be split into several sections, clear and easy to use. -- 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, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4856) Refactoring Managed Bean(Seam Component)/Methods/Properties which are used in ELs.

by Alexey Kazakov (JIRA)

Refactoring Managed Bean(Seam Component)/Methods/Properties which are used in ELs. ---------------------------------------------------------------------------------- Key: JBIDE-4856 URL: https://jira.jboss.org/jira/browse/JBIDE-4856 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, Seam Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.M4 -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4512) "var cannot be resolved" does not recognize single value

by Julien Kronegg (JIRA)

"var cannot be resolved" does not recognize single value -------------------------------------------------------- Key: JBIDE-4512 URL: https://jira.jboss.org/jira/browse/JBIDE-4512 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.0.GA Environment: JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18, Seam 2.1.1.GA Reporter: Julien Kronegg Jboss Tools does not recognize correctly the "var" property in list iterators (e.g. rich:dataTable, h:dataTable) if the "value" property is a single value (but works if the "value" property is a List. This problem occurs for XHTML pages generated by seam-gen where the value is "#{myEntityHome.instance.singleValue}" (see <a href=https://jira.jboss.org/jira/browse/JBIDE-4048>JBIDE-4048</a>). Effects: 1. add a lot of warnings "variableName cannot be resolved" that should be there 2. makes "Seam Validator" task to be very slow when there is a lot of pages (because the Seam Validator task is run on each XHTML file with at least one unresolved EL, see <a href=https://jira.jboss.org/jira/browse/JBIDE-3336>JBIDE-3336</a>) Expected: As the rich:dataTable displays one row when the "value" property is a single value and not a list, Jboss Tools is expected to recognize list AND single value. How to reproduce: EXECUTE: Create seam project. EXECUTE: Create MyBean component (see attached java file) EXECUTE: Open home.xhtml EXECUTE: Add: <h:dataTable var="myVar" value="#{myBean.values}"> <h:column><h:outputText value="#{myVar.myProperty}"/></h:column> </h:dataTable> <h:dataTable var="myVar" value="#{myBean.singleValue}"> <h:column><h:outputText value="#{myVar.myProperty}"/></h:column> </h:dataTable> <h:dataTable var="myVar" value="#{myBean.singleValueAsList}"> <h:column><h:outputText value="#{myVar.myProperty}"/></h:column> </h:dataTable> ASSERT: no warning "myVar cannot be resolved" appear Workaround: Use a "value" property as List and not as single value (maybe wrapping the single value to a List should do the trick). -- 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, 5 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-4908) NoSuchMethodError when enabling JPA facet

by Philippe Marschall (JIRA)

NoSuchMethodError when enabling JPA facet ----------------------------------------- Key: JBIDE-4908 URL: https://jira.jboss.org/jira/browse/JBIDE-4908 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: LATER Reporter: Philippe Marschall What steps will reproduce the problem? 1. Enable JPA Nature 2. Hibernate platform 3. no libraries Dali Version: 2.2 Hibernate Tools version: 3.3.0.v200909110340M-H277-M3 -- Error Details -- Date: Thu Sep 17 16:15:01 CEST 2009 Message: java.lang.RuntimeException: java.lang.NoSuchMethodError: org.eclipse.jpt.core.internal.platform.GenericJpaPlatform.<init>(Ljava/lang/String;Lorg/eclipse/jpt/core/JpaFactory;Lorg/eclipse/jpt/core/JpaAnnotationProvider;Lorg/eclipse/jpt/core/JpaValidation;[Lorg/eclipse/jpt/core/JpaPlatformProvider;)V Severity: Error Product: Eclipse SDK 3.5.0.v200906111540 (org.eclipse.sdk.ide) Plugin: org.eclipse.jface Exception Stack Trace: java.lang.RuntimeException: java.lang.NoSuchMethodError: org.eclipse.jpt.core.internal.platform.GenericJpaPlatform.<init>(Ljava/lang/String;Lorg/eclipse/jpt/core/JpaFactory;Lorg/eclipse/jpt/core/JpaAnnotationProvider;Lorg/eclipse/jpt/core/JpaValidation;[Lorg/eclipse/jpt/core/JpaPlatformProvider;)V at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage.performOk(FacetsPropertyPage.java:248) at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:964) 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.preference.PreferenceDialog.okPressed(PreferenceDialog.java:944) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:453) at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) 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.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:157) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:470) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:510) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1191) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036) at org.eclipse.swt.widgets.Widget.wmSysChar(Widget.java:2313) at org.eclipse.swt.widgets.Control.WM_SYSCHAR(Control.java:4600) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4020) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:5821) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2409) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3471) 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:597) 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) Caused by: java.lang.NoSuchMethodError: org.eclipse.jpt.core.internal.platform.GenericJpaPlatform.<init>(Ljava/lang/String;Lorg/eclipse/jpt/core/JpaFactory;Lorg/eclipse/jpt/core/JpaAnnotationProvider;Lorg/eclipse/jpt/core/JpaValidation;[Lorg/eclipse/jpt/core/JpaPlatformProvider;)V at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaPlatform.<init>(HibernateJpaPlatform.java:28) at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaPlatformFactory.buildJpaPlatform(HibernateJpaPlatformFactory.java:36) at org.eclipse.jpt.core.internal.platform.JpaPlatformRegistry.getJpaPlatform(JpaPlatformRegistry.java:197) at org.eclipse.jpt.core.JptCorePlugin.getJpaPlatform(JptCorePlugin.java:368) at org.eclipse.jpt.core.internal.GenericJpaModel.buildJpaProjectConfig(GenericJpaModel.java:132) at org.eclipse.jpt.core.internal.GenericJpaModel.addJpaProject(GenericJpaModel.java:141) at org.eclipse.jpt.core.internal.GenericJpaModel.jpaFacetedProjectPostInstall(GenericJpaModel.java:217) at org.eclipse.jpt.core.internal.JpaModelManager.facetedProjectPostInstall(JpaModelManager.java:443) at org.eclipse.jpt.core.internal.JpaModelManager.facetedProjectChanged(JpaModelManager.java:427) at org.eclipse.jpt.core.internal.JpaModelManager$FacetedProjectListener.handleEvent(JpaModelManager.java:538) at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1317) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:451) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1171) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1107) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1089) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1099) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:1958) at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$3.run(FacetsPropertyPage.java:186) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:200) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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, 5 months

3
11
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 September 2009