Jease (www.jease.org), a content management framework based on the best in open source Java technologies, has added support for the Perst object-oriented, open source embedded database system from McObject. When used with Jease, Perst becomes the persistence engine for highly customized, content- and database-driven Web applications that leverage the productivity and efficiency of working with “plain old Java objects” (POJOs). Jease (the name combines “Java” and “ease”) provides building blocks for developers with even a little Java experience to assemble Web applications tailored to specific needs. The goal of Jease is to offer a flexible content management framework rather than a full-blown content management system, said Jease founder and project leader Maik Jablonski. “Jease makes it very easy to create custom content structures -- such as FAQs or pages for a particular Web site section-- within minutes. The user creates a POJO and ‘programmatically declares’ that POJO's appropriate content editor (the form used to create and edit data for the structure). Just a few lines of code and you're done,” Jablonski said. “Jease handles behind-the-scenes considerations like persistence (thanks to the object-oriented database), a full Ajax-driven user-interface with drag/drop, and high-performance full-text-search.” To accomplish this, Jease is built on top of some of the most powerful and widely used open source technologies in the Java community:

• Object-oriented database technology to provide persistence.
• Lucene as high performance full-text indexing and search technology.
• ZK as a component- & event-driven Ajax-based Web framework.

Perst features such as automatic schema evolution, support for “foreign objects” (Java classes without any dependency on the database), and seamless handling of object arrays make the embedded database a natural fit for Jease, Jablonski said. “Perst hides all the complexity from the application developer when working with a very complex object-graph like the node-hierarchy used in Jease,” he said. “Perst worked right out of the box, which is very impressive. It seems to be one of the most advanced open source, object-oriented databases in the Java world.” Jablonski added that he hopes working with Jease will lead more developers to recognize the benefits of object-oriented database systems. “Productivity and efficiency are what count. When working on a complex domain, you really want to use a domain model based on the principles of object-orientation. That’s why object-relational-mapping is a must for complex projects involving relational databases. But mapping relational tables to objects comes with additional costs, and seems overall a little bit antiquated.” “Using relational technology with an object-relational mapping makes me less productive as a developer: I need to maintain the POJO, the mapping and the database schema. When using an object database like Perst I just have to maintain the POJO, the database take cares of all the rest,” he said. “Using relational technology with an object-relational mapping also makes my applications less efficient because of the costs of the additional (and complex) mapping layer. Additionally, nested hierarchies with node-based inheritance (like the model used in Jease) are nearly a non-starter for relational technology. I don't want to know how many complex joins are needed for even the simplest query,” Jablonski said. See the full announcement at http://www.mcobject.com/january5/2010.

The ZK framework is pretty powerful. I've used it on smaller apps. There was a recent link to an article on TSS about performance monitoring - using ZK(the article came from the ZK site). That is the once concern I guess with ZK, given the server-centric architecture, is performance when a large number of users involved. Have you done much in the way of performance testing?

Have you done much in the way of performance testing?

Jease uses ZK as frontend for the internal CMS-Application and not for rendering the public web-site. Although ZK consumes more ressources than traditional web-frameworks, it scales pretty well for typical "Jease-use-cases": thinking of a few hundred users who maintain the content of a web-site. Rendering the public site via JSPs (I like JSPs, but you're free to use any other technology) allows to serve several thousand concurrent requests per second from a single machine easliy... throwing in some more Apaches or Squids as additional proxies will do the rest.

Thank you for registering at MyBangalore.

Discount Vouchersdata recovery brighton