7 Replies Latest reply on Mar 4, 2008 6:16 AM by Max Rydahl Andersen

    Using Seam 2.0.1.CR1 with JBoss Tools 2.0.0.GA

    John Skillings Newbie

      Hi all,

      I am currently learning Seam, and thought I would use the JBoss Tools 2.0.0.GA instead of using the command line "seam setup".

      During the installation, I noticed that out of the box, JBoss Tools 2.0.0.GA is configured with Seam 1.2 run time and does not allow it to run with Seam 2.0.1.CR1. Also, there are changes in the code generated / directory structure / config files generated using the version of Seam 1.2 runtime integrated in JBoss Tools 2.0.0.GA to what is generated by running "seam setup" in Seam 2.0.1.CR1.

      Couple of quick questions:

      1) Is there a way to integrate JBoss Tools 2.0.0.GA with Seam 2.0.1.CR1?

      2) If so, how to go about doing it?

      Thank you.

      Best regards,

      John

        • 1. Re: Using Seam 2.0.1.CR1 with JBoss Tools 2.0.0.GA
          Max Rydahl Andersen Master

          JBoss tools is *not* preconfigured to Seam 1.2; only JBoss Developer Studio has that preconfigured.

          Both can use Seam 2, you just need to choose Seam 2 and not Seam 1.2 in the new project and/or runtime setup.

          • 2. Re: Using Seam 2.0.1.CR1 with JBoss Tools 2.0.0.GA
            kevin o'brien Newbie

             

            "max.andersen@jboss.com" wrote:
            JBoss tools is *not* preconfigured to Seam 1.2; only JBoss Developer Studio has that preconfigured.

            Both can use Seam 2, you just need to choose Seam 2 and not Seam 1.2 in the new project and/or runtime setup.



            Now that Seam 2.0.1.GA is out, can you use JBoss Tools 2.0.0.GA with Seam 2.0.1.GA? Or should we wait for a release of JBoss Tools whose release # matches that of the Seam version?



            • 3. Re: Using Seam 2.0.1.CR1 with JBoss Tools 2.0.0.GA
              Max Rydahl Andersen Master

              did you see any issues ? It should just work.

              • 4. Re: Using Seam 2.0.1.CR1 with JBoss Tools 2.0.0.GA
                Antoine Sabot-Durand Newbie

                I've got a light issue migrating from seam 2.0.0 to 2.0.1 in JBDS (It should be the same with Jboss Tools)
                My project is an EJB3 project targeting JBoss 4.2.2, when I replace jboss-seam.jar in the EAR project with version 2.0.1 I cannot open the "J2EE dependencies" panel in the EJB or War project properties. Here is my workspace log :


                !ENTRY org.eclipse.wst.validation 4 0 2008-02-05 16:23:35.639
                !MESSAGE
                *** ERROR ***: Tue Feb 05 16:23:35 CET 2008 No IModelProvider exists for virtual component P/Zanzibar-ear Zanzibar-ear/EarContent/jboss-seam.jar of version: null
                
                !ENTRY org.eclipse.jface 4 2 2008-02-05 16:23:35.641
                !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
                !STACK 0
                java.lang.NullPointerException
                 at org.eclipse.jst.j2ee.application.internal.operations.ClassPathSelection.initializeElements(ClassPathSelection.java:544)
                 at org.eclipse.jst.j2ee.application.internal.operations.ClassPathSelection.<init>(ClassPathSelection.java:142)
                 at org.eclipse.jst.j2ee.internal.common.ClasspathModel.createClassPathSelection(ClasspathModel.java:260)
                 at org.eclipse.jst.j2ee.internal.common.ClasspathModel.initializeSelection(ClasspathModel.java:244)
                 at org.eclipse.jst.j2ee.internal.common.ClasspathModel.getClassPathSelection(ClasspathModel.java:286)
                 at org.eclipse.jst.j2ee.internal.ClasspathTableManager.initializeEJBClientDefaults(ClasspathTableManager.java:110)
                 at org.eclipse.jst.j2ee.internal.ClasspathTableManager.createRadioGroup(ClasspathTableManager.java:167)
                 at org.eclipse.jst.j2ee.internal.ClasspathTableManager.fillComposite(ClasspathTableManager.java:94)
                 at org.eclipse.jst.j2ee.internal.JARDependencyPropertiesPage.createTableComposite(JARDependencyPropertiesPage.java:415)
                 at org.eclipse.jst.j2ee.internal.JARDependencyPropertiesPage.createListGroup(JARDependencyPropertiesPage.java:372)
                 at org.eclipse.jst.j2ee.internal.JARDependencyPropertiesPage.createContents(JARDependencyPropertiesPage.java:282)
                 at org.eclipse.jst.j2ee.internal.J2EEDependenciesPage.createNonEARContent(J2EEDependenciesPage.java:138)
                 at org.eclipse.jst.j2ee.internal.J2EEDependenciesPage.createContents(J2EEDependenciesPage.java:75)
                 at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233)
                 at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1456)
                 at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1213)
                 at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
                 at org.eclipse.core.runtime.Platform.run(Platform.java:857)
                 at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
                 at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199)
                 at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1207)
                 at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:433)
                 at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:698)
                 at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:842)
                 at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
                 at org.eclipse.core.runtime.Platform.run(Platform.java:857)
                 at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
                 at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199)
                 at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:840)
                 at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1642)
                 at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1095)
                 at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1009)
                 at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:476)
                 at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:369)
                 at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
                 at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:365)
                 at org.eclipse.jface.window.Window.create(Window.java:426)
                 at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1081)
                 at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:81)
                 at org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:175)
                 at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:154)
                 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)
                


                reverting to version 2.0.0 jar correct the problem. Eclipse seems to look for something in the jar that it doesn't find. However the project can be deployed and run with 2.0.1 jar the only trouble is that we can't edit J2EE dependencies anymore

                regards

                Antoine

                • 5. Re: Using Seam 2.0.1.CR1 with JBoss Tools 2.0.0.GA
                  Alexey Kazakov Master

                   

                  "Antoine Sabot-Durand" wrote:
                  Eclipse seems to look for something in the jar that it doesn't find. However the project can be deployed and run with 2.0.1 jar the only trouble is that we can't edit J2EE dependencies anymore

                  Yes, it is a bug of WTP.
                  It will be fixed in WTP 2.0.2.
                  See http://jira.jboss.com/jira/browse/JBIDE-1716

                  • 6. Re: Using Seam 2.0.1.CR1 with JBoss Tools 2.0.0.GA
                    Leonids Maslovs Newbie

                     

                    "max.andersen@jboss.com" wrote:
                    JBoss tools is *not* preconfigured to Seam 1.2; only JBoss Developer Studio has that preconfigured.

                    Both can use Seam 2, you just need to choose Seam 2 and not Seam 1.2 in the new project and/or runtime setup.



                    What is the correct answer? :) Could we just use Jboss Tools 2.0.0. with Seam 2.0.1-GA?