There's nothing specifically in the framework, nor anything planned, that
I know of. There is a "ListPropertySelectionModel" in Tassel
(http://www.tapestrycomponents.org/Tassel/app?service=external/ViewComponent&sp=SListPropertySelectionModel)
which does the same thing in almost exactly the same ma
> Pre-Question: where can documentation issues/corrections/additions be
> sent? Better to send to the dev-list?
>
The best thing would be to open up a Jira issue.
Robert
>
>
>
>
> I lost some time trying to work with the Script component and wanted to
> offer some suggestions:
>
>
>
> http://jak
There are multiple ways to accomplish this.
One way might be to do something like (I'm going to assume that you're
using the "base" library provided on t-deli. If not, you can substitute
the if/else components with appropriate conditional components):
Preliminary Scales
I'd be interested in seeing where it's documented that it works in 3.0.x.
In fact, people have tweaked 3.0.x to make a global message catalog work
(I don't recall the particulars offhand), but out of the box, there is no
such mechanism for 3.0.x. Thus, it /is/ a change (improvement) in
functionali
To be honest, personally, I don't think that approach is really going to
mix well with tapestry. As was mentioned by HLS in a recent thread, you
should consider pages at runtime as immutable. Removing elements will
prove problematic, I think.
An approach I used was to create a sort of "inRole" co
Best bet here is definitely going to be a parameter.
Or to go ahead and put the listener in the component... :) Can the
listener be generalized? If so, put it in the component, and you'll save
yourself time and effort later (and debugging time, and... :)
But that having been said...
(note, I'm a l
> In running the DirectLink sample, it looked like a malicious user could
> easily replace parameters by manipulating the URL.
>
> Sure enough, fiddling with a running sample confirmed it.
>
> Other than manually checking incoming parameters, has anyone devised a
> simpler, less error prone strateg
Harish submitted a patch a /long/ while back that dealt with the scenario
of how to set a particular field in error when it's rendered in a loop. He
added a new "index" property, as I recall. The patch was never applied,
but if you search the archives for it, you should be able to find it.
I also
