7 Mar
2012
7 Mar
'12
5:49 p.m.
On Wed, Mar 7, 2012 at 3:47 AM, Jürgen Herrmann <Juergen.Herrmann@xlhost.de> wrote:
now i had a use case where i need to mark some templates and methods as public because they use an internal authentication.
One of the challenges I see is that InitializeClass() removes the original 'security' attribute of the class, so you end up having to copy the security info to a module global before calling InitializeClass() the first time. Then, if you have that copy of the class security information, you should be able to re-use it, modify it, re-apply it to the class, then call InitializeClass (again). Sean