Hm. It definitely works if you define a bean that has a property of type ArrayList<Foo>. I'll see if I can reproduce the issue with just a straight ArrayList<Foo>.
On Nov 23, 2010, at 7:41 PM, Bill van Melle wrote: > OK, this is fixed. When JSONSerializer encounters a key that references a > non-existent bean property, that value will be ignored. > > Thanks! I updated my build, and it seems to work correctly when encountering > unknown properties. > > However, I still have no way to read a typed json list. As I reported > earlier in the thread, the TypeLiteral kludge doesn't work, breaking in the > serialization code. I also tried your other suggestion of defining a trivial > class that extend ArrayList<Foo>. That one doesn't break until I try to read > the contents of the list. The serializer does indeed return a ListOfFoo (the > trivial class I defined), but the elements of the list are not of type Foo, > but rather of type HashMap, presumably the same untyped string/value pairs > I'd get were I to just ask for untyped json in the first place.
