|Aleksey Perfilov||Oct 10, 2008 12:55 pm|
|Kevin Brown||Oct 10, 2008 2:35 pm|
|Aleksey Perfilov||Oct 10, 2008 3:32 pm|
|Aleksey Perfilov||Oct 10, 2008 4:07 pm|
|Kevin Brown||Oct 10, 2008 4:13 pm|
|Aleksey Perfilov||Oct 10, 2008 5:07 pm|
|Evan Gilbert||Oct 10, 2008 5:21 pm|
|Ian Boston||Oct 11, 2008 5:04 am|
|astha||Oct 14, 2008 1:03 am|
|Parrott, Justin||Oct 14, 2008 6:28 am|
|peeyush gulati||Oct 14, 2008 9:13 am||.zip|
|Chris Chabot||Oct 14, 2008 10:38 am|
|Dan Peterson||Oct 14, 2008 2:53 pm|
|xin zhang||Oct 14, 2008 2:58 pm|
|peeyush gulati||Oct 14, 2008 3:12 pm|
|astha||Oct 14, 2008 11:45 pm|
|Astha Bhatnagar||Dec 9, 2008 1:55 am|
|Ropu||Dec 9, 2008 4:00 am|
|Chris Chabot||Dec 9, 2008 5:20 am|
|Bob Evans||Mar 27, 2009 3:19 pm|
|Subject:||Re: crash in BeanJsonConverter|
|From:||Aleksey Perfilov (aper...@hi5.com)|
|Date:||Oct 10, 2008 4:07:59 pm|
I think I misinterpreted what Kevin said.
I agree that using annotations is preferable, although name based matching can be also left in place, in case annotations are not present, as I mentioned, for imported classes.
On 10/10/08 3:33 PM, "Aleksey Perfilov" <aper...@hi5.com> wrote:
True, and of course we do that for our own classes. But in case you end up using some other class that comes from standard Java or some library, you can't annotate that. Perhaps using an adapter in some way might be the only way then.
Besides, I actually don't see annotations being taken into account in BeanJsonConverter code. It just grabs all methods that start with "get" when converting object to json. Actually, I just noticed that in the Person class from org.apache.shindig.social.opensocial.model, getGender is not annotated, neither is getUtcOffset, yet both of them are converted to json.
On 10/10/08 2:36 PM, "Kevin Brown" <et...@google.com> wrote:
I think it would make more sense to use annotations on the beans instead of doing name based matching. That way you're always explicit in what you export and don't have problems like this.
On Fri, Oct 10, 2008 at 12:55 PM, Aleksey Perfilov <aper...@hi5.com>wrote:
I¹ve had problems using BeanJsonConverter on objects that contain getters that have 1 or more arguments. Since convertMethodsToJson() expects not to see any arguments on getters, invoke() will crash on getters that have some.
Do you think we should adjust getMatchingMethods() to filter out getters that require parameters? Or just skip those getters in convertMethodsToJson(). I think it is reasonable to assume we don¹t need those for conversion purposes.