diff --git a/docs/src/reference/docbook/aggregator.xml b/docs/src/reference/docbook/aggregator.xml index 5ef9fe7f33..014e4062bc 100644 --- a/docs/src/reference/docbook/aggregator.xml +++ b/docs/src/reference/docbook/aggregator.xml @@ -260,7 +260,7 @@ Spring Integration provides an out-of-the box implementation for ReleaseStrategy, the - SequenceSizerReleaseStrategy. This implementation uses the + SequenceSizeReleaseStrategy. This implementation uses the SEQUENCE_NUMBER and SEQUENCE_SIZE of the arriving messages for deciding when a message group is complete and ready to be aggregated. As shown above, it is also the default strategy. @@ -683,7 +683,7 @@ }]]> The expireMessageGroups method can be called with a timeout value: - any message older than the current time minus this value wiull be expired, + any message older than the current time minus this value will be expired, and have the callbacks applied. Thus it is the user of the store that defines what is meant by message group "expiry". diff --git a/docs/src/reference/docbook/endpoint.xml b/docs/src/reference/docbook/endpoint.xml index 4d77f11768..819fdc5698 100644 --- a/docs/src/reference/docbook/endpoint.xml +++ b/docs/src/reference/docbook/endpoint.xml @@ -65,7 +65,7 @@ subscribableChannel.subscribe(messageHandler); Since a handler that is subscribed to a channel does not have to actively poll that channel, this is an Event Driven Consumer, and the implementation provided by Spring Integration accepts a a SubscribableChannel and a MessageHandler: - SubscribableChannel channel = (SubscribableChannel) context.getBean("subscribableChannel"); + SubscribableChannel channel = context.getBean("subscribableChannel", SubscribableChannel.class); EventDrivenConsumer consumer = new EventDrivenConsumer(channel, exampleHandler); @@ -76,7 +76,7 @@ EventDrivenConsumer consumer = new EventDrivenConsumer(channel, exampleHandler); Spring Integration also provides a PollingConsumer, and it can be instantiated in the same way except that the channel must implement PollableChannel: - PollableChannel channel = (PollableChannel) context.getBean("pollableChannel"); + PollableChannel channel = context.getBean("pollableChannel", PollableChannel.class); PollingConsumer consumer = new PollingConsumer(channel, exampleHandler); @@ -131,10 +131,10 @@ consumer.setReceiveTimeout(5000); PollingConsumer consumer = new PollingConsumer(channel, handler); -TaskExecutor taskExecutor = (TaskExecutor) context.getBean("exampleExecutor"); +TaskExecutor taskExecutor = context.getBean("exampleExecutor", TaskExecutor.class); consumer.setTaskExecutor(taskExecutor); -PlatformTransactionManager txManager = (PlatformTransationManager) context.getBean("exampleTxManager"); +PlatformTransactionManager txManager = context.getBean("exampleTxManager", PlatformTransationManager.class); consumer.setTransactionManager(txManager); The examples above show dependency lookups, but keep in mind that these consumers will most often be configured as Spring bean definitions. In fact, Spring Integration also provides a diff --git a/docs/src/reference/docbook/http.xml b/docs/src/reference/docbook/http.xml index 621b1f6224..f7fc62d10b 100644 --- a/docs/src/reference/docbook/http.xml +++ b/docs/src/reference/docbook/http.xml @@ -105,7 +105,8 @@ By default the HTTP request will be generated using an instance of Si To configure an inbound http channel adapter which is an instance of HttpInboundEndpoint configured not to expect a response. - ]]> + ]]> To configure an inbound http gateway which expects a response. diff --git a/docs/src/reference/docbook/jms.xml b/docs/src/reference/docbook/jms.xml index 5fda3a258a..99fd6e42f7 100644 --- a/docs/src/reference/docbook/jms.xml +++ b/docs/src/reference/docbook/jms.xml @@ -155,7 +155,7 @@ As with anything else, Gateway invocation might result in error. - By default Producer will not be notified of the errors thta might have occurredon ythe consumer side and will time out waiting for + By default Producer will not be notified of the errors that might have occurred on the consumer side and will time out waiting for the reply. However there might be times when you want to communicate an error condition back to the consumer, in other words treat the Exception as a valid reply by mapping it to a Message. To accomplish this JMS Inbound Gateway provides support for a Message Channel to which errors diff --git a/docs/src/reference/docbook/mail.xml b/docs/src/reference/docbook/mail.xml index 842224a0eb..7f501d369b 100644 --- a/docs/src/reference/docbook/mail.xml +++ b/docs/src/reference/docbook/mail.xml @@ -9,7 +9,7 @@ Spring Integration provides support for outbound email with the MailSendingMessageHandler. It delegates to a configured instance of Spring's JavaMailSender: - JavaMailSender mailSender = (JavaMailSender) context.getBean("mailSender"); + JavaMailSender mailSender = context.getBean("mailSender", JavaMailSender.class); MailSendingMessageHandler mailSendingHandler = new MailSendingMessageHandler(mailSender); MailSendingMessageHandler has various mapping strategies that use Spring's diff --git a/docs/src/reference/docbook/samples.xml b/docs/src/reference/docbook/samples.xml index 9ab5f6e2b6..2261d2e5f5 100644 --- a/docs/src/reference/docbook/samples.xml +++ b/docs/src/reference/docbook/samples.xml @@ -564,7 +564,7 @@ That includes Samples, so if you can't find what you are looking for let us know else { context = new ClassPathXmlApplicationContext("cafeDemo.xml", CafeDemo.class); } - Cafe cafe = (Cafe) context.getBean("cafe"); + Cafe cafe = context.getBean("cafe", Cafe.class); for (int i = 1; i <= 100; i++) { Order order = new Order(i); order.addItem(DrinkType.LATTE, 2, false);