On Thu, May 24, 2012 at 6:09 PM, Thomas Mortagne <[email protected]> wrote: > On Thu, May 24, 2012 at 5:52 PM, sasinda rukshan > <[email protected]> wrote: >> Hi all, >> I am starting this thread for my XWiki Android Platform Project. >> >> Please check whether following are OK. >> [1] INFO >> I tried to start my new modules with the de.akquinet.android.archetypes: >> android-quickstart:1.0.8. (added eclipse plugins m2e, >> m2e-android[a.k.a *Android >> Configurator* ]). But this seems buggy in eclipse. >> Any way the earlier project has not followed the above archtype either. So >> I am going to write pom.xml manually for my each module. >> >> [2] ADVICE NEEDED >> xwiki-rest-model module contains 2 submodules >> |-- xwiki-rest-model-gson ( gson should be corrected to json) > > No the g is not a mistake, it's a model to be used with the gson > library (http://code.google.com/p/google-gson/). See > http://extensions.xwiki.org/xwiki/bin/view/Extension/Google+Android+Client#HXWikiAndroidDevelopmentAPIsandResources. > >> |-- xwiki-rest-model-simplexml >> I think the xwiki-rest-model-gson is redundant. The classes >> in xwiki-rest-model-simplexml is added with simple xml annotations, >> otherwise both modules have same classes. There is no problem with the >> added annotations for using the same model objects for Json REST web >> services. And I intend to add my JPA (ORMLite library for persistence) >> annotations on top of it. >> Shall I re-factor them to a single module xwiki-rest-model. > > No keep them separated, the idea is that both are useful tool to be > used by someone else that might be moved to xwiki-platform at some > point along with the current xwiki-rest-model (to be renamed to > xwiki-rest-model-jaxb). > > Chamika initially started with gson and since XWiki REST JSON > representation had some limitation he moved to XML representation. > Maybe at some point Android will have native support for jaxb which > would obviously be the easier for us (embedding jaxb is not an option > in mobile world where size it still pretty important especially on > phones). Maybe it's already the case on most recent versions like 4.0 > I don't know.
There's also Jackson that could be tried for JSON deserialization, if said limitations are actually GSON limitations. Having full JAXB support sound a bit overweight for such an "embedded API", even if one day it is natively supported by Android. What's important is to have an easy and fast deserialization, IMO. The only advantage I can see of going JAXB would be in re-using the exact representations and body readers/writers from XWiki core. But you probably don't even want to do that since it would mean dragging XWiki core with you :) Jerome > >> >> [3] INFO >> I had to change some pom.xml s. As the current project at: >> https://github.com/xwiki-contrib/android-client.git does not build. Error >> with parent pom.xml coordinates. > > You probably did not setup you maven install properly since what's on > https://github.com/xwiki-contrib/android-client.git build perfectly as > you can see on http://ci.xwiki.org/view/All/job/xwiki-android-client/ > which run a build every time something changes on the git repository.. > You should look at > http://dev.xwiki.org/xwiki/bin/view/Community/Building. > >> >> >> Thank you >> Best Regards. >> Sasinda Rukshan >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs > > > > -- > Thomas Mortagne > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs -- Jérôme Velociter Winesquare http://www.winesquare.net/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
