Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.3.x
    • Fix Version/s: 3.3.0.Final-SOA
    • Component/s: esb
    • Labels:
      None

      Description

      Develop the beginnings of some SwitchYard tooling to support ongoing SwitchYard development.

        Gliffy Diagrams

          Activity

          Hide
          bfitzpat Brian Fitzpatrick added a comment -
          Show
          bfitzpat Brian Fitzpatrick added a comment - Committed to my workspace - https://svn.jboss.org/repos/jbosstools/workspace/bfitzpat/org.jboss.tools.esb.switchyard.ui Added new readme.txt
          Hide
          bfitzpat Brian Fitzpatrick added a comment -

          Contents of readme:

          ****************************
          Using the SwitchYard Editor
          v.0.4
          ****************************
          The SwitchYard Editor relies on new technology available from Eclipse - the Sapphire UI framework and the Graphiti UI framework.

          Graphiti has been at use at Eclipse for a couple of releases now (Helios and now Indigo). Sapphire is a maturing framework new
          to the Indigo release that is stable, but still early in its lifecycle. As such, it is not part of the Eclipse release train
          this go around and is in Incubation status.

          You will need to install Indigo for this tool to work. An early milestone (M6a) of it is available here:
          http://www.eclipse.org/downloads/packages/release/indigo/m6

          I recommend grabbing the Eclipse IDE for Java EE Developers.

          Once you have that up and running, install the latest Graphiti build from this update site:
          http://download.eclipse.org/graphiti/updates/milestones/

          And the latest Sapphire 0.3.x build from this nightly update site:
          https://hudson.eclipse.org/hudson/job/sapphire-0.3.x/

          Then you should be able to build the SwitchYard Editor plug-in and run it in a new Eclipse Runtime Configuration instance.

          At this point you need to change the name of the SwitchYard configuration file to "switchyard.xml" but it opens and can
          edit the switchyard.xml file in the "sample2" directory in the editor project.

          The graphical diagram at this point is mostly useless, but will gain functionality over time as Sapphire matures.

          Show
          bfitzpat Brian Fitzpatrick added a comment - Contents of readme: **************************** Using the SwitchYard Editor v.0.4 **************************** The SwitchYard Editor relies on new technology available from Eclipse - the Sapphire UI framework and the Graphiti UI framework. Graphiti has been at use at Eclipse for a couple of releases now (Helios and now Indigo). Sapphire is a maturing framework new to the Indigo release that is stable, but still early in its lifecycle. As such, it is not part of the Eclipse release train this go around and is in Incubation status. You will need to install Indigo for this tool to work. An early milestone (M6a) of it is available here: http://www.eclipse.org/downloads/packages/release/indigo/m6 I recommend grabbing the Eclipse IDE for Java EE Developers. Once you have that up and running, install the latest Graphiti build from this update site: http://download.eclipse.org/graphiti/updates/milestones/ And the latest Sapphire 0.3.x build from this nightly update site: https://hudson.eclipse.org/hudson/job/sapphire-0.3.x/ Then you should be able to build the SwitchYard Editor plug-in and run it in a new Eclipse Runtime Configuration instance. At this point you need to change the name of the SwitchYard configuration file to "switchyard.xml" but it opens and can edit the switchyard.xml file in the "sample2" directory in the editor project. The graphical diagram at this point is mostly useless, but will gain functionality over time as Sapphire matures.
          Hide
          bfitzpat Brian Fitzpatrick added a comment -

          This has been shifted to Rob Cernich, so am closing this initial JIRA in favor of individual new bugs.

          Show
          bfitzpat Brian Fitzpatrick added a comment - This has been shifted to Rob Cernich, so am closing this initial JIRA in favor of individual new bugs.

            People

            • Assignee:
              bfitzpat Brian Fitzpatrick
              Reporter:
              bfitzpat Brian Fitzpatrick
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development