As we are starting the ServiceMix in embedded mode it will generate
exceptions in the console. These errors can be ignored. Instead you can concentrate
on the application logging which is reproduced here:
[junit] JmsInOnlyAsyncTest.testJmsInOnlySync - Start...
[junit] JmsInOnlyAsyncTest.testJmsInOnlySync - Transaction Committed.
[junit] INFO - MessageList - Waiting for message to
arrive
[junit] INFO - MessageList - End of wait for 1001
millis
[junit] JmsInOnlyAsyncTest.testJmsInOnlySync - End.
[junit] JmsInOnlyAsyncTest.tearDown...
[junit] Closing down the Spring ApplicationContext
Chapter 17
[ 383 ]
We can see that the MessageList waits for messages which it receives at the end of
1001 milliseconds. The following screenshot shows the ESB console:
Sample demonstrating Security
The security in ServiceMix can be configured at multiple levels and at multiple
layers. In this section we will demonstrate a simple security configuration for the
servicemix-http component. We will configure HTTP basic authentication and as
per that, when a client tries to access a resource marked as protected in the server,
the server prompts for a username and password combination.
Pages:
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502