forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sina K. Heshmati" <>
Subject Re: Using javax.xml.xpath
Date Tue, 11 Dec 2007 13:48:47 GMT
Thorsten Scherler <> said:

> On Tue, 2007-12-11 at 14:15 +0100, Sina K. Heshmati wrote:
> ...
>> OK. So I suspect we should stop using an attribute called @xpath as it turns out
>> to be misleading since there however exists only two possible positions, namely
>> /html/head and /html/body.
> No, that is only true for html. The dispatcher supports more the html.
> Meaning in a custom xml format that can be any position.
>> Your argument though about not indicating in the contract itself where it will be
>> injected seems quite valid to me.
>> But the problem is that [4] and [6] are quite similar and the only difference is
>> that in [6], an extra contract has been called, but still I had to copy-and-paste
>> all the other contract calls.
> Not if one makes good usage of panels, then the code overhead can be
> reduced to a couple of lines.
>> How could one avoid ending up maintaining a number of forrest:views with a lot of
>> duplicate content between them?
> a) Panels. Grouping of common hooks and contracts and calling them from
> one structurer. That let you as well panels as whole.
> b) using jx to decide when to use a contract.
> I am using a) and b) a lot in my current project (next version of
> and we have reduced the duplicated code in
> the structurer very much.
OK, that's what I wanted to know. Thanks for your time!


View raw message