"Imitation is the sincerest form of flattery." :-)
Seriously, the problems that Pull Model solves for Turbine apps was the primary
motivation for implementing nested and indexed property handling in Struts.
It's going to get even better if we succeed in implementing property getters
that can transparently access information from a tree of Java objects (the
current model), a JDBC RowSet, or an XML DOM structure -- all *transparently* to
the page designer. For more powerful accessing capabilities, I also want to
look at XPath expressions -- again, with the underlying data architecture being
transparent, so that the business logic developers can remodel things to their
The only agreements that will be needed between business logic developers and
page developers are the names of the action mappings, the names (and scopes) of
the relevant beans, and the access paths to the relevant properties.