But not with Scheduler on Windows... https://issues.apache.org/jira/browse/ZEST-41
There are three ways this can be fixed; a. Do character replacements in the identity, per filesystem, to create valid files. Downside; One can't move the store to another OS and remain compatible. b. Do character replacement in the identity, same on all filesystem, to create portable filenames. Downside; Existing stores will break. c. Introduce a IdentityConstraint in the FileEntityStore, which must be applied to all entities in the application if one use this ES. Downside; Scheduler (others?) will required to be changed and introduces an incompatibility from previous version. Not sure which is most reasonable. On Tue, Jul 7, 2015 at 11:13 AM, Paul Merlin <[email protected]> wrote: > Niclas Hedhman a écrit : > > As for "test grade"; Personally I am getting fond of the FileES for > smaller > > apps (which I am doing now), since it simplifies the testing quite a bit, > > and is good enough for my performance requirements. > I've been using it in small production apps for years and it works great. > Simple and effective, really easy testing/debugging/"hacking". > Small is beautiful :) > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
