Support Spring Integration Java DSL

[joshlong]

the Spring Boot Spring Integration starter oddly brings in adapters for stream and file (which, you don't need necessarily and may never use!) but doesn't bring in the Spring Integration Java DSL. This is very confusing.

At a minimum, please also bring in the Java DSL and - in the next major version perhaps - remove the crazy unnecessary Spring Integration Adapters. There are dozens of adapters in Spring Integration and no body knows which particular one they'll need but the can bring all of them by following the pattern org.springframework.integration : spring-integration-$SUPPORTED_TECH : spring-integration.version but the Java DSL doesn't share the same version as the rest of Spring Integration, so it would benefit from being in there and having its own property.

Also, the Spring Integration dependencies fro the Spring Integration project itself are already available unqualified thanks to the Spring Integration BOM. The Java DSL isn't.

[philwebb]

Adding the Java DSL seems like a nice addition but I'm not keen to remove the stream and file adapters since it will make the upgrade to 1.4 more difficult.

We actually chose what we considered to be as sensible subset of technologies to include, namely:

• spring-integration-core
• spring-integration-file
• spring-integration-http
• spring-integration-ip
• spring-integration-stream

Other than the size of the JAR, does including them actually cause any problems?

[joshlong]

id be happy with just including the DSL but i always exclude those dependencies as soon as I import the spring integration starter.

• core makes sense
• file? what about ftp or sftp or ftps?
• http? use Spring MVC and just write to a channel, it's almost always easier
• ip ? :/ hopefully most people are using prewritten protocols (like spring-integration-mqtt or XMPP). instead of rolling their own protocols. If they need to do that I'd imagine they're in the minority.
• reading and writing from stdin/stdout are not the reasons i reach for an enterprise integration technology.

and anyway, it's the symmetry of it all. Libraries that aren't auto-configured just sitting on the CLASSPATH for no particular reason. Even Spring Social has various starters for various optional implementations.

these seem completely arbitrary and mean i have to add an exclude. Some people won't even know they can add an exclude as our messaging has always been that a starter is the opinionated way to get started with a given technology, the minimum for the best experience. obviously i don't care about .jar size. they're just.. confusing.

i'd be happy with just adding the DSL tho and hope we could add the DSL before 1.4. Removing these others might need to wait till 1.4..

[philwebb]

Why do you always exclude them? What problems do they cause?

[snicoll]

ping @joshlong

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.