> I'm really hoping to eliminate
> page and component specs entirely at some
> future date.
Spiffy.
> My other impression is that this will heavily overlap Spring
> Web Flow or other similar technologies, and perhaps what we
> need is to properly wrap such a library, rather than reinvent
> it inside Tapestry.
Oh, interesting...I missed the "web flow" angle in my first read.
Instead of getting that fancy right away, a simpler, short-term use case
that is a good starting point and could grow into what Mind Bridge is
talking about would be:
<a jwcid="@SomeLink" page="PageName" parameters="#{'fooId': 1,
'otherProperty': 'asdf'}">
And having it generate the URL:
/context/PageName.html?fooId=1&otherProperty=asdf
And the parameters are auto-mapped to page properties, so in your page
listeners/onRender/etc. all you have to do is:
this.getFooId()
The @SomeLink syntax could change, e.g. maybe fooId=1 is a full attribute
instead of in a Ognl map, but seeing exactly "?fooId=1" and not some
squeezed/base64-encoded/etc. in the URL is important (to me in terms of
style/elegance/etc.).
This is really just finishing up the great start already made with Friendly
URLs.
As an asside, I've got a hack that does this via overriding page.attach and
doing, psuedo-code, BeanUtils.populate(page, request.getParameterMap()). But
having this rolled in as an official feature, in the correct
Tapestry/HiveMind fashion, etc., woudl, for me, be 4.0's killer feature
(along with the current Friendly URL support).
- Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
