No. Wicket's only usage of JSON** objects is at https://github.com/apache/wicket/blob/42bf896538953b302933362ce347e820a72ba40d/wicket-core/src/main/java/org/apache/wicket/ajax/AbstractDefaultAjaxBehavior.java#L202-L418 We do not want to add more complexity. I should have used String concatenation instead of introducing those classes in 6.0.0 :-/
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Jul 18, 2017 at 3:33 PM, Илья Нарыжный <phan...@ydn.ru> wrote: > Martin, > > Yes - I understand that. But in any case: is there any plans to make > serialization to JSON be compatible with wicket custom IPropertyLocator > feature? > > Ilia > --------------------------------------------- > Orienteer(http://orienteer.org) - open source Business Application > Platform > > On Tue, Jul 18, 2017 at 2:35 PM, Martin Grigorov <mgrigo...@apache.org> > wrote: > > > Hi, > > > > Actually the plan is (was) to get rid of Wicket's JSONObject. > > In Wicket 8.x there is no more such class. Now we use external dependency > > to OpenJson for Wicket's internal JSON needs. > > > > Martin Grigorov > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Tue, Jul 18, 2017 at 1:28 PM, Илья Нарыжный <phan...@ydn.ru> wrote: > > > > > Hello, > > > > > > Wicket has a great feature: ability to customize getting and setting > > > properties from/to an object. It's done through IPropertyLocator. > > > > > > But at the same time wicket's JSONObject implementation use just common > > > native properties of an object through Introspector. As a result: not > all > > > properties of customized object might be reflected in json. > > > > > > And plans to fix this unfair situation? > > > > > > Thanks, > > > > > > Ilia > > > --------------------------------------------- > > > Orienteer(http://orienteer.org) - open source Business Application > > > Platform > > > > > >
