Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Conditional resource type
Fixed
Description fields
Basics
Technical
Logistics
Basics
Technical
Logistics
Description
Not sure this is a fully formed thought but wanted to capture it.
One of the things we sometimes have to do is tell people to add stuff to services.xml to load additional Spring files into services. Normally that's not something we can do for them unless we provide empty placeholder files, which clutters the config.
I thought maybe it might make sense to have a wrapper type that allows a Resource to be defined but if the input stream fails (e.g. file isn't there) maybe it could auto-return an "empty" beans resource.
There's probably a lot wrong with this, like masking errors. Just a thought.
Not sure this is a fully formed thought but wanted to capture it.
One of the things we sometimes have to do is tell people to add stuff to services.xml to load additional Spring files into services. Normally that's not something we can do for them unless we provide empty placeholder files, which clutters the config.
I thought maybe it might make sense to have a wrapper type that allows a Resource to be defined but if the input stream fails (e.g. file isn't there) maybe it could auto-return an "empty" beans resource.
There's probably a lot wrong with this, like masking errors. Just a thought.