So simple it's embarassing I hadn't figured that out yet. Oh well, thank
you Howard. My custom encoder works great now.
All I had to do was write an implementation of the ServiceEncoder
interface and put the line below into my hivemodule. So great.
<encoder id="page"
object="instance:com.elidoran.tapestry.encoder.PageServiceEncoder"/>
Tapestry Picasso is even better to work with than 3.0 and I can't even
use the annotations yet.
~eli
Howard Lewis Ship wrote:
Use
object="instance:foo.bar.Baz"
or
object="service:mymodule.MyService";
The former instantiates an instance of the class; the latter is a
reference to a HiveMind service.
In either case, the object so reference must implement the right interface.
On 7/14/05, Eli Doran <[EMAIL PROTECTED]> wrote:
How do you put a customer service encoder into your hivemodule.
tapestry.url.xml has the schema and the configuration point info but i
can't seem to use the "encoder" element. I can use all the subelements
from the schema like page-service-encoder just fine. specifically, for
the <encoder> tag what do you specify for the "object" attribute? Can
you specify the class, or do you give a service...or an you not use the
<encoder> element?
<contribution configuration-id="tapestry.url.ServiceEncoders">
<page-service-encoder id="page" extension="page" service="page"/>
<encoder id="testEncoder" before="*"
object="com.elidoran.tapestry.encoder.TestEncoder"/>
</contribution>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
