<binding> creates a binding object (an instance of IBinding) that knows about the page (*) and can read/update OGNL expression rooted in the page. The binding is passed into the component so that it can gain access to properties of the page. The <set> element is more traidtional, a value is obtained and injected in (set and forget). Parameters and bindings are bi-directional, the component can (via the binding) change the properties of the page.
(*) I use the term page for clarity, it's really the container of the component which is often a page, but nearly as often, another component. On 5/7/05, Michael Echerer <[EMAIL PROTECTED]> wrote: > liigo wrote: > > please look on <set> and <binding>, they just do the same(or very similar) > > thing, > > why not use the same keywork <set>? > > > Internally "binding" is much more than just setting a property. A > static-binding is more comparable to set. Anyhow this can be confusing > in the beginning (especially the directions). > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
