February 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1409) Unknown context variable name: entityManager

by Menashe (JIRA)

Unknown context variable name: entityManager -------------------------------------------- Key: JBIDE-1409 URL: http://jira.jboss.com/jira/browse/JBIDE-1409 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.CR1 Environment: latest nightlybuild (dec 3) seam2.0.0 ecliple 3.3.1.1 Reporter: Menashe when em injection is used as in: @In private EntityManager entityManager; then validator fails with Unknown context variable name: entityManager although works fine with seam2 -- 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

18 years

6
22
0 / 0

[JBoss JIRA] Created: (JBDS-225) Wrong dialog title in "Add JSF Capabilities" wizard

by Sergei Abragevich (JIRA)

Wrong dialog title in "Add JSF Capabilities" wizard --------------------------------------------------- Key: JBDS-225 URL: http://jira.jboss.com/jira/browse/JBDS-225 Project: Developer Studio Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Sergei Abragevich Assigned To: Max Andersen 1. Create a non-jsf web project: New -> Project -> Web -> Dynamic Web Project. 2. Right click the project folder - > JBoss Tools -> Add JSF Capabilities. The dialog is called "Import JSF Project". I guess it's not logical, should be something like "Add JSF Capabilities". -- 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

18 years

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1785) Build results should be stored to be loaded when Eclipse restarts

by Viacheslav Kabanovich (JIRA)

Build results should be stored to be loaded when Eclipse restarts ----------------------------------------------------------------- Key: JBIDE-1785 URL: http://jira.jboss.com/jira/browse/JBIDE-1785 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 2.0.0.GA Reporter: Viacheslav Kabanovich Assigned To: Viacheslav Kabanovich Fix For: 2.1 Currently, each time Eclipse starts, all java and xml files that had contributed to Seam model, are parsed to restore it. Parsing takes a lot of time, a project with 1000 components takes 2 - 3 minutes to handle. We may not be able to improve it when full rebuild of project is selected, but we need to avoid that waste of time when once obtained build results are to be picked up by model at start. I propose to serialize parsed seam component declarations into xml file (which is now used just to keep paths of files that contribute to seam model). It is better to keep xml human-readable, so that it is easier to solve problems, especially that may arise at future modifications to Seam model. Testing will include iteration on seam component declaration in just built Seam project, each one serialized, deserialized, and compared to the original to assert that no changes occurred. -- 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

18 years

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1323) VPE x86_64

by Naveed Hasan (JIRA)

VPE x86_64 ---------- Key: JBIDE-1323 URL: http://jira.jboss.com/jira/browse/JBIDE-1323 Project: JBoss Tools Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 2.0.0.CR1 Environment: Fedora 8 x86_64 Reporter: Naveed Hasan VPE plugin built for native x86_64 systems (without relying on x86 binaries.) -- 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

18 years

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-1668) HQL/Criteria editor: when Save As is called no extension is attached automatically

by Dima Geraskov (JIRA)

HQL/Criteria editor: when Save As is called no extension is attached automatically ---------------------------------------------------------------------------------- Key: JBIDE-1668 URL: http://jira.jboss.com/jira/browse/JBIDE-1668 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Reporter: Dima Geraskov Assigned To: Dima Geraskov Priority: Minor Fix For: LATER when Save As is called no extension (hql?) is attached automatically -> will be not possible to easy reopen this file. Save doesn't work if "Save As" was not called first. from Max: "minor thing - but the best thing was that save as actually saved it back to where the query came from (e.g. hbm.xml or java code)" -- 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

18 years

2
13
0 / 0

[JBoss JIRA] Created: (JBIDE-1755) Add comments for all public methods of SeamELCompletionEngine.

by Alexey Kazakov (JIRA)

Add comments for all public methods of SeamELCompletionEngine. -------------------------------------------------------------- Key: JBIDE-1755 URL: http://jira.jboss.com/jira/browse/JBIDE-1755 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 2.0.1 Reporter: Alexey Kazakov Assigned To: Victor Rubezhny Fix For: 2.1 -- 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

18 years

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1734) The JBIDE1479Test test doesn't test jira 1479.

by Snjezana Peco (JIRA)

The JBIDE1479Test test doesn't test jira 1479. ---------------------------------------------- Key: JBIDE-1734 URL: http://jira.jboss.com/jira/browse/JBIDE-1734 Project: Tools (JBoss Tools) Issue Type: Bug Components: QA Affects Versions: 2.0.0.GA Reporter: Snjezana Peco Priority: Minor The problem in jira 1479 happens because VpeController.notifyChanged is called in non-UI thread. The test calls this method in the UI thread. The correct test would be as follows: ... assertNotNull("Editor input is null", input); TestUtil.waitForJobs(); JSPMultiPageEditor part = openEditor(input); TestUtil.waitForJobs(); assertNotNull(part); Job job = new WorkspaceJob("Test"){ public IStatus runInWorkspace(IProgressMonitor monitor) { try { new FormatProcessorXML().formatFile(file); } catch (Exception e) { e.printStackTrace(); } finished = true; return Status.OK_STATUS; } }; job.setPriority(Job.SHORT); job.schedule(0L); TestUtil.waitForJobs(); while (!finished) { TestUtil.delay(1000L); } TestUtil.delay(15000L); PlatformUI.getWorkbench().getActiveWorkbenchWindow().getActivePage() .closeAllEditors(false); ... -- 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

18 years

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-1322) Creating a seam form fails in maven-built web project

by Siarhei Dudzin (JIRA)

Creating a seam form fails in maven-built web project ----------------------------------------------------- Key: JBIDE-1322 URL: http://jira.jboss.com/jira/browse/JBIDE-1322 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.CR1 Environment: Windows XP, Eclipse Europa fall, JBoss Tools 2.0.0CR1, Seam 2.0 Reporter: Siarhei Dudzin I have Seam 2.0 assigned to a project that was created not by seam-gen (a maven web wtp project). While trying to create a form I after filling parameters I am getting an error. The eclipse logs show the following: org.eclipse.core.commands.ExecutionException: While executing the operation, an exception occurred at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:519) at org.jboss.tools.seam.ui.wizard.SeamBaseWizard$1.execute(SeamBaseWizard.java:77) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:101) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:113) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934) at org.jboss.tools.seam.ui.wizard.SeamBaseWizard.performFinish(SeamBaseWizard.java:66) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:135) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) Caused by: java.lang.NullPointerException at org.jboss.tools.seam.ui.wizard.SeamBaseOperation.execute(SeamBaseOperation.java:106) at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511) ... 47 more -- 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

18 years

4
43
0 / 0

[JBoss JIRA] Created: (JBIDE-1421) Hibernate Reverse Eng. Wizard: no validation on 2nd page

by Alexander Chabatar (JIRA)

Hibernate Reverse Eng. Wizard: no validation on 2nd page -------------------------------------------------------- Key: JBIDE-1421 URL: http://jira.jboss.com/jira/browse/JBIDE-1421 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Affects Versions: LATER Reporter: Alexander Chabatar Assigned To: Alexander Chabatar Priority: Minor Fix For: LATER Attachments: wizard.png 1) Finish button is always enabled (even if no Console configuration is selected) 2) Refresh button should be enabled only if configuration is selected. The same issue for all other buttons. 3) Add "Remove All" button to clear table filters list 4) When changing Console configuration from combo box - Table filters list from previous configuration keeps the same. Maybe clear it? 5) Possible to add a lot of *.* table filters, no control for duplicates. -- 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

18 years

4
43
0 / 0

[JBoss JIRA] Created: (RHDS-203) Wizard support for seam-gen style Seam applications

by Jacob Orshalick (JIRA)

Wizard support for seam-gen style Seam applications --------------------------------------------------- Key: RHDS-203 URL: http://jira.jboss.com/jira/browse/RHDS-203 Project: Red Hat Developer Studio Issue Type: Feature Request Affects Versions: 1.0.0.beta1 Reporter: Jacob Orshalick Currently the Seam wizards only support WTP style projects. seam-gen style projects are only supported by the this seam-gen wrapper. Although the seam-gen wrapper works for existing applications, it would be nice to use the wizards. Please see the forum reference for more information. Thanks. -- 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

18 years

4
26
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 2008