1. OSGi and Messaging Building large applications that don't break down Iwein Fuld - SpringSource Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
28. Some other really nice things that I don't need to tell you about Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
32. Map reduce Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
33. What is Messaging? Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited. How can multiple agents work together?... ...without being in each others way. Waiter helps customer and cook to collaborate.
34. Characteristics of Messaging Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited. Transport The waiter takes an order and moves it to the barista Asynchronous Different actors can do different things in parallel Translation menu item => number => recipe Routing Orders arrive back at the proper table
35. Spring Integration Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
36. Pipes and Filters Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited. Sender Application Receiver Application Channel MessageEndpoint
37. Hello world Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited. <service-activator input-channel = "inputChannel" default-output-channel = "outputChannel" ref = "helloService" method = "sayHello" /> < beans:bean id = "helloService" class = "...HelloService" /> public class HelloService { public String sayHello(String name) { return "Hello " + name; } }
38. Channels Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited. < channel id = "incoming" /> < channel id = "orderedNotifications" > <queue capacity = "10"/ > </channel>
39.
40.
41.
42. Not an ESB Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
43.
44.
45.
46. Focus on the deployment architecture not the actual integration. Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
47. Basic Integration Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
48. With a bus Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
49. Demo Time Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
50.
51.
52.
53. STS, dm Server Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
54. Questions and Plugs Ask now... or visit our booth... or google “Iwein Fuld” Copyright 2008 SpringSource. Copying, publishing or distributing without express written permission is prohibited.
Notas del editor
Next up: Introduction to Spring integration which covers: - How and why Spring Integration came into existence
Next up: Introduction to Spring integration which covers: - How and why Spring Integration came into existence
Next up: Introduction to Spring integration which covers: - How and why Spring Integration came into existence
Next up: Introduction to Spring integration which covers: - How and why Spring Integration came into existence
Next up: Introduction to Spring integration which covers: - How and why Spring Integration came into existence
Spring Integration was created by Mark Fisher of SpringSource. - It is an implementation of the patterns described in Enterprise Integration Patterns by Hohpe and Woolf. - The book itself doesn’t give concrete usable components, Spring Integration does this: non invasive declarative
Endpoints connect application code to the integration framework.
There is quite some code in the slide. Go over it slowly and promise another look during the demo. TODO enlarge code samples -> two slides
Channels are buffers that hold messages, responsible for transporting the messages from sender to receiver(s) Mention equivalence with JMS Queues
Download the SI distribution or check out the project from svn, import the sample projects into STS. Show at least the CafeDemo xml variant. If there is time you can show some of the following: - Tweaking for performance (add a thread-pool-task-executor to the poller, play with the trigger) - Other demos - add a JMX based detour (router with @ManagedAttribute outputChannel) to the deliveredOrders
![Topics in this session ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)