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 service*. *Communication*.
In the *Petals Component* list, select *JMS // petals-bc-jms*.
In the *Component Usage*, select *Consume a Petals service (or Expose it outside the bus)*.
In the *Component Version* list, select the version of the Petals-BC-JMS that you are using in Petals.
...In particular, it defines the interface, service and end-point names of the service that will be invoked when a file is added in the watched directory.
!petals-studio-tuto-consume-jms-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-consume-jms-2bis.jpg!
\\
...This page defines information which are specific to the Petals JMS component.
The required parameters are all about the JNDI properties and the JNDI-configuration of the JMS server.
The meaning of all the parameters can be read in the documentation of the [Petals-BC-JMS|petalscomponents:Petals-BC-JMS] component.
...This page requires information related to the CDK.
If the service to consume is described by a WSDL, then there is a list of the possible operations that can be invoked.
You Otherwise, you 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 local part of the invoked operation's name (WSDL operations are QNames).
...