We can file an issue about this but wanted to ask also to give more details
and get some ideas from the team.
In netbeans 6 there is a new project type called java desktop application
that lets user create a swing app that interfaces with a database using
toplink or other providers.
We've seen that as in issuezilla 119567, that
when multibyte is used in a path to this project,
and when current, v2 build 58g toplink is used,
there are errors from toplink and the application
does not run. (if mbyte not used, there is no problem)
http://www.netbeans.org/issues/show_bug.cgi?id=119567
But its ok with toplink from v2 build 36
(we only recently upgraded the toplink jars we use in
nb from 36 to 58g)
There are no problems using another nb sample,
jsf jpa crud, using the latest toplink jars. its true the approach
of that sample is different than that of the project that has the problem
in some ways; developer mentioned below can tell more about that also.
NB developers could give more info on the approach
taken by the project type where we see the toplink
problems, in case it might be that there is some
api change and they need to use it vs actual
problem in toplink.
jan.stola_at_sun.com is the developer at nb who works on that project type.
erno.mononen also knows a lot about use of toplink in nb.
NOTE that the problem happened in both of these cases -
where user was in ja locale for example, and installed nb/gf and later ran
nb in ja locale
where user was in en locale for installing nb/gf and later ran nb in ja
locale.
http://www.netbeans.org/issues/show_bug.cgi?id=119567
tells more information on the error msgs seen.
Thanks - Ken