E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (8)
View Page History
...
{section} \\
A wizard opens, showing three drop-down lists.
A wizard opens, showing three drop-down lists.
In the *Use Case* list, select *Consume or Call a Petals technical service*. *Communication*.
In the *Petals Component* list, select *SOAP // petals-bc-soap*.
In the *Component Usage* list, select *Consume a Petals service (or Expose it outside the bus)*.
In the *Component Version* list, select the version of the Petals-BC-SOAP that you are using in Petals.
...In particular, it defines the interface, service and end-point names of the service that will be exposed as a Web Service.
!petals-studio-tuto-consumes-soap-2.jpg!
\\
{note}
A service is identified by a triplet, interface, service and end-point names. This triplet is unique in a Petals topology.
When you consume a service, the service is selected in a set. This set is defined by the invocation properties.
If the 3 fields are set in the consume properties, then the set will contain at most 1 result (there can be only 1 service with this ID).
If 2 fields are set, then the third one is considered as a wildcard and the set will larger.
Consume possibilities are the following ones:
* By interface, service and end-point names.
* By interface and service names.
* By interface name only.
{note}
\\
\\
{note}
A service is identified by a triplet, interface, service and end-point names. This triplet is unique in a Petals topology.
When you consume a service, the service is selected in a set. This set is defined by the invocation properties.
If the 3 fields are set in the consume properties, then the set will contain at most 1 result (there can be only 1 service with this ID).
If 2 fields are set, then the third one is considered as a wildcard and the set will larger.
Consume possibilities are the following ones:
* By interface, service and end-point names.
* By interface and service names.
* By interface name only.
{note}
\\
You can obviously fill-in these fields by hand.
However, the most efficient way is to use the [Petals Services explorer|Getting familiar with the Petals Services view] (provided it was populated).
Click *Select a service*. A selection dialog shows up, providing filtering assistance.
However, the most efficient way is to use the [Petals Services explorer|Getting familiar with the Petals Services view] (provided it was populated).
Click *Select a service*. A selection dialog shows up, providing filtering assistance.
!petals-studio-tuto-consumes-soap-2bis.jpg!
\\
...This page defines information which are specific to the Petals SOAP component.
The only one you have to fill-in is the *address* *service-name* field.
It defines the suffix of the URL at which the web service will be available.
...This page requires information related to the CDK.
Usually, you would have three parameters to complete here (others are optional or have default values):
* The name space of the invoked operation's name (WSDL operations are QNames).
* The local part of the invoked operation's name (WSDL operations are QNames).
* The Message Exchange Pattern (MEP).
* The name space of the invoked operation's name (WSDL operations are QNames).
* The local part of the invoked operation's name (WSDL operations are QNames).
* The Message Exchange Pattern (MEP).
In the case of the SOAP component, version 4.x, you only have one field to set: the MEP.
The Message Exchange Pattern (MEP) defines the interactions between the SOAP client and the web service. Unfortunately, this version of the SOAP component cannot guess the MEP from the invoked operation. This is why it has to be set in the configuration.
The Message Exchange Pattern (MEP) defines the interactions between the SOAP client and the web service. Unfortunately, this version of the SOAP component cannot guess the MEP from the invoked operation. This is why it has to be set in the configuration.
\\
However, regarding the SOAP component, these fields do not need to be filled-in.
Indeed, the SOAP component can deduce the invoked operation and the MEP from the SOAP request.
{tip}
When you expose a Petals Service as a Web Service, do not specify the operation and the MEP in the CDK page.
Their values will be deduced from the SOAP request by the component.
{tip}
\\
Indeed, the SOAP component can deduce the invoked operation and the MEP from the SOAP request.
{tip}
When you expose a Petals Service as a Web Service, do not specify the operation and the MEP in the CDK page.
Their values will be deduced from the SOAP request by the component.
{tip}
\\
The meaning of all the CDK parameters for SOAP can be found in the documentation of the [Petals-BC-SOAP|petalscomponents:Petals-BC-SOAP] component.
...