You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pretty sure this is some configuration error on my part, but I can't figure it out. From the documentation it seems like I should be able to access a repository in an integration test, but maybe not? I'm using SDC 3.4.12.
I have an integration test that is Autowiring in a repository.
I'm pretty sure that requests through the delete endpoint work because I have setup the converters, but I don't understand why the converters don't seem to be working when I use the repository in the integration test.
And adding the converters to customConversions(). If I set a break point here I can see this method is getting called when I run the integration tests.
We revised the converter with #1384 earlier this year and backported the changes into 4.0.7. The 3.x development line doesn't contain these changes and that development line goes EOL by next month. Please upgrade to the latest Spring Data Cassandra version at your earliest convenience.
I'm pretty sure this is some configuration error on my part, but I can't figure it out. From the documentation it seems like I should be able to access a repository in an integration test, but maybe not? I'm using SDC 3.4.12.
I have an integration test that is Autowiring in a repository.
At the end of a test I want to do this to clean up:
This ends up throwing:
However, if I use mockMVC to call the endpoint that does a delete it works:
I'm pretty sure that requests through the delete endpoint work because I have setup the converters, but I don't understand why the converters don't seem to be working when I use the repository in the integration test.
The
@Table
:The converter: (I have one for SquareToken to String and String to SquareToken
And adding the converters to customConversions(). If I set a break point here I can see this method is getting called when I run the integration tests.
The text was updated successfully, but these errors were encountered: