Comments on Grid Designer's Blog: Oracle Coherence using POF, without a single line ...

That is true. You have to provide no-args constru...

2011-05-11T03:27:31.752-07:00

That is true.
You have to provide no-args constructor (eigther public or private). Otherwise blank object instance cannot be create via reflection.

ReflectionPOFSerializer can handle private no-arg constuctors, which is useful if you want to protect your classes against misuse.

If no-arg constructor is not an option for you you can always mix and match ReflectionPOFSerializer with any other kind of serializer.

Myself, I usually use handmade POF for domain objects and ReflectionPOFSerializer for entriprocessors, value extractors and other types of mobile agents in Coherence.

One problem that hasn't been mentioned is that...

2011-05-09T09:12:44.043-07:00

One problem that hasn't been mentioned is that you'll need to make sure that every object has a default constructor. This may not always be desirable. It works beautifully for simple objects though. Thanks!

Interesting idea. Current implementation is not de...

2010-07-14T08:32:10.629-07:00

Interesting idea. Current implementation is not designed to support POFExtractors. But it turns out to be quite simple to implement.
I need some more time to properly cover new ReflectionPofExtractor with test.
I will publish PofExtractor support soon.
Thanks for an idea.

how can you use this with POFExtractor and filters...

2010-07-13T06:03:14.646-07:00

how can you use this with POFExtractor and filters ?

I assume that was jmap, not lmap, not sure where have you find reference to lmap in this post.

Where can I find information about this "lmap...

2010-01-05T02:11:23.401-08:00

Where can I find information about this "lmap" tool you talked about? I know about "jhat" for heap analysis but not not lmap...

Googling ling did not find anything...

Hi ZeoS. I use this implementation with about 50 ...

2009-12-23T08:57:17.948-08:00

Hi ZeoS.

I use this implementation with about 50 classes (number of classes was a motivation to write generic tool in first place). Reflection in java can be extremely fast if you do it right. JVM generates code for relflection accessors, which is further optimized by JIT like your own code.
Creating an accessors is expensive operation, of cause, and any reflection based code should carefully cache generated accessors.
In my implementation a class serialization scheme is generated on first attempt to serialize/deserialize object of given class. Such serialization scheme stores all field accessors needed and they are generated only once for each class.
In other words, my implementation has own reflection cache to avoid lookup overheads.

2009-12-23T08:49:09.188-08:00

This comment has been removed by the author.

Have you tried this with some real scenario? Refl...

2009-12-23T06:41:20.560-08:00

Have you tried this with some real scenario? Reflection will cache method lookups and the class loading will be done only in the first loop. by testing it with only one object/class you almost discard that overhead.

Thanks for a link Patrick, looks interesting. But ...

2009-10-19T06:09:23.915-07:00

Thanks for a link Patrick, looks interesting. But I really like to keep my domain objects clear from product specific annotations.
From the other side, ability to generate .NET and C++ would be great.
I will look forward for project evolution.

Nice post, thanks for sharing this! You might be ...

2009-10-07T08:34:27.158-07:00

Nice post, thanks for sharing this! You might be interested to look at this approach as well from Rob Varga:

http://coherence.politext.info/pof-serializer-generator-java-apt-plugin