You need to have two distinct attributes in the entity. You can point
those attributes to your columns using @Column annotation
glassfish_at_javadesktop.org wrote:
> I'm dealing with this codebase that has an entity with a column of the same name defined in both the primary and secondary table. This attribute has a not null constraint on it which in a particular scenario fails.
>
> I have no control over the schema so it can't be changed.
>
> Is there way to have the getX, setX in the primary entity updated so that it works for cases of the primary or secondary?
> [Message sent by forum member 'samdoyle' (samdoyle)]
>
> http://forums.java.net/jive/thread.jspa?messageID=286088
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>