In this podcast, JSFCentral editor-in-chief Kito D. Mann talks with Daniel Lichtenberger about [fleXive] and its use of JSF. Daniel is a senior software engineer at the Vienna, Austria based software development company UCS -- Unique Computing Solutions. He develops enterprise software for the Java EE platform and has a keen interest in web technologies and agile development. This interview was recorded in April of 2009 at JSFDays in Vienna, Austria. Here is an excerpt:
Daniel: fleXive was created from our experience in enterprise solutions with web front ends that use some kind of dynamic database as a back end, where you want to define your own types of data -- for example documents or personal data. You have to manage this, you have to somehow always write the front end for it, and you always have to add Enterprise features like security to control who can edit which fields. You have to add things like versioning or multilingual content, especially for web front ends -- this is a very common requirement. This was the setting that fleXive originated from. We wanted to create a solution that is usable to create applications in this area rapidly without having to reinvent the same things over and over again. We started to build a content repository with a set of Java Enterprise APIs. You can use these APIs to define you data types, to create structures that are then used for storing the data from the application. You can create the data, and you get all these features like versioning and so on for free basically. Then you usually have to write some kind of web front end, so what we decided to do was not to create another web framework, or another kind of full blown stack, to avoid being locked into the specific solution just because you want some features of fleXive. We decided to create a JSF component suite which offers you components for displaying data from the repository or for displaying edit fields. You can conveniently interact with the repository or create programs to interact with it.
Kito: So when you say content repository, that brings up different ideas. One thing might be the Java content repository API, or big systems like Documentum or some of these newer content management systems like Alfresco, etc. So where does the fleXive content repository fit into that landscape?