Martijn Faassen wrote:
Jim Fulton wrote:
Christian Theune wrote:
[snip]
Is this intentional?
Yes. self is never proxied.
I'll just note as a data-point that this surprised me as well. I noticed
that some things in Zope 3 weren't giving me authorization errors as I
expected, even th
Jim Fulton wrote:
Christian Theune wrote:
[snip]
Is this intentional?
Yes. self is never proxied.
I'll just note as a data-point that this surprised me as well. I noticed
that some things in Zope 3 weren't giving me authorization errors as I
expected, even though as I was swamped in them
Christian Theune wrote:
Am Donnerstag, den 12.01.2006, 12:52 -0500 schrieb Jim Fulton:
Is this intentional?
Yes. self is never proxied.
Ok. Just for my understanding: This results in a behaviour similar to
Java where you can access everything within your own class, regardless
of private/p
Am Donnerstag, den 12.01.2006, 12:52 -0500 schrieb Jim Fulton:
> > Is this intentional?
>
> Yes. self is never proxied.
Ok. Just for my understanding: This results in a behaviour similar to
Java where you can access everything within your own class, regardless
of private/public declarations. (I
Christian Theune wrote:
Hi,
we are wondering about the behaviour in the following situation:
* self is a view and we're in a method of that view
* self.context is an instance of class A
(A is a content class and a folder)
* self.context is security proxied
* class A has a method doStuff
