[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 17:48:18 EST 2007


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

Essentially both maven-eclipse-plugin and m2eclipse plugins (there are also other but those 2 are most used IMHO) are trying to reach the same thing - make standard wtp 2 facets work by arranging dependencies correctly (including for hot deployment). 
I think maven-eclipse-plugin is much closer to achieving the goal. It's difference with m2eclipse plugin is that it's not eclipse plugin at all (it is a maven plugin) - it allows to configure project settings including project natures and project facets (which I think exactly what JBoss Tools need?) in a pom. It allows to configure quite a lot except that the current version doesn't support generation wtp 2 specifric settings. (only upto wtp 1.5). Here is the list of properties that is possible to configure: http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html

m2eclipse plugin may be a bigger concern as it is another eclipse plugin ant it tries to arrange dependencies in a container (imho, it is also further away from supporting WTP 2).

However in both cases if and when those plugins start supporting wtp 2 from JBoss Tools point of view it all should (theoretically) come down to supporting absolutely valid WTP 2 project with non-default (but legal) directory and dependencies structure. This is of course speculation at this point as there is no support yet. But it would be nice to support at least one project than not to support at all. 

Right now 'mavenized' projects are pretty much closed for JBoss Tools except for the excellent jsf/facelets/richfaces editors that don't really require certain layouts.

p.s. MavenIDE is another project and considering the 'last published' date on their site I am not sure how active it is (although there are updates in JIRA) so I dont know much about it.

> 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