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

[Siarhei Dudzin (JIRA)]

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

Max, the idea behind the maven-eclipse-plugin is not to fight between  eclipse and maven but to generate eclipse projects from pom. Which means that  if a user want to have seam project in maven while using this plugin then he would need to specifiy seam-specific settings and natures in pom which shouldn't be a worry of JBoss Tools at all. 
This also would mean that a creation of a new project wouldn't be done via JBoss Tools but could be re-generated from scratch by maven. Which is perfectly alright from the way the plugin works. 
I use this project for RAD (ejb 2.1 projects) and can delete eclipse project specific files and regenerate them with single command (all eclipse settings are specified in the pom).
Anyway if a user creates or changes project settings and uses this plugin he/she is perfectly aware that the project is being controlled by maven.

This may seem awkward if you're only used to work from within IDE but from the other hand this allows to have really only one source of configuration instead of 2 (pom and eclipse), besides because this plugin is not coupled to eclipse version - it can be used in legacy environment (RAD-6 for example) while eclipse plugins are pretty much dependent on eclipse version.
Besides the last bugs were fixed today and looks like it would be possible to actually test WTP-2 support form that plugin.

m2eclipse has of course better integration with eclipse but is also much further away from WTP 2. 

No matter which one of these 2 may be supported the main challenges with JBoss Tools will be:
* The directory structure
* The dependencies (jars physically are not actually in web-inf/lib - issue for deployment)

Hopefully if any of those plugins will get WTP-2 compatible the only challenge would be the directory structure.

Q4E is even further away from WTP ( http://groups.google.com/group/q4e-users/browse_thread/thread/9410e3ef6ff120ec ). They just planned it.

I am still preparing the project example as Denis asked because the directory and projects structure is the main issue here (if that's ok with you).

> 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