I'd suggest you use a single "activate" event handler, with a signature like
this:
public Object onActivate(EventContext ec)
You can see it being used in here:
http://jumpstart.doublenegative.com.au/jumpstart/together/onepagecrud/persons
Doco is here:
http://tapestry.apache.org/component-events.html#ComponentEvents-EventContext
HTH,
Geoff
On 16/12/2012, at 4:34 PM, Ken in Nashua wrote:
>
> This doesnt work...
>
> public Object onActivate(Class clazz, String id)
> {
> if (clazz == null)
> return Utils.new404(messages);
>
> this.bean = contextValueEncoder.toValue(clazz, id);
> this.beanType = clazz;
>
> if (bean == null)
> return Utils.new404(messages);
> return null;
> }
>
> cant get a breakpoint to set here
>
> all i did was add formal parameter "Class clazz" and a little usage
>
> It is very disheartening and discouraging that at this late in these releases
> that nothing is reliable or consistent or hardened.
>
> and I am thinking if I go commercial or commit commercial with something...
> where will i stand then?
>
> it wuold be really nice if this framework and affiliates would settle down
> finally and let something tangible gel for once.
>
> i come from an XWindows R&D in the late eighties and I developed far more
> formidable apps with XWindows out of MIT than anything else due to it's
> reliable documentation and consistent runtime.
>
> I dont accept the fact that open source is open source suck it up and run
> with it
>
> i have seen companies use these frameworks and its impact on product and
> developer
>
> And I keep asking myself... when is this going to work
>
> just frikkin pissed
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
