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

Siarhei Dudzin (JIRA) jira-events at lists.jboss.org
Thu Nov 15 15:42:27 EST 2007


    [ http://jira.jboss.com/jira/browse/JBIDE-1322?page=comments#action_12387818 ] 
            
Siarhei Dudzin commented on JBIDE-1322:
---------------------------------------

Well yes, if you test with maven (for example) you do have a different classpath (because of dependencies in test scope). Usually, when I work with maven I already have that alternative (including test dependencies) classpath, at least this is what I get when generating project using maven-eclipse-plugin. It works with  with older wtp versions (hot deployment via wtp I mean - didn't have a chance to test seam since it ejb-3 wont work with older WTP). However they are just 2 bugfixes away from having a release with wtp-2 support, and those are:

http://jira.codehaus.org/browse/MECLIPSE-333 

and 

http://jira.codehaus.org/browse/MECLIPSE-264 

which is very interesting (from testing prospective) because it's easier to adapt ant to the 'default' eclipse wtp layout than do the same with maven.

Anyway, I actually meant somewhat 'smart' behavior of the wizard which would (hypothetically) do one of the following:

* Give a warning message but still create the form (skip tests)
* Provide a checkbox asking whether creation of test should be part of creating the form (although I think it would be nice that IDE does 'motivate' a user to have tests)
* Ask for a source folder/project on where to put tests (since test project is not detected the user would need to deal with the alternative classpath himself anyway)
* (Almost sci-fi :) Scan dependency tree and/or facets and put generated stuff in corresponding projects: entities in projects with JPA facets, xhtml in projects with JSF facets, tests in plain utility projects which are above JPA/WEB/EAR projects in the dependency tree

> 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
>          Components: Seam
>    Affects Versions: 2.0.0.CR1
>         Environment: Windows XP, Eclipse Europa fall, JBoss Tools 2.0.0CR1, Seam 2.0
>            Reporter: Siarhei Dudzin
>         Assigned To: Denis Golovin
>             Fix For: 2.0.0.GA
>
>
> 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

        



More information about the jbosstools-issues mailing list