Menu
▾
▴
#158 wrapper.conf does not support relative paths with ".."
In wrapper.conf, if you have any properties with paths that use ".." (parent dir), YAJSW converts that into ".." which is an invalid path. YAJSW therefore cannot support relative paths in configuration. Get IOException at WrappedService line 491. Traced to commons-configuration but can't tell if its the cause due to its overly complex design. Switched to commons-configuration2 2.4 but problem remains. Using YAJSW 12.10.
When wrapper.conf is loaded you can immediately see the paths are mangled.
SF converted what I typed in, ugh! \.\.
Forgot to mention that we are using embedded mode so we are calling WrappedService.init();
Disregard. It looks like the problem is caused by a fouled up java.class.path system property caused by our EXE generator, that has decided to simply stop working for no reason. The problem is not in YAJSW. But it would be nice to have better error handling here.