Oh, I missed something, Adapter1 *was* using your implementation all along,
if you see its implementation of unmarshall and marshall:
// Class Adapter1:
public Date unmarshal(String value) {
return
(-->be.ucm.career.converter.jaxb.DateAdapter.parseDate(value)<--);
}
public String marshal(Date value) {
return
(-->be.ucm.career.converter.jaxb.DateAdapter.printDate(value)<--);
}
>From this JAXB bug that came in this morning:
https://jaxb.dev.java.net/issues/show_bug.cgi?id=780, I just noticed that
the developer's print/parse data methods end up being called by the Adapter1
class that it generates.
Oh well,
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/JAXB-bindings-and-xs-date-to-java-util-Date-conversion-tp2143517p2256676.html
Sent from the cxf-user mailing list archive at Nabble.com.
