Comments on: Spring Integration Samples http://blog.springsource.com/main/2007/12/21/spring-integration-samples/ The voice of SpringSource Thu, 21 Aug 2008 19:11:04 +0000 http://wordpress.org/?v=2.0.11 by: SpringSource Team Blog » Implementing Enterprise Integration Patterns part 0 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-106599 Mon, 19 May 2008 19:24:55 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-106599 [...] Open up HelloWorldDemo and run as Java application. If you've done this before you'll see the changes in syntax. [...] […] Open up HelloWorldDemo and run as Java application. If you've done this before you'll see the changes in syntax. […]

]]> by: Danny Robinson http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-103167 Mon, 14 Apr 2008 20:16:39 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-103167 Great stuff. Would you be able to also post the SI slides you presented at the NEJUG? Great stuff. Would you be able to also post the SI slides you presented at the NEJUG?

]]> by: AndrewB http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-101078 Thu, 20 Mar 2008 13:00:21 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-101078 Mark, How would I get a Cobol application connected to Spring Integration? Mark,
How would I get a Cobol application connected to Spring Integration?

]]> by: Stephan Strittmatter http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-99900 Tue, 04 Mar 2008 12:42:43 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-99900 For industrial solutions we have designed also an EAI-solution like spring-integration. We support there communication for example with PLSs (http://en.wikipedia.org/wiki/Programmable_logic_controller) and special industrial displays on production lines on one site and SAP for sales information on the other hand. For more details see http://www.sybit.de/en/solutions/industrial-solutions/industrial-solutions-solutions.html or contact us: info@sybit.de. For industrial solutions we have designed also an EAI-solution like spring-integration.
We support there communication for example with PLSs (http://en.wikipedia.org/wiki/Programmable_logic_controller) and special industrial displays on production lines on one site and SAP for sales information on the other hand.
For more details see http://www.sybit.de/en/solutions/industrial-solutions/industrial-solutions-solutions.html or contact us: info@sybit.de.

]]> by: Ryan Daum http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-97560 Fri, 08 Feb 2008 14:56:01 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-97560 Sorry to drag this on, and this may not be the right forum for this, but I've noticed that other Lifecycle beans do not get start() events either, presumably because the application context has not been started. Would it be safe to write my own context loading listener, and have it invoke the start() method on the application context, and would that in turn start the MessageBus? Autostart on the bus sounds great, but I'm really wondering in general about Spring's application context start() and the general lack of documentation (that I can see) on it... Sorry to drag this on, and this may not be the right forum for this, but I've noticed that other Lifecycle beans do not get start() events either, presumably because the application context has not been started. Would it be safe to write my own context loading listener, and have it invoke the start() method on the application context, and would that in turn start the MessageBus?

Autostart on the bus sounds great, but I'm really wondering in general about Spring's application context start() and the general lack of documentation (that I can see) on it…

]]> by: Mark Fisher http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-97500 Fri, 08 Feb 2008 03:06:18 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-97500 [quote comment="97472"]wondering if the Lifecycle.start method even gets called on my ApplicationContext.[/quote] Indeed, the start() method of an Application Context is not invoked automatically. Now, as far as Spring Integration is concerned, you only need to start the MessageBus - so if you get the MessageBus bean, you can invoke start() directly (you can look it up with the constant: MessageBusParser.MESSAGE_BUS_BEAN_NAME). Perhaps we should include an auto-start option on the bus itself (I'll add that in Jira now). Another options it to expose the bus' lifecycle methods as JMX managed operations. -Mark On February 7, 2008 at 6:46 pm, Ryan Daum said:

wondering if the Lifecycle.start method even gets called on my ApplicationContext.

Indeed, the start() method of an Application Context is not invoked automatically. Now, as far as Spring Integration is concerned, you only need to start the MessageBus - so if you get the MessageBus bean, you can invoke start() directly (you can look it up with the constant: MessageBusParser.MESSAGE_BUS_BEAN_NAME). Perhaps we should include an auto-start option on the bus itself (I'll add that in Jira now). Another options it to expose the bus' lifecycle methods as JMX managed operations.

-Mark

]]> by: Ryan Daum http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-97472 Thu, 07 Feb 2008 23:46:22 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-97472 While I can run the examples from the Subversion repository fine, when I attempt to create my own usages of message endpoints I have noticed that the PollingSourceAdapter.start method never gets called (though its constructor and setPeriod methods do). I am loading my application context using the ContextLoaderListener via the web.xml, and am wondering if the Lifecycle.start method even gets called on my ApplicationContext. My code looks almost identical to the (annotated) Quote example. I have no idea what I'm doing wrong here, but has anybody successfully made Spring Integration work from an application inside a servlet container? While I can run the examples from the Subversion repository fine, when I attempt to create my own usages of message endpoints I have noticed that the PollingSourceAdapter.start method never gets called (though its constructor and setPeriod methods do). I am loading my application context using the ContextLoaderListener via the web.xml, and am wondering if the Lifecycle.start method even gets called on my ApplicationContext.

My code looks almost identical to the (annotated) Quote example.

I have no idea what I'm doing wrong here, but has anybody successfully made Spring Integration work from an application inside a servlet container?

]]> by: Ben Hale http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-89368 Thu, 17 Jan 2008 16:20:13 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-89368 [quote comment="88389"]Hi, why do you use Ivy for dependency-management? Do you plan to migrate to maven for spring-integration in near future or will Ivy be the build-tool for new subprojects? Thanks Jörg[/quote] We use Ivy because after evaluating the options, Ivy's dependency management is, for our needs, more powerful and better suited to our projects. We have no plans to migrate to Maven at any point for our projects that are not already on it. We do however plan to produce POMs and other artifacts for Maven users in both release and snapshot form. -Ben On January 15, 2008 at 2:28 pm, Jörg said:

Hi,

why do you use Ivy for dependency-management? Do you plan to migrate to maven for spring-integration in near future or will Ivy be the build-tool for new subprojects?

Thanks

Jörg

We use Ivy because after evaluating the options, Ivy's dependency management is, for our needs, more powerful and better suited to our projects. We have no plans to migrate to Maven at any point for our projects that are not already on it. We do however plan to produce POMs and other artifacts for Maven users in both release and snapshot form.

-Ben

]]> by: Jörg http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-88389 Tue, 15 Jan 2008 19:28:52 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-88389 Hi, why do you use Ivy for dependency-management? Do you plan to migrate to maven for spring-integration in near future or will Ivy be the build-tool for new subprojects? Thanks Jörg Hi,

why do you use Ivy for dependency-management? Do you plan to migrate to maven for spring-integration in near future or will Ivy be the build-tool for new subprojects?

Thanks

Jörg

]]> by: Mark Fisher http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-86570 Wed, 09 Jan 2008 16:23:20 +0000 http://blog.springsource.com/main/2007/12/21/spring-integration-samples/#comment-86570 Steven, It definitely should be possible for handler methods to accept the Message (or any subclass) as the parameter. While Message return values were already supported (not using the mapper in that case), the same was not yet supported for parameters - so thank you for pointing this out! I have just added a property 'shouldUseMapperOnInvocation' to the DefaultMessageHandlerAdapter. The default value is 'true', but now the DefaultMessageHandlerCreator will set the value to 'false' whenever the target method does expect an actual Message object. If you are interested in the details, then do an svn update, then have a look at the following tests: DefaultMessageHandlerAdapterTests, DefaultMessageHandlerCreatorTests, and MessageEndpointAnnotationPostProcessorTests (specifically with MessageParameterAnnotatedEndpoint). Thanks again, Mark Steven,

It definitely should be possible for handler methods to accept the Message (or any subclass) as the parameter. While Message return values were already supported (not using the mapper in that case), the same was not yet supported for parameters - so thank you for pointing this out! I have just added a property 'shouldUseMapperOnInvocation' to the DefaultMessageHandlerAdapter. The default value is 'true', but now the DefaultMessageHandlerCreator will set the value to 'false' whenever the target method does expect an actual Message object. If you are interested in the details, then do an svn update, then have a look at the following tests:
DefaultMessageHandlerAdapterTests, DefaultMessageHandlerCreatorTests, and MessageEndpointAnnotationPostProcessorTests (specifically with MessageParameterAnnotatedEndpoint).

Thanks again,
Mark

]]>