Thanks Rick
2011/7/11 Rick McGuire <object.r...@gmail.com>
> Setting the security manager on a method or routine sets the manager
> for the entire package. This is the way it worked before the concept
> of a package was exposed in 4.0, so it works a little awkwardly. Had
> the package concept been there from the beginning, that would have
> been the only method exposed for doing this.
>
> That's clear.
But I still don't understand how a security manager is selected during
program execution...
Using my profiler, I see cross-package calls of methods, which is good.
But the profiler (a security manager which defines the METHOD checkpoint) is
assigned to one package only (pipe.rex) :
pipe_test.rex requires pipe_extension.cls
pipe_extensions.cls requires pipe.rex
pipe.rex (has security manager)
so, if the scope was limited to the package pipe.rex, only the messages sent
to methods defined in pipe.rex should be intercepted, but this is not the
case...
Jean-Louis
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
