We can always query the HibernateSessionSource service for the
Configuration and get a PersistentClass from it. From there I believe we
can get all the information we need.
Cheers,
Uli
Alejandro Scandroli schrieb:
I think this would be quite difficult to implement in
tapestry-hibernate without parsing hibernate's metadata and storing it
in some kind of metadata container, which is what Trails is doing.
Alejandro.
On Tue, Jan 20, 2009 at 12:33 AM, Thiago H. de Paula Figueiredo
<thiag...@gmail.com> wrote:
Em Mon, 19 Jan 2009 16:14:01 -0300, Kevin Monceaux <ke...@rawfeddogs.net>
escreveu:
On Wed, 21 Nov 2007, Francois Armand wrote:
For now, BeanEditor (or BeanEditForm) is not really aware of collection
as a property. I think it's in the todo list (T5 still alpha, etc ;)
Tapestry 5.0.18 is not alpha nor beta: it's the first stable,
ready-for-production release. (at least it's what is written in
tapestry.apache.org)
Regarding collections, Java generics don't help, as they lose the
parameter's info in runtime (erasure). That's why the encoder parameter of
the Select component is not required and the same parameter of Palette is
required.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
