4:26 p.m.
[ http://jira.jboss.com/jira/browse/JBIDE-1322?page=comments#action_12388051 ]
Siarhei Dudzin commented on JBIDE-1322:
---------------------------------------
First of all, m2eclipse does not support creation WTP-2 projects (all projects are created
as plain java projects and to add a facet I have to 'hack' the project
descriptors). Even if I manage to manually setup the project settings - deployment to a
server defined via WTP or JBoss Tools doesn't work for various reasons. For example,
at the exploded deployment location application.xml many libraries are missing, target
folder is deployed with everything else, web project is deployed exploded (also with
missing libs) but a JPA project for some reason deployed as a JAR (and there is more).
Without correctly setting classpath and dependencies those plugins can not be used with
WTP. I can't speak for q4e but I guess it's similar story especially since
it's stated on their forums that WTP support is only planned.
It would be possible as you said (once maven-eclipse-plugin supports WTP-2) to generate
the project and than use m2eclipse so that you don't need to rebuild the whole eclipse
project (and it seems to be very minor problem in comparison to not being able yet to use
WTP-2 at all) because the poms have changed. That is actually what I hear some people do
(whic is 1st - generate project with maven eclipse plugin, then enable maven support with
m2eclipse and edit project descriptors manually to support WTP-2) except that they
can't use WTP functionality for exploded deployment (for the same reasons I stated few
lines above). Even then it seems to be 'too much' tooling, that's why I am not
trying to focus on combination of plugins but at least on one (for the starters).
Actually I see two main problems:
First is that JBoss Tools doesn't support 'custom' (but standard for maven)
directory layout (hence this bug report) .
And the second - exploded deployment of such projects (generating and maintaining WTP
projects is a problem of those plugins, imho), even then I am not sure on which side the
solution for the second problem is possible (exploded deployment works almost perfectly
with maven-eclipse-plugin and RAD-6 though).
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