It *should* be pretty straightforward. You map a prefix, such as "ognl:" or "message:" (or in your case, "jxpath:") to a BindingFactory service.
The BindingFactory is responsible for creating an IBinding instance; you will usually create your own subclass of AbstractBinding and pass what data is needed into your subclasses's constructor. Outside of "ognl:" being the default in a lot of places, there's nothing special about the OGNL binding factory vs. any other implemenation, including yours. Tapestry and HiveMind treat them all as equal. In fact, the intention of Tapestry 4 is to support this kind of unbounded customizability. On 10/10/05, Jim Alateras <[EMAIL PROTECTED]> wrote: > Hi, > > We are currently using Tapestry 3.x and have come across some > limitations, which we believe can be resolved by moving to v4.x. One of > our primary requirements is to support JXPath for binding data to form > fields. I believe that v4.x has the facility to support different > binding languages. Is this the case? > > Can anyone point me in the right direction for developing JXPath support. > > cheers > </jima> > > > --------------------------------------------------------------------- > 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]
