>> I think this has come up before. BeanAdapter wraps a single bean instance >> and exposes its (immediate) properties via map methods. You can access >> nested properties using JSON.get(), put(), etc. >> >> However, TableView does not currently expect paths in column names, only >> keys. It could be modified to use JSON.get() instead, but I'm on the fence >> about whether that is a good idea or not. > > What about just letting BeanAdapter understand Maps as well? It will only > wrap explicilty used keys anyway, and it should be an easy fix.
No, that's what JSON#get() is for. BeanAdapter#get() is used by JSON#get() as it traverses the path.
