Thorsten Scherler wrote:
I replied in a another response with respect to the processing paradigm.
This response is about a different issue, hence the change in subject.
The business helper that we have are best described by our most famous
contract.
<forrest:contract name="content-feeder">
<forrest:properties contract="content-feeder">
<forrest:property name="content-feeder"
nugget="get.nugget.feeder">
<url>/feeds/somefeed.xml</url>
</forrest:property>
</forrest:properties>
</forrest:contract>
Which will request parts of the presentation model from the feeder
plugin. This is quite basic for now and we have to extend on it.
If the purpose of this logic is simply to request content then why not
have something like:
<forrest:contract name="content-include-xhtml">
<url>cocoon://feeds/somefeed.xml</url>
</forrest:contract>
My point is that this is far simpler to read, than the above, yet it
appears to contain the same information. I know it won't work with the
current implementation, my question is why is it not implemented in this
way, what is the purpose of the extra complexity we currently have?
Ross
