Uploaded image for project: 'FUSE ESB'
  1. FUSE ESB
  2. ESB-709

ESB gshell needs to be properly documented

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.1.0.0-fuse
    • Fix Version/s: 4.2.0.0M1-fuse
    • Component/s: Documentation
    • Labels:
      None

      Description

      The new shell in servicemix is quite a bit different than previous servicemix versions and has been causing some confusion for customers. This change be clearly documented in the release notes, and the new syntax should be described for example stating that commands such as "features list" would now be run like "features/list". Also, as there's no documentation it's not clear how to exit a subshell, for example if I type "osgi" and enter at the console I cannot get back to the root shell with "exit", the "exit" command instead shuts down the ESB.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            kpatras Karen Patras added a comment -

            The Console Reference Guide for FUSE ESB 4.2 has been updated to correctly describe how to access and use the console commands, and how to navigate between shells. A draft of the updated guide is at: http://fuseesb.fusesource.org/docs/4.2/command_ref/index.html.

            Show
            kpatras Karen Patras added a comment - The Console Reference Guide for FUSE ESB 4.2 has been updated to correctly describe how to access and use the console commands, and how to navigate between shells. A draft of the updated guide is at: http://fuseesb.fusesource.org/docs/4.2/command_ref/index.html .

              People

              • Assignee:
                kpatras Karen Patras
                Reporter:
                stlewis Stan Lewis
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: