We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Moving to javaconfig will make our configuration more robust and will improve its testability.
But will we able to keep extensibility and overriding capabilities that Resthub has today ?
Will users have to move also to javaconfig or could they stay on xml based configuration relying on our javaconfig ?
Must check these points.
The text was updated successfully, but these errors were encountered:
FWIW,i find xml config more convenient. More than anything else, i wouldn't want to be forced into refactoring it to java config!
Sorry, something went wrong.
No branches or pull requests
Moving to javaconfig will make our configuration more robust and will improve its testability.
But will we able to keep extensibility and overriding capabilities that Resthub has today ?
Will users have to move also to javaconfig or could they stay on xml based configuration relying on our javaconfig ?
Must check these points.
The text was updated successfully, but these errors were encountered: