Hi, I am not really sure I understand your posting correctly. Are you saying that your impression is that java.awt.FileDialog in mode FileDialog.LOAD does not work properly in an app bundle, regardless of sandboxing? If that is so, then I can confirm that this is not the case.
You are not by any chance starting the app with a splash screen with -splash? If so that is likely to be the reason for your problems as java.awt.FileDialog is completely broken then (see https://bugs.openjdk.java.net/browse/JDK-8009203, https://bugs.openjdk.java.net/browse/JDK-8006420). If I understand the feedback of an Oracle dev a few days ago on this list correctly, this is fixed in J9 and will be backported for the next J8 update. We even implemented our own splash screen because of this. Cheers, Robert On Wed, May 28, 2014 at 8:32 PM, Hendrik Schreiber <h...@tagtraum.com> wrote: > On May 23, 2014, at 19:26, Hendrik Schreiber <h...@tagtraum.com> wrote: >> I'm under the impression that the java.awt.FileDialog in mode >> FileDialog.LOAD does not work properly when invoked from an app bundle. >> As in: It always assumes a sandbox and does not give me access to all files >> anymore. >> It does not matter, if the bundle was signed or not. >> The bundle was created with https://bitbucket.org/infinitekind/appbundler >> Note that AppBundler passes in a system property -DSandboxEnabled=true, if >> it finds *any* Containers folder. Meaning, it's only an indication for >> whether sandboxing is possible at all, *not* whether this particular app is >> sandboxed. >> >> There is no problem, when launching the same app via the regular java >> launcher. >> >> Does anybody else have this problem? > > Really, no one else is having problems with this? > > -hendrik -- Robert Krüger Managing Partner Lesspain GmbH & Co. KG www.lesspain-software.com
