#3 Integrity check fails when path to folder contains spaces

closed-fixed
None
5
2005-02-12
2005-02-04
Marat Radchenko
No

OS: Windows XP Professional (rus)

JDK: Java(TM) 2 SDK, Standard Edition Version 1.4.2
(build 1.4.2_04-b5)

Error in toolbox-boot-failed.log:
java.lang.Exception: plug-ins integrity check failed
at org.jpf.demo.toolbox.Boot.main
(Boot.java:115)

How to reproduce: launch JPF demo application from
folder which name contains spaces.

When application is launched from folder without
spaces, everything works.

If you need more information, please contact me via
SourceForge messaging service.

Discussion

  • Logged In: YES
    user_id=1194314

    Actually here's the problem:

    2005-02-07 18:04:06,284 [main] ERROR
    org.java.plugin.impl.IntegrityChecker integrity check failed for
    registry org.java.plugin.impl.PluginRegistryImpl@116ab4e
    java.lang.IllegalArgumentException
    at java.net.URI.create(Unknown Source)
    at
    org.java.plugin.StandardPathResolver.isResourceExists
    (StandardPathResolver.java:124)
    at org.java.plugin.impl.IntegrityChecker.checkPlugin
    (IntegrityChecker.java:112)
    at org.java.plugin.impl.IntegrityChecker.doCheck
    (IntegrityChecker.java:70)
    at
    org.java.plugin.impl.PluginRegistryImpl.checkIntegrity
    (PluginRegistryImpl.java:374)
    at org.jpf.demo.toolbox.Boot.main(Boot.java:108)
    Caused by: java.net.URISyntaxException: Illegal character in
    path at index 18: file:/D:/Documents and Settings/User/jpf-
    demo-bin-0.3/plugins/org.jpf.demo.toolbox.pluginbrowser-
    0.0.2/icons/
    at java.net.URI$Parser.fail(Unknown Source)
    at java.net.URI$Parser.checkChars(Unknown Source)
    at java.net.URI$Parser.parseHierarchical(Unknown
    Source)
    at java.net.URI$Parser.parse(Unknown Source)
    at java.net.URI.<init>(Unknown Source)
    ... 6 more

    java.net.URI doesn't like spaces.

     
    • assigned_to: nobody --> ddimon
    • status: open --> closed-fixed
     
  • Logged In: YES
    user_id=783559

    The problem seems to be fixed in version 0.4