Announcement Announcement Module
Collapse
No announcement yet.
Web Flow XML Editor available Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Web Flow XML Editor available

    Hello community,

    the latest nightly build on our way towards Spring IDE 2.0 M3 contains XML editing support for Spring Web Flow flow definitions and Web Flow's 2.0 configuration namespace.

    More details are available at http://springide.org/project/wiki/WebflowXmlEditor. The build can be installed from our nightly build updatesite (http://springide.org/updatesite_nightly/).

    Please provide us with your thoughts and feedback on this, as we want to make the Web Flow support as valuable as possible. Comments in this thread are welcome.

    Cheers
    Christian

  • #2
    Thanks!

    I'll jump in and say 'thanks'...lots of hard work must have gone into this.

    *My* major issue at this point in time is not having a graphical visualisation tool. Managers LOVE pretty pictures and I'd like to be able to give them what they want...

    Less facetiously, I have a flow with about 60 nodes now and keeping the complexity straight in my head is becoming an issue that a visualiser would REALLY help with. It would also be a very useful tool to have on hand when sitting down with clients...the people who are actually going to be driving my app through its flow, and also with the people who are designing the business processes that my flow is supposed to mimic.

    Looking forward to M3!

    Cheers,

    Alph

    Comment


    • #3
      One thing I noticed that since installing the nightly build, I now have a menu item called %refactorMenu.label !

      That could be because I did a Callisto update as well, but might be worth investigating.

      I do agree with the other post that the most important thing is the visualization, I can cope with hand coding the XML, but the pretty picture is better than a thousand words/lines of XML !

      Excellent plugin none the less !

      Comment


      • #4
        Originally posted by Paul Newport View Post
        One thing I noticed that since installing the nightly build, I now have a menu item called %refactorMenu.label !
        Hey, you came across a newly added feature: Refactoring of Java elements triggered form the Spring XML files; just use the normal Shift+Alt+R and Shift+Alt+V on class names, property names and bean ids. I've created a ticket for the missing menu label. http://springide.org/project/ticket/485

        I do agree with the other post that the most important thing is the visualization, I can cope with hand coding the XML, but the pretty picture is better than a thousand words/lines of XML !
        If you guys are keen on getting read-only visualization of flow definitions, you will be happy to hear that this will be part of coming M3 (due ~next week).

        Christian

        Comment


        • #5
          Originally posted by cdupuis View Post

          If you guys are keen on getting read-only visualization of flow definitions, you will be happy to hear that this will be part of coming M3 (due ~next week).

          Christian
          I noticed the refactor thing on the context menu as well, but the missing label threw me a bit.

          Great on the visualisation bit !

          Comment


          • #6
            I'm getting error

            org.osgi.framework.BundleException: The activator org.springframework.ide.eclipse.beans.core.BeansCo rePlugin for bundle org.springframework.ide.eclipse.beans.core is invalid

            Comment


            • #7
              Whopee! Visualisation!

              I'm SOOO looking forward to M3.

              Alph

              Comment


              • #8
                Here here to Web Flow visualization!!!!!

                Comment


                • #9
                  Originally posted by cdupuis View Post
                  Hey, you came across a newly added feature: Refactoring of Java elements triggered form the Spring XML files; just use the normal Shift+Alt+R and Shift+Alt+V on class names, property names and bean ids. I've created a ticket for the missing menu label. http://springide.org/project/ticket/485

                  If you guys are keen on getting read-only visualization of flow definitions, you will be happy to hear that this will be part of coming M3 (due ~next week).

                  Christian
                  I am demoing SWF to developers on Monday, it would be great if it was there before then - no pressure ;-)

                  Comment


                  • #10
                    errors with latest plugin

                    Odd one this one.

                    I have the plugin working fine on my laptop. I copy the entire eclipse installation directory to my work desktop, and get this when I try and show a graph view:

                    The only differences are JRE level the work is JRE 1.5.0_10 and laptop is _11, and the work PC is behind a firewall.

                    Code:
                    java.lang.ClassNotFoundException: org.springframework.ide.eclipse.beans.ui.navigator.BeansExplorer
                    	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
                    	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:347)
                    	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
                    	at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
                    	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:278)
                    	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
                    	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1245)
                    	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:147)
                    	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759)
                    	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
                    	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
                    	at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:242)
                    	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
                    	at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:238)
                    	at org.eclipse.ui.internal.registry.ViewDescriptor.createView(ViewDescriptor.java:69)
                    	at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:292)
                    	at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:197)
                    	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
                    	at org.eclipse.ui.internal.Perspective.showView(Perspective.java:1675)
                    	at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:987)
                    	at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:968)
                    	at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:3514)
                    	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
                    	at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:3511)
                    	at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:3487)
                    	at org.eclipse.ui.handlers.ShowViewHandler.openView(ShowViewHandler.java:148)
                    	at org.eclipse.ui.handlers.ShowViewHandler.openOther(ShowViewHandler.java:104)
                    	at org.eclipse.ui.handlers.ShowViewHandler.execute(ShowViewHandler.java:70)
                    	at org.eclipse.ui.internal.ShowViewMenu$3.run(ShowViewMenu.java:114)
                    	at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
                    	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
                    	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
                    	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
                    	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
                    	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
                    	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
                    	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
                    	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
                    	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
                    	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
                    	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
                    	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
                    	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
                    	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
                    	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
                    	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
                    	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
                    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    	at java.lang.reflect.Method.invoke(Method.java:324)
                    	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
                    	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
                    	at org.eclipse.core.launcher.Main.run(Main.java:977)
                    	at org.eclipse.core.launcher.Main.main(Main.java:952)

                    Comment


                    • #11
                      Did you try a -clean start on Eclipse?

                      Comment


                      • #12
                        Originally posted by Paul Newport View Post
                        I copy the entire eclipse installation directory to my work desktop, and get this when I try and show a graph view:

                        The only differences are JRE level the work is JRE 1.5.0_10 and laptop is _11, and the work PC is behind a firewall.
                        Somedays the BeansExplorer extended Eclipse 3.2's CommonNavigator (part of the Common Navigator Framework) and overwrote CommonNavigator's implementation of the interface "org.eclipse.ui.part.IShowInTarget" to provide a different behaviour [finally "super.show(context)" was called]. With a newer version of Eclipse the CommonNavigator didn't implemented this interface anymore and our base class implementing "org.eclipse.ui.part.IShowInTarget" wasn't available anymore. Since 16th of January this is fixed by letting BeansExplorer implementing "org.eclipse.ui.part.IShowInTarget" and not calling super anymore.

                        Ok, this lengthy description leads to the following recommendation:

                        It seems that you're running an outdated version of the "*.beans.ui.navigator" plugin. So please delete all Spring IDE plugins "org.springframework.ide.eclipse.*" from your Eclipse installation and install Spring IDE from scratch via the update manager.

                        If you're using our nightly builds then I would like to recommend to create a separate Eclipse product extension exclusively for Spring IDE and delete the content of this extension before installing a new nightly build of Spring IDE. This "clean install" of Spring IDE's nightly builds is necessary because we're modifying the OSGI bundles as well. E.g. for the Spring OSGI bundle (provides the upcoming version 2.0.3) we're updating the spring.jar from their nightly builds without modifying the bundle's version number.

                        Comment


                        • #13
                          Thanks for this.

                          I think half the problem is related to our network/firewall at work - as everything works fine from home I'll just carry on with the home environment for the moment.

                          Comment


                          • #14
                            Originally posted by ronwheeler View Post
                            Did you try a -clean start on Eclipse?
                            Yes ta but the same effect. Don't worry, I think it's a work networking/firewall issue.

                            Comment


                            • #15
                              There is no editor

                              Hello,

                              I would like to ask you if I do ane mistake because I have installed nightly build from your update site (this is version before M3). Everythink seems to be installed correctly but when I open my xml web flow file there is nothing in outline just classic xml outline.

                              Thank you for your answers.

                              Comment

                              Working...
                              X