On Thu, 19 May 2011 02:31:40 -0300, libaoming <[email protected]> wrote:
hello!
Hi!
i'am using tapesty5.2.0,when render select options must be enum or
string list?
Absolutely no. The Select component
(http://tapestry.apache.org/current/tapestry-core/ref/org/apache/tapestry5/corelib/components/Select.html)
has a model parameter. Its type is SelectModel, which is basically a list
of OptionModel, one instance for each option in the Select.
some times options stored in database,so i must use internal APIs.
Why?
"If you ever find yourself forced to make use of internal APIs, please
bring it up on the developer mailing list; this is how we know which
services should be exposed as public, and fall under the backwards
compatibility umbrella."
Which APIs, classes and interfaces for dealing with the Select component
do you think are internal? SelectModelImpl and OptionModelImpl are
internal, but even if SelectModelFactory didn't exist you could still have
your own implementation of SelectModel and OptionModel.
is any way to solve this problem?
As ningdh suggested, use the SelectModelFactory service.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
