Dmitri Colebatch wrote:
Hi again,
I'm trying to get my head around where the right place to put these
changes is and wouldn't mind if someone could answer a couple of
queries.
I'm looking at AnnotationBinder.mustBeSkipped and thinking that I'd
like to replace that with something along the lines of
property.isTransient() which would then give me somewhere to bundle
the current logic but also allow for @TransientOverride annotations.
However - this is obviously not the right place for it as there's
right, the XLayer should be agnostic regarding the annotations behavior.
nothing remotely similar in there.
Instead, I assume that AbstractPropertyHolder is in fact the right
place for this logic, but my problem then is how do I get access to
this from in AnnotationBinder.addProperty?
the caller of addProperty has a propertyHolder
Any chance of a prod in the right direction?
cheers
dim
On 3/22/06, Dmitri Colebatch <[EMAIL PROTECTED]> wrote:
Hi all,
Firstly, I'm new to the list, and until a month or so ago hadn't used
hibernate for a few years, so if I say something out of line, let me
know.
A bit of background (don't worry, I do have a developer question
further on): I'm in the dying stages of trying to use hibernate to map
JAXB2 generated classes to a database - I can't change the structure
of the db, nor the structure of the schema that drives the generation
of the classes. What I've done so far is to restructure the JAXB
generated classes as best I can to enable hibernate to store them in
the database.
I'm facing what I believe is a limitation in embedded classes relating
to properties that might be transient in the embedded class, but we
want to save for this usage, or vice versa. I've posted this on the
forums (http://forum.hibernate.org/viewtopic.php?t=957009) but will
repeat it here as this is probably the right place.
What I'd like to do is submit a patch that allows the following:
@Embeddable class Foo
{
@Transient String firstName;
@Column String lastName;
}
@Entity class Bar
{
@Id Long id;
@Embedded
@TransientOverride(name="firstName", transient = false)
@AttributeOverride(name="firstName", column = @Column)
Foo foo;
}
I hope that's fairly self-explanatory. I've dug through the code and
feel reasonably confident that I could put a patch together, but don't
want to do anything that wouldn't be acceptable.
Any thoughts/suggestions on the above? My motivation is that I have
an xml schema that has reuse of a few key types (eg Price) that
contain different elements, not all of which are applicable to every
usage.
cheers
dim
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
