...
Component or Bean ID | Description |
---|---|
myComponent | This JMS binding component subscribes to the "demo.org.servicemix.source" topic via its defaultDestinationName |
pxe:ProcessSVC | This is the component in which the JMS binding connects to. 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 |
broker | The broker bean uses the activemq.xml file to configure the message broker, which handles the JMS messages for the components that require JMS messaging services. |
transactionManager | This bean is configured to be the default transaction manager for the jbi container. jencks is configured to use the default transaction manager. This transaction manager provides transactional services between the resource adapter (in this case the ActiveMQ resource adapter provided by the jencks JCA container) and components the jbi container. |
jmsFactory | This bean listens on port 61616 and provides a pooled ActiveMQ connection. |
Summarizing, when the ServiceMix container instantiates an MBean it firsts sets the property values if there are any, then calls the init() method of the class and its' parent classes, if applicable. Then it calls the start() method of the class. When a Spring bean starts up, the properties are set and then the afterPropertiesSet() method is called.
...