Hello Thomas, Thanks for your message.
jOOQ currently doesn't support the Oracle XMLType out of the box, yet. The pending feature request is here: https://github.com/jOOQ/jOOQ/issues/1112 However, you can implement your own jOOQ to JDBC data type Binding as documented here: https://www.jooq.org/doc/latest/manual/sql-building/queryparts/custom-bindings For support of XMLType in UDTs, you will need to implement these two methods: void set(BindingSetSQLOutputContext<U> ctx) throws SQLException; void get(BindingGetSQLInputContext<U> ctx) throws SQLException; ... in order to bind your own, custom XML representation to JDBC's SQLOutput and SQLInput types. If you need top-level XMLType support, other Binding methods will need to be implemented as well. I'll be very happy to guide you through this implementation if you have any specific questions. Best Regards, Lukas 2017-03-30 15:27 GMT+02:00 Thomas Fuchs <[email protected]>: > Hello Everyone! > > We're migrating Oracle JPublisher Code having a deeply structured > hierarchy of UDTs (PLSQL Types). > Some fields in the Oracle DB are sys.xmltype resulting by now in > java.lang.Object in our generated JOOQ Code. > > With JPublisher we had a "hint option" for code generation > > -adddefaulttypemap=SYS.XMLTYPE:oracle.xdb.XMLType > > Is something similar possible with JOOQ ?!? > > thank you for reading > and answering > > Thomas Fuchs > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
