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
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.
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:
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>
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
(C) Copyright IBM Corporation 2000, 2003. All Rights Reserved.