News

News 14-Jun-09: A new snapshot release was made available. This one changed only the Eclipse's plugin. Two bugs was fixed. More here.

News 29-Apr-09: Floggy reached 10,000 downloads today it is another remarkable mark! Thank you Floggy community!

05-Apr-09: A snapshot release (alpha) of 1.3.0 was made available, please test it and give us a feedback. Further information about the changes here.

22-Feb-09: The documentation turned into a little out of date since the last release but it is not any more! Check it on Getting Started, FAQ, Eclipse and Weaver sections.

29-Jan-09: Floggy 1.2.0 was released. You can get further information about the changes here. Enjoy!

29-Jan-09: If you couldn't went to the M3DD Conference see Floggy live, now you can! Watch this.

15-Jan-09: Floggy will be presented at Java Mobile, Media & Embedded Developer Days Conference our first international event. PresentationVideo.

A complete list of news is available here. Stay tuned! Subscribe our RSS feed.RSS

Welcome to Floggy

Floggy is a free object persistence frameworkfor J2ME/MIDP applications. The main goal of this framework is to abstract the data persistence details from the developer, reducing the development and maintenance effort. How? Check the examples in the Getting Started section.

Floggy is licensed under the Apache License, version 2.0. That means that you can use Floggy in open source and commercial projects.

Now you don't need to write thousands of lines of persistence code anymore. Floggy will do the dirty work for you!

Why Floggy?

As J2ME developers we couldn't handle anymore the idea of writing so many code lines to persist so few attributes. For each class we want to persist we had to developed the source code to transform an object into a byte array and vice-versa. We have tried to find free persistence frameworks for this technology on the internet, but we couldn't find one that fitted our needs. So, we have decided to start our own project.

Architecture

Floggy is composed by 2 modules:

  • Framework: Responsible for supplying persistence methods such as saving, removing and finding objects through a small API (11k) that must be attached to your application.
  • Weaver: Responsible for analyzing, generating and weaving bytecode into the persistable classes.

The following process describes how Floggy works:

Before you start using Floggy, we strongly recommend the reading of the getting started section.