Hi Darío.
Look at the source code. It only takes a minute to find out why.
You're passing in a RadioPropertySelectionRenderer, right?
If there is no renderer, PropertySelection puts onChange and
informal parameters in the select tag:
writer.begin("select");
...
if (getSubmitOnChange())
writer.attribute("onchange", "javascript:this.form.submit();");
...
renderInformalParameters(writer, cycle);
But if you use a renderer, that renderer does whatever it wants.
RadioPropertySelectionRenderer doesn't output informal parameters,
but you could easily modify it to do what you want.
Cheers,
Nick.
Darío Vasconcelos wrote:
Whatever. In the end, I decided to use a Script component to add the
onChange functionality. Nevertheless, it seems to me too big a problem
just to include a tiny onChange script...
On 7/21/05, Darío Vasconcelos <[EMAIL PROTECTED]> wrote:
OK, nevermind. After googling the subject, I came across an article
that explains how to render a PropertySelection as a table of radio
buttons...
<span jwcid="@PropertySelection" model="..." value="..."
renderer="ognl:@[EMAIL PROTECTED]"
/>
Good. Now I just want to know how to add an onChange event to the
PropertySelection, since I'm using it to turn on and off a series of
layers...
Is this possible? The PropertySelection seems to ignore whatever
informal parameters I add...
Regards,
Dario
On 7/21/05, Darío Vasconcelos <[EMAIL PROTECTED]> wrote:
Hi,
I want to include a radio button in my app, but without the
look-and-feel that RadioGroup offers. The documentation says a Radio
component can be indirectly wrapped inside a RadioGroup component. How
is this?
--
Communism is man's exploitation of man. Capitalism is just the opposite.
--
Communism is man's exploitation of man. Capitalism is just the opposite.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
