Bottom-up development method - Revision history

Anonymous: /* Example */

2012-02-13T10:33:19Z

‎Example

2012-02-13T09:19:53Z

‎Wizard bottom-up development method

2012-02-09T21:19:32Z

‎Example

2012-02-08T09:18:33Z

‎Example

2012-02-08T09:16:26Z

‎Example

2012-02-07T10:58:04Z

2012-02-07T10:43:26Z

2012-02-07T10:40:41Z

2012-02-06T09:01:27Z

‎Wizard bottom-up development method

2012-02-05T10:31:50Z

‎Example

@@ Line 64: / Line 64: @@
 | This operation gets the user input and returns it in uppercase.
 | [[toupper_ws bottom-up method]]
 |}

@@ Line 11: / Line 11: @@
 *Soap Action and the mapped operation name to the WebService, This optional property is set on an outgoing SOAP/JMS request message to indicate the SoapAction value associated with the Web Services request. This property is similar to the SoapAction HTTP header used when transporting Web Service requests over an HTTP transport. The value of the SoapAction property is a URI identifying the intent of the SOAP request. If the SoapAction property is specified, it is used by the server component to determine the target of the request. The SOAP specification places no restrictions on the format or specificity of the URI or that it is resolvable. Typically, this property is set to the SoapAction value from the WSDL document.
 [[File:ws3.png|thumb|WebService Wizard third window]]
-On the third page you can choose your preferred transport protocol. Properties indicate the version number of the protocol used by the client and server.If the SOAP request message represents a two-way request, the client component must set the JMS message.
+On the third page you can choose your preferred [[GVWebServices#Transport|transport]] protocol. Properties indicate the version number of the protocol used by the client and server.If the SOAP request message represents a two-way request, the client component must set the JMS message.
 *Soap Transport
 *Soap12 Transport

@@ Line 63: / Line 63: @@
 | toupper
 | This operation gets the user input and returns it in uppercase.
-| [[Example 2]]
+| [[toupper_ws bottom-up method]]
 |}

@@ Line 58: / Line 58: @@
 | echo
 | This operation gets the user input and returns itself to user.
-| Example [[echo_ws bottom-up method]]
+| [[echo_ws bottom-up method]]
 |-
 | toupper_ws

@@ Line 58: / Line 58: @@
 | echo
 | This operation gets the user input and returns itself to user.
-| [[Example 1]]
+| Example [[echo_ws bottom-up method]]
 |-
 | toupper_ws

@@ Line 28: / Line 28: @@
 [[File:ws4.png|thumb|WebService Wizard fourth window]]
 On the last page you must choose:
-*The Web Service input type
+*The Web Service input type, used to choose what must be passes as input to the workflow:
 *The [[Data provider]] name, used to adapt the workflow output to the Web service output
 And optionally:

@@ Line 1: / Line 1: @@
 == '''Wizard bottom-up development method''' ==
 [[File:ws1.png|thumb|WebService Wizard first window]]
-Wizard bottom-up development method helps user to create a {{GVESB}} service as a [http://en.wikipedia.org/wiki/Web_service Web Service]. Right click on GVServices-->Services label and select "Wizard New WebService...".
+Wizard bottom-up development method helps user to publish a {{GVESB}} service as a [http://en.wikipedia.org/wiki/Web_service Web Service]. Right click on GVServices-->Services label and select "Wizard New WebService...".
 New WebService Wizard window will be open.
 Fill the window fields as following:

@@ Line 5: / Line 5: @@
 Fill the window fields as following:
 *In the "WebService name" field set the WebService name that you want to publish
-*In the "target namespace" field you can change the default operation target namespace proposed
+*In the "target namespace" field you can change the proposed default operation target namespace
-*In the "Operation" field choose the operation to bind from list proposed
+*In the "Operation" field choose the operation to bind from the proposed list
 [[File:ws2.png|thumb|WebService Wizard second window ]]
 On the second page you can change:
@@ Line 29: / Line 29: @@
 On the last page you must choose:
 *The Web Service input type
-*The [[Data provider]] name
+*The [[Data provider]] name, used to adapt the workflow output to the Web service output
 And optionally:
 *The input XSD name
@@ Line 36: / Line 36: @@
 *HTTP or HTTPS
 *Web Service's target namespace is in the XSD or it is that proposed by default
-*Use the original wsdl or not
+*Use the original, already provided, wsdl or create a new one
 == Example ==

@@ Line 46: / Line 46: @@
+!
 |-
-| Credit Card
+| echo_ws
-| withdrawal
+| echo
-| This operation.............................................................
+| This operation gets the user input and returns itself to user.
 | [[Example 1]]
 |-
-| Credit Card
+| toupper_ws
-| Saldo
+| toupper
-| This operation.............................................................
+| This operation gets the user input and returns it in uppercase.
 | [[Example 2]]
 |}