Question concerning java Serialization of a complex internal field variable.

Question

Not everything in the J2SE implements serializable by default.  Say BufferedImage.
I have learned from an online artical that absolutely all fields to be serialized must
implement Serializable, including internal ("global") class fields,
a la
http://javarevisited.blogspot.com.au/2011/04/top-10-java-serialization-interview.html
(point 5).
However, for my purposes, I cannot re-implement (extend) and recompile every and any
java class I would want to serialize, eg. anything which is a "complex" sub field of
a conceptual class I do want to serialize, which doesn't occur on the java 1.6 list
of default serializable classes:
a la
http://docs.oracle.com/javase/6/docs/api/java/io/Serializable.html
and
"If member variables of a serializable object reference to a non-serializable object, the code will compile but a RumtimeException will be thrown."
Understanding there are implications for the java security model, is there anything to be done for these non-serializable-implementing class fields?
Is there a Serialization add on kit for Java or something?

Answer 1

Indeed, however, with a distinct lack of success with the instrumentation api, my request is dualfold now.
I do understand the restrictions explained here concerning more complex classes and the Serializable API.
I have found that there is an input line that needs to be submitted when running an Inustrumentation, premain Agent class.
However, I would have to avoid that by doing System.setProperty(a,b); appropriately.
Why won't the following just work, without any further supplied input parameters?
   import static java.lang.System.out;
   import java.io.PrintStream;
   import java.lang.instrument.Instrumentation;
   public class InstrumentationAgent
      private static volatile Instrumentation globalInstrumentation;
      public static void premain(String paramString, Instrumentation paramInstrumentation)
         System.out.println("premain...");
         globalInstrumentation = paramInstrumentation;
      public static void agentmain(String paramString, Instrumentation paramInstrumentation)
         System.out.println("agentmain...");
         globalInstrumentation = paramInstrumentation;
      public static void main(String ... args)
         out.println("!");
         String data = new String("data");
         long size = getObjectSize(data);
         out.println(size);
      public static long getObjectSize(Object paramObject)
         if (globalInstrumentation == null)
            throw new IllegalStateException("Agent not initialized.");
         return globalInstrumentation.getObjectSize(paramObject);
I am still curious as to how the DataFlavor approach I have outlined above.  Does it accomplish a shallow or deep conversion?  Are
there other limitations which restrict what's put to the underlying ByteOutputStream?
Why won't my agent class execute though, regardless?