Task #10659 (closed)
Opened 11 years ago
Closed 11 years ago
Loosen prefix restrictions in FS
Reported by: | jamoore | Owned by: | mtbcarroll |
---|---|---|---|
Priority: | major | Milestone: | 5.0.0-beta1 |
Component: | General | Version: | n.a. |
Keywords: | fs | Cc: | fs@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
Raised by Andreas, since creating a file with a period was disallowed:
ValidationException: exception ::omero::ValidationException { serverStackTrace = serverExceptionClass = message = Path contains illegal components }
Change History (4)
comment:1 Changed 11 years ago by mtbcarroll
- Status changed from new to accepted
comment:2 Changed 11 years ago by jamoore
Mark: would getFsFileFromClientFile silently change that value or throw an exception?
comment:3 Changed 11 years ago by mtbcarroll
It would provide an adjusted string that should validate okay, probably it would prefix it with an underscore or something: the idea is that the client supplies a locally constructed File instance that may be awkwardly named and gets back an FsFile instance that validates okay (because it directly corresponds to something the server file system should support). (The toString() of that instance can be supplied for importing or whatever.)
I do agree with removing the "." prefix restriction, though.
comment:4 Changed 11 years ago by mtbcarroll
- Resolution set to fixed
- Status changed from accepted to closed
Will remove "." prefix restriction but in the usual case clients should use ClientFilePathTransformer.getFsFileFromClientFile to prevent such validation errors.