This change is not that easy to me.
Our application retreives acl, parameters, request, response, message,
locale, screentemplates ect all over the place.
This change would be too big and I'm having a hard time seeing the benefits.
/Ludwig
-----Ursprungligt meddelande-----
From: Thomas Vandahl
Sent: Thursday, November 10, 2011 11:13 PM
To: Turbine Developers List
Subject: [DISCUSS] Deprecate/Remove setter methods in TurbineRunData?
Hi folks,
as the RunData object is derived from PipelineData, the kosher way to
set values in it would be data.get(Turbine.class).put(whatever). So the
setter methods of TurbineRunData and their implementations are no longer
required. Anyone having a strong feeling against removing them?
In any case, the PipelineData do* methods need to be reconsidered IMO.
The access to important data is much more complicated than with RunData
and I see actually no real reason for a reduced interface.
WDYT?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
