Hi Darren,

jOOQ knows XML and JSON serialisation on a Result level:
http://www.jooq.org/doc/3.2/manual/sql-execution/exporting/

JSON importing / deserialisation is currently being worked on by Johannes
Bühler, a new contributor:
https://github.com/jOOQ/jOOQ/pull/2849

Now, what you're asking for makes total sense to me. As jOOQ already
clearly specifies general export formats, there's no stopping us from
adding relevant JAXB annotations to allow for such exports through the JAXB
APIs as well. I have registered a feature request for this:
https://github.com/jOOQ/jOOQ/issues/2850

However, instead of just adding @XmlTransient, I'd like to implement this
thoroughly.

Cheers
Lukas

2013/11/16 Darren S <[email protected]>

> It would be nice to be able to serialize a TableRecord to XML or JSON.  It
> doesn't work right now though because TableRecordImpl.getTable() will cause
> a circular reference that will blow up with a stack overflow.  There are
> ways I can work around this, I can configure Jackson to ignore getTable()
> or I can override the JavaGenerator to have the record implement an
> interface that will mark the field as @XmlTransient.
>
> I was curious if this is something that jOOQ should support out of the
> box.  Currently it means just adding @XmlTransient to
> TableRecordImpl.getTable() as I think that is the only public bean style
> getter that there is on the class.  I could understand if jOOQ wouldn't
> want to support this as you would have to be careful with every addition to
> TableRecordImpl and its super classes that you don't accidentally add a
> getX() method without a @XmlTransient.
>

-- 
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/groups/opt_out.

Reply via email to