Add Java configuration and fix gateway mapping #369
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduce Java-based configuration as an alternative to the existing XML configuration for the barrier sample application. Provide developers with a modern, type-safe approach to configuring the barrier pattern while maintaining backward compatibility. Java-based configuration will be the default. Allow user to specify either `java-config` or `xml-config` profile to determine how app is configured. Add three new `@Configuration` classes activated via profiles: - ClientConfiguration: Configure HTTP outbound gateway - ServerConfiguration: Implement complete barrier pattern flow - ErrorHandlingConfiguration: Handle error scenarios Fix barrier2 gateway parameter mapping by adding Spring Integration as the current XML configuration does not work. Add comprehensive Javadoc documentation in imperative voice for all configuration classes, explaining the barrier pattern implementation, message flows, and component interactions. Update README.md to document profile-based configuration selection (xml-config vs java-config) and provide commands for running error handling examples. Remove unused namespaces from XML files
cppwfs
force-pushed
the
SIS-barrier-java-config
branch
from
d76aa72 to
071d683
Compare
Introduce Java-based Spring Integration configuration as an alternative to the existing XML configuration. The new ControlBusConfiguration class uses `@Configuration` and Integration DSL to define the control bus flow and inbound adapter. The application.properties file sets `java-config` as the default profile, allowing users to run the sample with Java configuration out of the box. The XML configuration remains available by explicitly activating the `xml-config` profile.
Introduce Java-based Spring Integration configuration as an alternative to the existing XML configuration. The new EnricherConfiguration class uses `@Configuration` and Integration DSL to define three enricher flows demonstrating different enrichment strategies. The UserGateway interface uses `@MessagingGateway` to provide a simple interface for clients to invoke enricher flows. The application.properties file sets `java-config` as the default profile, allowing users to run the sample with Java configuration out of the box. The Main class now supports profile-based configuration switching to load either Java or XML configuration. Tests have been updated to verify both configuration modes work correctly, with helper methods extracted to reduce code duplication. The XML configuration remains available by explicitly activating the `xml-config` profile, maintaining backward compatibility. All samples can now run using gradlew :enricher:run. Was broken before
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce Java-based configuration as an alternative to the existing XML configuration for the barrier sample application. Provide developers with a modern, type-safe approach to configuring the barrier pattern while maintaining backward compatibility. Java-based configuration will be the default.
Allow user to specify either
java-configorxml-configprofile to determine how app is configured.Add three new
@Configurationclasses activated via profiles:Fix barrier2 gateway parameter mapping by adding Spring Integration as the current XML configuration does not work.
Add comprehensive Javadoc documentation in imperative voice for all configuration classes, explaining the barrier pattern implementation, message flows, and component interactions.
Update README.md to document profile-based configuration selection (xml-config vs java-config) and provide commands for running error handling examples.
Remove unused namespaces from XML files