Dashboard > WSO2 Mashup Server > Home > Mashup UI requirements
  WSO2 Mashup Server Log in | Register   View a printable version of the current page.  
  Mashup UI requirements
Added by Thilina Gunarathne , last edited by Jonathan Marsh on May 07, 2007  (view change)
Labels: 
(None)

  • Tabs
    • Index tab
    • Monitor
    • Tools
  • Index tab
    • Side bar with services list
      1. Title
      2. small description
      3. ON/OFF+ service status button
      4.  Edit button
      5. Show in Widget Button
    • Two columns of Widgets
  • Widget has two panes
    1. Config links
    2. UI (try it)
  • Include these in the widget or in edit window
    1. Indication (and toggle) of whether this service is running or not.
    2. link to WSDL (let's assume XSD and Policy are embedded for now)
    3. links to stubs (JS, E4X)
    4. link to TryIt UI.
    5. link to the source code
    6. available and engaged binding types (soap 1.1, soap 1.2, http, custom (point to a WSDL binding) etc.)
    7. configuration details (like what? turning off ?src, attaching description)
    8. available and engaged modules (WS-Addressing, MTOM, etc.) (do through pointing to a WSDL binding.)
    9. available and engaged modules (throttling, etc.) (post-alpha 1)
    10. any options for engaged modules (post-alpha 1)
    11. links for tooling if there is any (how are we going to tell that anyway?) (post-alpha 1)
    12. links to custom UIs (how do we tell that anyway?)  (post-alpha 1)
    13. link to health statistics about the service (post-alpha 1)

Powered by a free Atlassian Confluence Open Source Project License granted to WSO2 Inc.. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators