Files
spring-integration-samples/intermediate/stored-procedures-derby
Artem Bilan 5f524dc534 Upgrade to SI-5.0 & SIK-3.0, Reactor 3.0
* Fix compatibility after Java DSL migration to the SI Core
* Also upgrade all the JMS sample to the JMS 2.0
* Fix default `connectionFactory` bean reference to the current `jmsConnectionFactory`
* Remove unsupported JPA-1.0 Spec via `OpenJpaAutoConfiguration`, since the minimum now is JPA-2.0
* Remove non-lambda sample since minimum now is Java 8
* Rename `PromiseTest` to `MonoTest` and fix it to Reactor 3.0
* Fix `stomp-server.xml` to use proper Reactor 3.0 `eactor.util.function.Tuples` for SpEL
* Regenerate POMs
2016-11-18 14:11:32 -05:00
..

Spring Integration - Stored Procedure Example - Derby

Overview

This example provides a simple example using the stored procedure Outbound Gateway adapter. This example will call 2 Derby Stored Procedures.

One procedure uses an Out Parameter to return values and the second procedure returns a ResultSet.

Setup

Just make sure you have Gradle set up and that the project builds successfully.

Run the Sample

  • running the "Main" class from within STS (Right-click on Main class --> Run As --> Java Application)

  • or from the command line:

    $ gradlew :stored-procedures-derby:run

  • Follow the screen (command line) instructions.


For help please take a look at the Spring Integration documentation:

http://www.springsource.org/spring-integration