Skip to content

DATAJDBC-258 - Enable Integration tests for MS-SQL-Server. #98

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

THD-Thomas-Lang
Copy link
Contributor

Pull request for issue DATAJDBC-258.

@pivotal-issuemaster
Copy link

@THD-Thomas-Lang Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-issuemaster
Copy link

@THD-Thomas-Lang Thank you for signing the Contributor License Agreement!

@schauder schauder changed the title Datajdbc 258 DATAJDBC-258 - Enable Integration tests for MS-SQL-Server. Oct 30, 2018
schauder pushed a commit that referenced this pull request Nov 1, 2018
This adds MS-SQL-Server via Testcontainers to the set of databases available for integration testing.
For this purpose it accepts the EULA of MS SQL Server.

Failing tests are ignored to be fixed in separate issues.

Original pull request: #98.
schauder added a commit that referenced this pull request Nov 1, 2018
Simplified id value retrieval.
Simplified ignoring tests for a specific database.
Fixed property name in pom.xml.

Original pull request: #98.
schauder added a commit that referenced this pull request Nov 1, 2018
Added mssql to the readme as available database for tests.

Original pull request: #98.
@schauder
Copy link
Contributor

schauder commented Nov 1, 2018

That's squashed, polished and merged into master.

Thank you very much @THD-Thomas-Lang.

@schauder schauder closed this Nov 1, 2018
mp911de added a commit that referenced this pull request Feb 21, 2022
We now provide an abstract base class for ConnectionFactory routing. Routing keys are typically obtained from a subscriber context. AbstractRoutingConnectionFactory is backed by either a map of string identifiers or connection factories. When using string identifiers, these can map agains e.g. Spring bean names that can be resolved using BeanFactoryConnectionFactoryLookup.

class MyRoutingConnectionFactory extends AbstractRoutingConnectionFactory {

		@OverRide
		protected Mono<Object> determineCurrentLookupKey() {
			return Mono.subscriberContext().filter(it -> it.hasKey(ROUTING_KEY)).map(it -> it.get(ROUTING_KEY));
		}
}

@bean
public void routingConnectionFactory() {

		MyRoutingConnectionFactory router = new MyRoutingConnectionFactory();

		Map<String, ConnectionFactory> factories = new HashMap<>();
		ConnectionFactory myDefault = …;
		ConnectionFactory primary = …;
		ConnectionFactory secondary = …;

		factories.put("primary", primary);
		factories.put("secondary", secondary);

		router.setTargetConnectionFactories(factories);
		router.setDefaultTargetConnectionFactory(myDefault);

		return router;
}

Original pull request: #132.
mp911de pushed a commit that referenced this pull request Feb 21, 2022
Formatting.
Changed generics to avoid unchecked casting.
Avoided abbreviated variable name.
Simplified handling of absent keys at ConnectionFactory lookup.

Original pull request: #132.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants