I understand encapsulation and the need for it, but isn't it very common for base classes to have protected variables which the derived classes can access freely without having accessor methods?
Is there any architectural reason in tapestry for disallowing this for property and injected variables? I get this error - ... contains fields that are not private. You should change these fields to private, and add accessor methods if needed. I have a wizard and there are some common properties and injected stuff ... but i want to freely access these variables by having them 'protected' instead of writing numerous getters and setters. -- View this message in context: http://tapestry.1045711.n5.nabble.com/why-does-tapestry-force-variables-to-be-private-tp4924925p4924925.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
