> On Jul 7, 2016, at 4:37 PM, Alan Bateman <alan.bate...@oracle.com> wrote: > > On 07/07/2016 09:27, Wang Weijun wrote: > >> Like this? >> >> https://gist.github.com/wangweij/6992aaf9617b9e2f242ddf9e391ea5f6 >> >> The horizontal line is printed on line 706 of the gist. >> > I assume the suggestion was to reference SQLPermission before setting the > security manager. As regards module loading then we can re-wording this > specific case but fundamentally then anything in the checkPermission > implementation that triggers a permission check is going to lead to a > recursive call to checkPermission.
If I add a "new SQLPermission("setLog");" at the beginning, then there will be no exception thrown. The stack trace does show the issue arise from resolving SQLPermission. Peter says "all necessary classes are loaded", and I thought it's about the access control things. --Max > > -Alan