Re: [json-lib-user] What causes: Property 'x' has no read method. SKIPPED?

[Andres A. <aal...@ya...>]

Hi Christopher,

It looks to me that your filter is configured to filter out every single property of a Geometry class/subclass unless its name is 'coordinates' or 'SRID', still it tries to process other properties?

Ahh I see JSONObject:737, the filter is applied only if the property has a read method. Let me see if it can be changed.
Btw, filed 2005661 Add class name to skipped properties messages and fixed it already.

Cheers,
Andres

 -------------------------------------------
http://jroller.com/aalmiray
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and those who don't.
To understand recursion, we must first understand recursion.



----- Original Message ----
From: Christopher Hunt <hu...@in...>
To: Andres Almiray <aal...@ya...>
Cc: jso...@li...
Sent: Saturday, June 28, 2008 11:46:45 PM
Subject: Re: [json-lib-user] What causes: Property 'x' has no read method. SKIPPED?

Hi Andres,

Thanks for your email. My reply:



Json-lib relies on PropertyDescriptors to find which properties may be serialized into JSON.
In your case there is a class that has a write-only property name geometryN (usually it just
has a setter method). I think it is a read-only property... Here's the class reference:

http://www.vividsolutions.com/jts/javadoc/com/vividsolutions/jts/geom/Geometry.html


Perhaps the property descriptor for 'geometryN' is actually for an indexed
property and not a regular one. Yes it is.


Without a proper bounded limit for that indexed property it may 
be hard to retrieve any values.

I agree that the message is not quite clear on which class is the owner of that property, I'll fix that 
for the next release. Let me think what can be done with indexed properties, you can tweak the
serialization process with JsonValueProcessors or JsonBeanProcessors for the time being.OK. Thanks. I understand the work-around - but I'm still not clear on why the warning appears when I've told JSON to filter my Geometry instances... Perhaps my filter is wrong?

Cheers,
-C