I should've also mentioned that the registration/configuration part is
because you have to manually (at least currently, I'm hoping this will
change) register custom/extended data types with Cayenne before using
them. Should you need to implement your own data types in the future,
you could use this code as an example if needed.
/dev/mrg
-----Original Message-----
From: Gentry, Michael (Contractor) [mailto:michael_gentr..anniemae.com]
Sent: Monday, May 02, 2005 1:59 PM
To: cayenne-use..bjectstyle.org
Subject: RE: How to use Enums
You only need to do the configuration once in your application (before
using the enumerations).
/dev/mrg
-----Original Message-----
From: sastan [mailto:sasta..-d-o-t.com]
Sent: Monday, May 02, 2005 1:33 PM
To: Cayenne User
Subject: RE: How to use Enums
> Parts of it may seem a bit cumbersome, but I wanted something that
could
> log values nicely (hence part of the redundancy). When I have time, I
> also plan on putting together a Tapestry class that implements the
> IPropertySelectionModel interface, so that you can put the
enumerations
> in a pulldown easily (with localization if I get ambitious).
I am working on project for my studies where i build a tapestry app with
cayenne. In this project i will use your enums and so i will have to
work out such a component. It is not a promise but when i have a it i
will post it.
By the way. Where should the configure step take place. On each
DataContext creation? Or just once for a application and where to do it
in a tapestry app?
sastan
This archive was generated by hypermail 2.0.0 : Mon May 02 2005 - 15:44:17 EDT