Re: component definitions

>> Actually,  I used the property file because it was something
> that was going
>> to change frequently, and because I coded that before OGNL
> was available.
>>
>> So I could have done it as:
>>
>> <binding name="tabOrder"
> expression='{ "Home", "Foo", "Bar", "Baz" ... }'/>
>>
>> If I was doing it today.
>>
>> Either way, it is only configured once.
>
> but you would have had to repeat the binding with the exact
> same values in every page that uses the Border component,
> right?

Oh Christian, come on!
A lot of people already mentioned that it depends entirely on how you 
implement your component if you have to specify those bindings to your 
component or not. If the 'tabOrder' mentioned above doesn't change, 
well then hard-code it into your component.

If you think that stinks (like I do) then make the values mentioned 
above the default values (so you don't have to specify them on every 
page) and make that component configurable via bindings (like Howard 
mentions) if you need different values.

>> Does WOF have this feature you are suggesting?
>
> What is WOF?

Web Objects Framework
No, it doesn't have OGNL support out of the box but Project WONDER 
(wonder.sf.net) has a framework named WOOGNL that makes the WO bindings 
OGNL-aware. Didn't try it myself but the examples look quite similar to 
what we have in Tapestry today.

-dirk



-------------------------------------------------------
This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
Time is running out!  Thinkgeek.com has the coolest gifts for
your favorite geek.   Let your fingers do the typing.   Visit Now.
T H I N K G E E K . C O M        http://www.thinkgeek.com/sf/