On 28/02/2008, at 2:31 AM, Mike Schrag wrote:
>> Unless I'm remembering incorrectly, WOBuilder only showed you the
>> keys that were in the model, not every possible key available to
>> you in the class. This is a huge step forward!
> I'm not sure what heuristic they use to determine this ...
>
> * At the top level, I would think you'd have to show all of the
> possible bindings on the component (sans "system" ones, which we
> remove now, too). It looks like WOB puts session and application
> up at the top of the list, which sort of makes sense
Yep.
> * I think WOB also split out actions from regular bindings, which
> is actually a little bit tricky.
Yep, actions were at the bottom underneath an hr.
> I'm not sure how they determine which ones are actions compared to
> just regular "get" methods. No way they looked at the inheritance
> hierarchy to only show methods that extend from WOActionResults
> (and even though we can do that easily, it's really expensive to
> actually do that).
I'd be guessing they did.
with regards,
--Lachlan Deck
This archive was generated by hypermail 2.0.0 : Wed Feb 27 2008 - 16:56:23 EST