This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Open
Conversation
RestTemplate consisted of methods of the following form (getFor..., postFor..., etc.)
def m(...)
and
def m(..., uriVariables: Any*)
This made it impossible to call methods without passing any uriVariables, since the compiler cannot determine which of the overloaded method is intended. In any case, there is no need for the non-varargs methods; users can just call the varargs version passing no arguments for the uriVariables parameter.
Added TransactionSupport trait that can be used to extend FunctionalConfiguration. enableTransactionManagement(...) function is equivalent to traditional <tx:annotation-driven ...>.
PropertiesResolver - to ease access to application properties when configuring Spring beans PropertiesAware - to ease access to application properties from the Spring beans
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi,
I have thought about creating some mechanism to simplify access to application properties inside classes extending
FunctionalConfiguration. Therefore I have createdPropertiesResolvertrait that introduces variable$which can be used to access them in two ways:$("my.property.name")or$.my.property.name. This does not define properties source in any way, but just creates simple mechanism of accessing them.Sample usage:
I have also created another trait
PropertiesAwarethat, when extended by any bean, gives it access to properties the same way:For those more used to referencing properties by String
$("app.version")is also available and of course good old@Value("${app.version}")works too.Let me know what do you think.