Jack Woehr wrote:
Jose Alberto Fernandez wrote:
One of the problems here is that it is not always possible
to reconstruct the XML for a particular TASK. That is,
tasks MUST have setXXX methods for every attribute, but there is
no requirement that they provide a corresponding getXXX.
Simillar for createXXXX, addXXXX, etc.
Hence there is no way to given objects created programatically
to get back what the settings for those objects are.
True, but the process does take place in Antidote, so the back end ...
the output stage ... of such a task ("WriteProject" ?) is already coded.
As for getXXX() .. backing in such a function sounds like a sweep of the
tasks,
but a clean sweep.
Even if you could retro-fit every task out there with getters,
-what about overloaded set operatons? which one should the get return?
-what about property assignments. Tasks get their setters with
properties expanded.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
