<jaxb:globalBindings> javaType causes @Transient

[mzdeb]

Firstly thank you for your hard work! :)

I want to map Joda Time classes (LocalDate, LocalDateTime etc.) to DB so I configured globalBindings:

<jaxb:globalBindings>
    <jaxb:javaType name="org.joda.time.LocalDateTime"
        xmlType="xsd:dateTime" parseMethod="org.joda.time.LocalDateTime.parse"
        printMethod="java.lang.String.valueOf" />
    <jaxb:javaType name="org.joda.time.LocalDate" xmlType="xsd:date"
        parseMethod="org.joda.time.LocalDate.parse" printMethod="java.lang.String.valueOf" />
</jaxb:globalBindings>

I've also annotated fields with Hibernate Type annotation like:

        <jaxb:bindings node="//*[@type='xsd:dateTime']"
            multiple="true">
            <annox:annotate target="getter">@org.hibernate.annotations.Type(type
                = "org.joda.time.contrib.hibernate.PersistentLocalDateTime")
            </annox:annotate>
        </jaxb:bindings>

Result is:

    @Transient
    @Type(type = "org.joda.time.contrib.hibernate.PersistentLocalDateTime")
    public LocalDateTime getDate() {
        return date;
    }

As you can see @transient is undesirable here. I've found similar bug for previous Hyperjaxb realeases: http://jira.highsource.org/browse/HJIII-97 but it's still unresolved.

[highsource]

HJ3 adds @Transient as it assumes that the type of the property is not known to JPA. HJ3 can't also possibly know about all the types which are mappable with Hibernate. It also can't reason about annotations you add via Annox.

So, in core, @Transient isn't wrong here.

I see two ways to solve this:

• Add a HJ3 feature to turn off @Transient for such cases.
• Add a jaxb2-annotate-plugin feature to be able to remove a certain annotation.

I'd prefer the second option. It may feel a bit hacky, but it's not wrong in the scope of jaxb2-annotate-plugin and will produce expected results.

[mzdeb]

From my point of view both solutions are ok. If you prefer the second one it's fine with me.