Hi Lukas,
On Apr 8, 6:13 pm, Lukas Eder <[email protected]> wrote:
> I could release early, as your reported issues concerning
> serialisability are rather urgent. Say, by the end of next week? In
> the mean time, you can always download the jOOQ trunk from
> here:http://sourceforge.net/projects/jooq/develop
A quick release would be great off course but I don't want to rush
you :) I'm already quite happy if i can experiment with the trunk
version. Speaking of which, when i try to compile the current trunk
version of jOOQ on my home PC, i get:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Compiling 208 source files to /home/sander/NetBeansProjects/jOOQ/build/
classes
/home/sander/NetBeansProjects/jOOQ/src/org/jooq/impl/
AbstractStoredObject.java:113: warning: non-varargs call of varargs
method with inexact argument type for last parameter;
cast to java.lang.Object for a varargs call
cast to java.lang.Object[] for a non-varargs call and to suppress this
warning
setField(parameter, this.<T> constant(null));
/home/sander/NetBeansProjects/jOOQ/src/org/jooq/impl/
AbstractStoredObject.java:113:
<T>setField(org.jooq.Parameter<T>,org.jooq.Field<T>) in
org.jooq.impl.AbstractStoredObject cannot be applied to
(org.jooq.Parameter<T>,java.util.List<org.jooq.Field<?>>)
setField(parameter, this.<T> constant(null));
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
1 warning
/home/sander/NetBeansProjects/jOOQ/nbproject/build-impl.xml:524: The
following error occurred while executing this line:
/home/sander/NetBeansProjects/jOOQ/nbproject/build-impl.xml:258:
Compile failed; see the compiler error output for details.
BUILD FAILED (total time: 5 seconds)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
When i tried this earlier to day on my work PC, i saw the same error
in Netbeans, but for some reason it compiled anyway.
Do you have any idea what's going wrong here?
> The "Attachable API" is functional. Integration tests are running
> smoothly, so far. So you could already test serialising and
> re-attaching Query and Record objects (pre-release bug reports would
> be very welcome). But be aware of the fact that I might change some
> API elements before releasing 1.5.7
Just to make sure i understand how this is supposed to work - i need
to explicitly call [attachableobject].attach(newJooqFactory) before i
try to use a deserialized jOOQ object, right?
Would it be possible to add some kind of mechanism that
"automatically" re-attaches objects to a new factory whenever
necessary?
For instance, i can imagine that you could add some overridable method
to the Factory class (a "factories" factory) that allows the user to
define how a new factory should be created whenever needed so that
whenever a jOOQ object discovers that it's detached, it can call that
method to get a working factory. That way, a user could "ignore" the
whole serialization/deserialization process.
