user manual

92 BES Developer’s Guide
How Borland Web Services work
</service>
<service name="Animal2" provider="java:VISIBROKER">
<parameter name="className" value="com.borland.examples.web
services.visibroker.AnimalModule.Animal"/>
<parameter name="allowedMethods" value="talk sleep"/>
<parameter name="objectName" value="corbaname::172.20.20.28:9999#USA/
California/SanMateo/BigAnimal"/>
<parameter name="locateUsing" value="ior"/>
</service>
Java:MDB provider
This provider assumes that the incoming message is meant for a message
queue or a topic. When a web service request arrives, this provider:
1 Looks up the connection factory.
2 Creates a Queue or a Topic connection.
3 Sends the message to the queue or topic.
The parameters are:
■
connectionType: The type of connection. Can take value QUEUE or TOPIC.
■
connectionFactory:; The name of the connection factory. This is the serial
name and not the JNDI name of the object. For example: serial://jms/qcf.
■
destination: The name of the queue or topic to which the message is sent.
This is the serial name and not the JNDI name of the object. For example:
serial://jms/q
Examples:
<service name="MDBQService" provider="java:MDB">
<parameter name="ConnectionType" value="QUEUE"/>
<parameter name="ConnectionFactory" value="serial://jms/qcf"/>
<parameter name="Destination" value="serial://jms/"/>
</service>
How Borland Web Services work
1 The web services server receives an XML SOAP message from a client.
2 It then:
a Interprets the SOAP message.
b Extracts the SOAP service name.
c Determines the appropriate provider who can respond to this service.
3 The mapping between the SOAP service and the type of provider is
obtained from the Web Service Deployment Descriptor (WSDD) as part of
WAR deployment.
4 The message is then passed onto the right provider. For information about
the different ways in which each provider deals with the message, go to: