...
- myComponent subscribes to the "demo.org.servicemix.source" topic. Through its template property, myComponent uses JmsFactory to listen on
port 61616 via ActiveMQConnectionFactory. - When JMSClient is executed, it tries to make a connection to the topic demo.org.servicemix.source at port 61616
- It then send a text message through this connection and waits for a response.
- myComponent receives the message and transmit it to ProcessSVC which is probably the PXE BPEL engine as specified in the destinationService
property in the servicemix.xml file. - When the transmission is successful myComponent send a reply to the JMSClient and "Response was @response" is printed on the console.
Otherwise "Response time out" is printed.
...
Component or Bean ID | Description |
---|---|
myComponent | This JMS binding component subscribes to the "demo.org.servicemix.source" topic via its defaultDestinationName |
pxe:ProcessSVC | PXE is a runtime component for executing processes defined by the BPEL4WS 1.1 specification and forthcoming WS-BPEL 2.0 OASIS standard. PXE BPEL engine uses JMX to provide management and introspection functionality. Business Process Execution Language (BPEL) defines a notation for specifying business process behavior |
Useful Code Hints
This section describes the start-up sequence and how the ServiceMix container interacts with the BPEL application. The Java class files are located in the servicemix-1.0.1.jar file in the ServiceMix installation directory. To look at the Java source code, unjar and decompile the .class files or download the source code. Please note: the downloadable source code is slightly different than the compiled binary code.
...