Give spring-core
access to org.jboss.vfs
for VfsUtils
support on WildFly
#30973
+1
−1
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.
Give spring-core access to the org.jboss.vfs module to make VfsUtils work out of the box on WildFly 28+.
Starting from WildFly 28 deployments no longer have access by default to the
org.jboss.vfs
module. This causes the class initialization oforg.springframework.core.io.VfsUtils
to fail which causesConfigurationClassParser#parse
to fail (see stack tace below).As a workaround applications can create a jboss-deployment-structure.xml but a permanent fix is to add
org.jboss.vfs
to the existing Dependencies manifest header.This is very similar to #25852