Create Instance throws exception when Java Project located on network drive
If the java project that is using ABCL is located on a network drive, Method Create isntance throws this exception: Exception in thread "AWT-EventQueue-0" java.lang.ClassCastException: org.armedbear.lisp.Nil cannot be cast to org.armedbear.lisp.Pathname at org.armedbear.lisp.Load.loadSystemFile(Load.java:329) at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) at org.armedbear.lisp.Interpreter.createInstance(Interpreter.java:72) ....... I believe this has something to do with the the path. (path \\fs2\14233205\NetBeansProjects\HamdaBinteAjmal-interface- 1ed1d2022f90 ) Please note that both the abcl.jar and the java project are located on a network drive. Anyway to resolve this? Regards, Hamda
On 02 Jul 2015, at 15:09, Hamda binte Ajmal <Hamda.binte.ajmal@gmail.com> wrote:
If the java project that is using ABCL is located on a network drive, Method Create isntance throws this exception:
Exception in thread "AWT-EventQueue-0" java.lang.ClassCastException: org.armedbear.lisp.Nil cannot be cast to org.armedbear.lisp.Pathname at org.armedbear.lisp.Load.loadSystemFile(Load.java:329) at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) at org.armedbear.lisp.Interpreter.createInstance(Interpreter.java:72) .......
I believe this has something to do with the the path. (path \\fs2\14233205\NetBeansProjects\HamdaBinteAjmal-interface- 1ed1d2022f90 ) Please note that both the abcl.jar and the java project are located on a network drive.
Anyway to resolve this?
UNC pathnames under Windows should work: we use them daily in production. What are the values for LISP-IMPLEMENTATION-VERSION for you? Could you please refactor this to a reproducible test case outside of your code? Try to see if something like (pathname “//fs2/14233205/path/to/some/file”) fails and report the full stack trace (at least to the point that it resolves back into Lisp calls).
participants (2)
-
Hamda binte Ajmal -
Mark Evenson