WritableResource doesn't have parity with Resource in @Value etc. [SPR-10656]

[spring-projects-issues]

Dave Syer opened SPR-10656 and commented

Users can (and often do) inject Resource instances using placeholders and pattern matching, but this doesn't work with WritableResource. It might be an oversight?

---

Affects: 4.0 M1

1 votes, 4 watchers

[spring-projects-issues]

Phil Webb commented

Can you provide a small snippet of code to demonstrate what you mean?

[spring-projects-issues]

Dave Syer commented

This would fail to bind to the environment property:

@Component
public class MyWritingStuff {

@Value("${writing.file:file:/tmp/foo.txt}")
private WritableResource writable;

}

whereas this would succeed:

@Component
public class MyReadingStuff {

@Value("${writing.file:file:/tmp/foo.txt}")
private Resource writable;

}

[spring-projects-issues]

Phil Webb commented

I think I have a fix for this but it changes the default behavior of DefaultResourceLoader. Juergen Hoeller, could you review and let me know how risky you think this is?

#301

[spring-projects-issues]

Artem Bilan commented

Some our projects have started to bump to this issue, too: spring-attic/spring-cloud-gcp#72

Wouldn't it be great to revise the fix?

Thanks

[spring-projects-issues]

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.

[fmbenhassine]

Please, reopen if still relevant.

This issue is still relevant with SF 6.0.0 snapshots. Can you please take a look? This is actually blocking for spring-projects/spring-batch#756.