The actual way for cayenne is the defintion of getter/setter pairs
an so a non persistent attribute is born.
So far so good, but it would be fine if I could see them in
the modeler/map-definition. It would be very helpful
for the project-informations within the project-team.
We have the separation between DbEntity and ObjEntity.
One of the benefits of this kind of structure is that you
can have attributes in the ObjEntity that are not part
of the DbEntity. This attributes are non persistent.
With these attributes an ObjEntity is improved to a BusinessObject.
--- Juergen ---
2007/3/18, Aristedes Maniatis <ar..aniatis.org>:
>
>
> On 17/03/2007, at 5:17 AM, syrinx wrote:
>
> > I am looking for a way to declare non persistent attributes using
> > the cayenne
> > modeler? I know that I can add my own attributes manually in the
> > subclasses
> > generated by the modeler, but it would be nice if these attributes
> > could be
> > included in the auto-generated entity class instead. Is this
> > possible?
>
> If these attributes are the same for every entity, you can do this by
> editing the templates which are used to create the entity classes.
> Otherwise, I don't understand why editing the subclass isn't the
> easiest approach.
>
> Ari
>
>
>
> -------------------------->
> Aristedes Maniatis
> phone +61 2 9660 9700
> PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8
>
>
>
This archive was generated by hypermail 2.0.0 : Sun Mar 18 2007 - 08:33:58 EDT