Created attachment 18656 [details]
message log

Looks like some problem in j2me.

But Tomas please look at why J2SEPlatformModule.updateSourceLevel is
throwing an NPE after that; poor error recovery?

Yarda I think the "AbstractLookup$ISE: You are trying to modify lookup
from lookup query!" was something that was already fixed, right? Not
sure why it is appearing here.

Can you please attach the content of your
<userdir>/config/Services/Platforms/org-netbeans-api-java-Platform/
folder.
There is some J2ME platform .xml file that is causing this exception.

Re. ISE - it is still being thrown for internal purposes you do not
want to know. It is expected that when thrown, it will also be catched
by the AbstractLookup. However this may not always true, as there can
be code that catches everything and rethrows it:

try {
 // blabla
} catch (RuntimeException ex) {
  throw new IOException (...);
}

in such case the ex cannot be caught by the AbstractLookup and can
appear in logs. The only fix (in reasonable timeframe) I can think of
is to rewrite such code to allow runtime exceptions to propagate.

Created attachment 18675 [details]
j2me xml file

Ok, here's the J2ME platform .xml file. If I remove it, no exceptions.
Either way, the IDE does not find the j2me platform. Maybe the
non-English characters in my user name (käyttäjä) are causing this?
BTW, if I uninstall the mobility pack, this file is not removed and
neither is it replaced  if I reinstall it.

Thanks, this will help us a lot.

I am increasing the priority of this bug to P2 because any time the
user name contains any non-ASCII characters the path to pre-installed
WTK is wrongly encoded inside J2ME_Wireless_Toolkit_2_2_Beta.xml file.

Currently you can delete this file, start the IDE and install the
Wireless Toolkit manually for Java Platform Manager - that should
work. Or specify -userdir <some_folder> command line argument to
override default location in C:\Documents and Settings\käyttäjä\...
But you might have still problems with national characters in paths of
projects if using beta2 (there was another bug of wrong character
encoding fixed after).

fixed for 4.1 but requires approval for the fix integration into 4.0

verified in 4.0, will try in trunk later and then close as verified

since there is bug on wtk about use of non ascii in wtk,
ie 6193955, does this fix mean that user can
install me into a dir with non ascii or multibyte in the name ?

I seem to remember in general from older issues that 
nb did not allow this in general, but maybe that was
fixed.

ken.frank@sun.com

Ken, if i remember it this issue fix only that user can use non-ascii
characters in userdir name. There were a problem in mobility with such
userdir name, anyway the problem with wtk remains(run on app fails)
and has to be solved on wtk side.

Currently from wtk point of view you cannot:
- run midlet if path to jar contains non-ascii chars
- run midlet via OTA if path to wtk record store contains non-ascii chars
- midlet name cannot contain non-ascii chars
- jar name cannot contain non-ascii chars