blog/build-time-codegen/

[giscus[bot]]

blog/build-time-codegen/

An OpenAPI 3.x client generator that turns a spec into typed Codename One code, a JPA-shaped SQLite ORM, JAXB-shaped JSON / XML mappers, build-time SVG and Lottie transcoders, plus a declarative router and deep-link API. All ride on the same build-time codegen pipeline.

https://www.codenameone.com/blog/build-time-codegen/

[jsfan3]

Hi Shai,

Thank you for this article. I have a question about the new SQLite ORM support, because I’m trying to reconcile it with what I remember from previous Codename One discussions and blog posts.

My understanding over the years was that using SQLite directly in Codename One was generally something to avoid unless really necessary, mostly because of portability concerns and differences between the various ports. Because of that, I have usually implemented the internal databases of my apps using JSON-based storage instead.

In one particularly complex app, many years ago, I even built something somewhat similar to an ORM, with methods inspired by JPA/Hibernate, but implemented entirely on top of JSON. The goal was to maximize compatibility across Codename One ports and also make the saved data easy to inspect and modify from the simulator. That approach worked, but it also came with its own limitations and a lot of implementation complexity, especially since I built it by hand long before generative AI tools were available.

So I’m wondering: does this new SQLite ORM represent a change in the recommended approach? Would you now consider SQLite a safe/recommended option for local app persistence in Codename One, or is it still something you would suggest only for specific use cases? How would you compare this new ORM-based SQLite approach with a JSON-based persistence layer for internal app data?

[shai-almog]

Not so much, the recommendation still stands. I would still recommend using storage where possible but for complex data your options are rather limited to sqlite at which point you might as well use a more familiar/modern ORM tool.