See my other reply regarding fundamental modifiers of the Java Language. As for frameworks such as tapestry you are dealing with a Component and Object Model (COM).
In addition, tapestry uses plastic to induce synthetic methods such as getters and setters into your classes. See for example Objective C: @synthesize for an explanation on what is happening here. Of course this is only part of what is actually going on deep inside tapestry/plastic. Perhaps you might have a look at the concepts of aspect oriented programming (aop) and more generally at the concepts of both component and object models (COM) and meta component and object models (MOM). Corba seems to be a good start for me, XPCOM and NextStep or GnuStep are also good pointers. > Thanks guys, you have all answered my question. Being relatively new to > programming, I discovered this issue today while seeing data being shared > between sessions. "not something I planned". > > Thiago - I don't know what they're called then. My java book said they > were > modifiers. You build your getters and setters from their variables. What > is > the technical name? > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Sevice-State-Stateless-tp5716278p5716287.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
