Hi Michael,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="h5"></div></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div>> [skipped lengthy description of _this()'s behaviour that tracks activations and in case if there is only one activation -- it uses POA of that activation to produce a new reference]<br></div></div></blockquote>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="h5">><br>
> - I feel that this (probably helpful) behaviour is not standard-compliant --<br>
> can someone prove that it is not the case?<br>
</div></div>Afaik this is in fact standard compliant.<br>
<div class="im"></div></blockquote><div><br>Can't find anything in standard that might allow this, quite opposite -- standard clearly says that if object is not a target of 'Current' request -- _defaultPOA is called to get POA used to lookup a reference or activate (in case of implicit activation), no optionality.<br>
Can you give me a reference that suports your point of view?<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
> - I am trying to avoid necessity of overriding _defaultPOA (someone will<br>
> forget to do it and it will lead to hard-to-find problems). So there any way<br>
> to ensure that all objects get activated in specific POA without this?<br>
</div>You'll have to call activate on the correct poa explicitly (it shouldn't<br>
be hard to verify this, assuming you have a reasonable code structure).<br>
Maybe you should write a get_this helper template that makes sure<br>
everything is activated the way you want it?!?<br>
<div class="im"></div></blockquote><div><br>:-) Our product in constant state of development for last 10? years and will continue like that for foreseeable future (with developers coming and leaving). I am pretty much sure that sooner or later one of them will forget to use a helper or override that function. It is inevitable.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
> - maybe it is possible to 'disable' RootPOA somehow?<br>
</div>I don't think so + I don't think it would be any good (poas form a hierachy)</blockquote><div><br>Well, I see at last one good thing about disabling or killing RootPOA (assuming you can't change it's policies) -- it will remove necessity of overriding _defaultPOA() method in every servant if you want all your servants to belong to different POA :-)<br>
</div></div><br>-- <br>Sincerely yours,<br>Michael.<br>