Well, I'll have to check this out again (I've had so many different versions of the editor lately that I don't know if this is still a problem) but I can assure you that I did have at least one version of the editor that pulled it in as a method scoped "this" - and when I let it stand that way, the tcf definitely no longer functioned. Again, this might just have been a problem with that particular version... And I've also been bouncing back and forth between the Witango server and the J2EE server, so cannot recall now on which I had the problem... I have just been explicitly setting the internal methods ever since to the scope of the instantiated object and that's worked well. But if it's overkill I'd like to drop back to something simpler.

On Feb 20, 2004, at 1:03 PM, John McGowan wrote:



Dale Graham wrote:

Actually, if you have instantiated a TCF as a "request" within the TAF and then call a method from the same TCF, it will break if called as "method$this" - needs to be called as "request$this".

I have tafs and tcfs that would disagree with this statement.



And if instantiated in any other scope, the called internal method needs to match scope of instantiation. At least that's been my empirical experience.


when using "this" as the object name, the scope should be irrelevent. the "this" keyword implies that you want to call the method of the exact same instance of the method that is currently running. Method makes the most sense to me, because your are currently executing a method, but Instance$this would probably make more sense.

However, what I've documented in my previous email is how the two versions differ, and the Witango one definitly has "pain in the butt" potential, because dragging a method to a called within a tcf method by default will not work unless you explicitly fill in the name as this.

This (no pun intended) is a step backwards.

/John


_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf



________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to