Thanks for the suggestion, Igor.
I made up this use case just to keep it very simple.
My real question is still the following: is it possible to extend Select (or
any other tapestry-core component that extends AbstractField)?
----- Original Message -----
From: "Igor Drobiazko" <igor.drobia...@gmail.com>
There is no need to extend the Select component for your use case. Just
create an instance of EnumSelectModel [1] and pass it to the Select
component.
[1]
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/util/EnumSelectModel.html
2011/4/15 Keio Kraaner <k.kraa...@gmail.com>
Hi
I'm trying to extend Tapestry's Select component.
My idea is to create EnumSelect class (class EnumSelect extends Select)
that takes an Enum class as a parameter, and based on this creates
SelectModel and ValueEncoder.
Everything works fine, but each EnumSelect in a tml-file results in 2
rendered selects in output - at first Tapestry invokes render methods of
EnumSelect and then Select.
What should I do to get only 1 select in rendered output?
Is it even possible to extend existing AbstarctField implementation? I do
not see such an example in tapestry-core library.
Regards
Keio Kraaner
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
--
Best regards,
Igor Drobiazko
http://tapestry5.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
