doc: dont consider bean-introspection experimental #10463
Merged
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.
Today, I was doing a supporting company that wanted to upgrade to Micronaut Framework 4. They disabled
bean-introspection-module
in Micronaut Framework 3. When upgrading to 4 while keeping bean-introspection-module disabled, they hit an issue in security.I told them we encourage people to move to Micronaut Serialization or at least to Micronaut Jackson Databind with bean-introspection-module enabled and annotate any serializable POJO with
@Introspected
.They pointed to the fact that our documentation still considers
bean-introspection-module
as experimental, making them hesitate to enable it.The
bean-introspection-module
has been around for a while, and I think we should consider it no longer experimental. Thoughts?