Core - release notes


1.0 Known problems and limitation
    1.1 Invalid characters in WebSphereR Studio installation directory prevent it from starting
    1.2 Problems with class loaders in created threads
    1.3 Deadlock creating executable extension in Plugin.startup

1.0 Known problems and limitations

1.1 Invalid characters in WebSphere Studio installation directory prevents it from starting

WebSphere Studio will fail to launch if installed in a directory which contains certain invalid characters, such as :%#<>"!. To work around this, install WebSphere Studio in a directory that does not contain invalid characters.

1.2 Problems with classloaders in created threads

There is a known issue with trying to load classes from a newly created thread using a class loader different from the plug-in class loader. The result will be a ClassNotFoundException. As a workaround, perform the following steps:

  1. Create a thread in which to run your code.
  2. Send
    yourThread.setContextClassLoader(yourClassLoader); 
     (YourPluginClass.class.getClassLoader())

    You can find your class loader by grabbing a class it loaded.
  3. Run your code in the newly created thread.

If you set the context class loader for the current thread, you are competing with other users of the thread (all of WebSphere Studio), so the results will be unpredictable./p>

1.3 Deadlock creating executable extension in Plugin.startup

If the Plugin.startup code is too complex and performs tasks such as creating an executable extension, a deadlock situation may be created. Only simple bookkeeping tasks should be performed with the Plugin.startup code.

Return to the main readme file

>