Different handling in PathEditor in Servlet Context for existing and non-existing paths [SPR-15256] #19821
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: superseded
An issue that has been superseded by another
Holger Stenzhorn opened SPR-15256 and commented
Following the advice from from Juergen Hoeller in #19117, I have the code below "living" in a class of a webapp:
It is important to note that the directory
x
actually exists buty
does not exist.Now I have the following test method:
This method returns:
So for existing paths there is no difference as can be seen from the output for
a
andc
.But for non-existing paths there is a difference as the output for
b
andd
shows.I can see that the documentation for
PathEditor
says this:So it seems to me that the above difference might be intentional...
(Note: My specific use case is that I want to specify with the above "method" a path where Lucene creates its index and that directory does not necessarily have to exist beforehand.)
Affects: 4.3.6
Issue Links:
The text was updated successfully, but these errors were encountered: