My current custom link/service uses named parameters on the component:
<a jwcid="@ParamLink" someParam="value1" anotherParameter="value2">link</a>
And the first and only service parameter is a Map the informal parameters set as key/value pairs. Maybe I'll combine my approach with your method search and allow my listener methods to look like this:
public void doSomething(Map map)
Or maybe what you've done could be extended to look for that signature as well?
I'd really love for all the links to be simplified somehow. It's confusing to me to have so many link types and different entry points (plain page, listener method, external link entry point).
Erik
On Apr 13, 2005, at 6:54 PM, Howard Lewis Ship wrote:
This one was suggested by Erik, I think. Details on my blog:
http://howardlewisship.com/blog/2005/04/improved-listener-methods-in- picasso.html
It's all checked in and works like a charm. And its all backwards compatible.
-- 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]
