Abstract:
Web workflow service information may include implementations, contracts, addresses, bindings, and other information that is sprinkled throughout source files, configuration files, and other locations. A service explorer extracts service information, and visualizes service information in a form that supports navigation, thereby helping developers understand and use workflow service information. A workflow service structure underlying the visualization is constructed with the extracted service information. A hierarchical node visualization of the service structure is displayed in a service explorer GUI. A developer navigates by expanding/contracting nodes, searching nodes, selecting nodes, and running tools with node-specific information, e.g., for testing, tracing, publication, workflow design, and so on. The visualization is automatically updated after service configuration changes. Node-specific source code is displayed for contract and implementation classes, and pertinent sections of configuration files are displayed for bindings and addresses. Derivation of endpoints, bindings, and addresses are displayed for implicitly set endpoints.
Abstract:
Web workflow service information may include implementations, contracts, addresses, bindings, and other information that is sprinkled throughout source files, configuration files, and other locations. A service explorer extracts service information, and visualizes service information in a form that supports navigation, thereby helping developers understand and use workflow service information. A workflow service structure underlying the visualization is constructed with the extracted service information. A hierarchical node visualization of the service structure is displayed in a service explorer GUI. A developer navigates by expanding/contracting nodes, searching nodes, selecting nodes, and running tools with node-specific information, e.g., for testing, tracing, publication, workflow design, and so on. The visualization is automatically updated after service configuration changes. Node-specific source code is displayed for contract and implementation classes, and pertinent sections of configuration files are displayed for bindings and addresses. Derivation of endpoints, bindings, and addresses are displayed for implicitly set endpoints.
Abstract:
The present invention extends to methods, systems, and computer program products for generating service-access activities for workflow applications. Embodiments of the invention automatically generate service-access activities based on (e.g., Web) service metadata. One-click generation, together with encapsulation of configuration complexity, helps developers improve productivity and reduce the likelihood of making mistakes.