January 2008 - jbosstools-issues - Jboss List Archives

[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, 2 months

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, 2 months

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, 2 months

4
26
0 / 0

[JBoss JIRA] Created: (JBIDE-1646) Unable to start JBoss EAP 4.3.0

by Kapil Anand (JIRA)

Unable to start JBoss EAP 4.3.0 ------------------------------- Key: JBIDE-1646 URL: http://jira.jboss.com/jira/browse/JBIDE-1646 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.GA Environment: Eclipse3.3.1 (fall2 JEE Europa) and JBossTools2.0.0.GA JBoss EAP 4.3.0 jboss-as configuration: all, default, production Also tried this on JBossDeveloperStudio1.0.0 with same results Reporter: Kapil Anand I am able to launch JBoss 4.3.0 from command line using run.sh/run.bat, but it fails to start from within eclipse. Java process just abruptly dies while starting up . Logs do not show any error or exception, neither anything shows up on stderr eclipse is capturing and I could not establish any pattern in this since I tried this multiple times and the process died at different points. -- 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 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-1258) Actually auto-complete resource bundle keys for org.jboss.seam.international.messages (and resource bundles in faces-confg)

by Gavin King (JIRA)

Actually auto-complete resource bundle keys for org.jboss.seam.international.messages (and resource bundles in faces-confg) --------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1258 URL: http://jira.jboss.com/jira/browse/JBIDE-1258 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King Max tells my that, today, when a resource bundle is defined using f:loadBundle, we can actually look inside the .properties file and find the keys. Well, thats awesome, except that f:loadBundle is semi-deprecated, and the following approaches are preferred: * For Seam projects, use the built-in component, and do #{messages.foo} to get "foo" from messages_xx.properties * For any JSF project, look at resource bundles defined in faces-config.xml By the way, at present it looks like the resource bundle stuff is a bit confused about the classpath, and thinks that if the bundle.properties file is in src/model, then the name of it is "model.bundle", when in fact it is just "bundle". This is a bug. -- 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 months

5
17
0 / 0

[JBoss JIRA] Created: (JBDS-232) Update information about the palette

by Anatoly Fedosik (JIRA)

Update information about the palette ------------------------------------- Key: JBDS-232 URL: http://jira.jboss.com/jira/browse/JBDS-232 Project: Developer Studio Issue Type: Task Components: Doc - JSFTools Affects Versions: 1.0.0.GA Reporter: Anatoly Fedosik Assigned To: Yauheniya kryvinchanka Fix For: 1.0.1 1) Now most palette wizards have title. Update the screenshots if it is necessary. Related bug is: JBIDE-1471 2) 'Properties' menu Item is removed from Palette editor popup menu. Update text and screenshots if it is necessary. Related bug is: JBIDE-1472 -- 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 months

3
10
0 / 0

[JBoss JIRA] Created: (RHDS-339) Discuss the differences between WAR deployment and EAR deployment.

by Svetlana mukhina (JIRA)

Discuss the differences between WAR deployment and EAR deployment. ------------------------------------------------------------------ Key: RHDS-339 URL: http://jira.jboss.com/jira/browse/RHDS-339 Project: Red Hat Developer Studio Issue Type: Task Components: Doc - Seam Affects Versions: 1.0.0.CR1 Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Fix For: 1.1 Update the guide according to this remark: "Ch#3 needs some improvement: We need to discuss what are the differences between WAR deployment and EAR deployment. The WAR is for deployment on Tomcat + Embedded JBoss We need to discuss the directories inside the directories you have shown. We need to explain where are the xhtml files, java files, web.xml, etc etc. " Waiting for Max blog update where it will be written about it. -- 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 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1355) [unittest] ASClasspath test failure because of weird NPE on hudson

by Max Andersen (JIRA)

[unittest] ASClasspath test failure because of weird NPE on hudson ------------------------------------------------------------------ Key: JBIDE-1355 URL: http://jira.jboss.com/jira/browse/JBIDE-1355 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.CR1 Reporter: Max Andersen Fix For: 2.0.1 testClasspathAvailable fails - most likely because of this hidden stack trace inside the console output. Seems like the jvm type is unknown for some reason. [java] !ENTRY org.eclipse.wst.common.project.facet.core 4 0 2007-11-21 15:58:22.089 [java] !MESSAGE null [java] !STACK 0 [java] java.lang.NullPointerException [java] at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossServerRuntime.getVM(AbstractJBossServerRuntime.java:75) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadJREClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:178) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadClasspathEntries2(WebtoolsProjectJBossClasspathContainerInitializer.java:148) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:141) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.getClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:111) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider.getClasspathEntries(ProjectRuntimeClasspathProvider.java:69) [java] at org.eclipse.jst.common.project.facet.core.internal.RuntimeClasspathProvider.getClasspathEntries(RuntimeClasspathProvider.java:51) [java] at org.eclipse.jst.common.project.facet.core.ClasspathHelper.addClasspathEntries(ClasspathHelper.java:148) [java] at org.eclipse.jst.common.project.facet.JavaFacetUtils.resetClasspath(JavaFacetUtils.java:229) [java] at org.eclipse.jst.common.project.facet.JavaFacetRuntimeChangedDelegate.execute(JavaFacetRuntimeChangedDelegate.java:44) [java] at org.eclipse.wst.common.project.facet.core.events.internal.LegacyEventHandlerAdapter.handleEvent(LegacyEventHandlerAdapter.java:100) [java] at org.eclipse.wst.common.project.facet.core.events.internal.ListenerRegistry.notifyListeners(ListenerRegistry.java:76) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1088) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.setTargetedRuntimesInternal(FacetedProject.java:692) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$4(FacetedProject.java:613) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$3.run(FacetedProject.java:595) [java] at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.setTargetedRuntimes(FacetedProject.java:605) [java] at org.jboss.ide.eclipse.as.test.ASClasspathTest.setTargetRuntime(ASClasspathTest.java:141) [java] at org.jboss.ide.eclipse.as.test.ASClasspathTest.testClasspathAvailable(ASClasspathTest.java:98) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at junit.framework.TestCase.runTest(TestCase.java:164) -- 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 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1180) Consider using ICompilationParticipant when validating java

by Max Andersen (JIRA)

Consider using ICompilationParticipant when validating java ----------------------------------------------------------- Key: JBIDE-1180 URL: http://jira.jboss.com/jira/browse/JBIDE-1180 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Max Andersen Fix For: 2.1 I noticed that our seamvalidator reads each .java file into memory before validating; it much be much more efficient to use ICompliationParticipant to validate these things. -- 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 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1146) Problems with creating Seam ear web project using jre1.6.0_02.

by Anton Klimkovich (JIRA)

Problems with creating Seam ear web project using jre1.6.0_02. -------------------------------------------------------------- Key: JBIDE-1146 URL: http://jira.jboss.com/jira/browse/JBIDE-1146 Project: JBoss Tools Issue Type: Bug Components: Seam, seam-gen Affects Versions: 2.0.0.Beta4 Environment: WinXp jre1.6.0_02 200710210005-nightly Reporter: Anton Klimkovich Priority: Minor Attachments: seam.PNG Create Seam ear project (File->New->Project->Seam->Seam Web Project) After validation complete some errors will occure. java.lang.NullPointerException at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateXmlComponentDeclarations(SeamCoreValidator.java:448) at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateComponent(SeamCoreValidator.java:402) at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateComponent(SeamCoreValidator.java:323) at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validate(SeamCoreValidator.java:161) at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validate(SeamValidatorManager.java:75) at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:60) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75) 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

5
19
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 January 2008