Integrating MagooClient with Apache ActiveMQ/CXF(4)

MagooClient: Transform Configuration

As can be seen from the scenario overview, although MagooClient receives a rectifyPackingSlip message from the ProcessorService, it must reply with a processPackingSlip message in order to match the ProcessorService WSDL. Therefore an XML transform must be applied to convert the message to the correct format before re-submitting it to the process queue. This transform should be automatically applied when the user clicks on Reply to respond to the rectifyPackingSlip request.

 

MagooClient provides a transform generator to allow XSL-based transforms between message types to be generated. For convenience, a transform is provided as part of the MagooLogisticsForms.zip. To configure this, select Message Types… from the Configure menu in the main MagooClient window. The set of currently configured message types is displayed. Double-click on the MagooLogistics_rectifyPackingSlip type and then select the Transforms tab.

 

Use the Add… button to add the RectifyToProcess.xsl, which is located within the SuperLogisticsForms directory, as a possible request transform. Select this new entry in the transform table and click on Default Reply. This means that the transform will be automatically applied when the user clicks on Reply.

 

 

To test this, select the received rectifyPackingSlip message in the MagooClient inbox and click on Reply. A new draft processPackingSlip message will be created using the transformed contents of the original rectify message. Note that the To: line is populated with the endpoint details for the ProcessorService i.e. queue:dynamicQueues/demo.process.

 

Click on the Send button and the message will be put onto the process queue. As the ProcessorService simply routes all received messages back onto the rectify queue, you will see a new rectifyPackingSlip appear immediately in the inbox again!

 

The above provides a good illustration of how MagooClient can be used in the prototyping, development and testing phases to exercise message exchange patterns across JMS. In the next section we’ll see how the form look and feel can be tailored for less-technical users to allow MagooClient to be utilized in real-world business applications.

 

 

< Previous 1 2 3 4 5 Next >