Skip to content
Martin Goellnitz edited this page Dec 5, 2015 · 2 revisions

Tangra Modules

A short description of the modules resembling the tangram artifacts.

Development support

Framework

  • core The core obviously presenting templates as viewing methods on Java (pojo) models, code resources like css, JavaScript, Groovy, Apache Velocity in the data repository for dynamic web development...

Data Model

  • nucleus Java Data Objects (JDO) based implementation of a model layer using the DataNucleus Access Plattform.
  • jpa model layer making it possible to define model class with the Java Persistence API (JPA) using the DataNucleus Access Plattform, EclipseLink, Hibernate, or OpenJPA.
  • ebean implementation of a model layer using the EBean ORM.
  • coma read only CoreMedia Adapter model layer accessing CoreMedia CMS (5.2 and up) content server databases directly and use them as a base for the other layers of tangram.
  • mutable abstract base module for all model layers dealing with mutable models, which now means any of them except the CoreMedia Adapter coma.
  • jdo abstract base module for any implemetation of the Java Data Objects (JDO) API. Used by the Google App Engine (gae) module of Tangram 1.0 and the DataNucleus Access Plattform integration module nucleus.

Application Setup through Dependency Injection

  • dinistiq Wire the whole application using tangram together by means of the very limited dependency injection library dinistiq
  • spring Implementation of the wireup of tangram based applications with the springframework and several other aspects of web application done in Java with that framework.
  • guicy Google Guice can be used as a dependency injection option to glue the application together from the different artifacts. To avoid hard wiring of too many aspects in Java but still to provide reasonable default setup like with the springframework and dinistiq, a configuration layer with Groovy codes and some properties files has been integrated resulting in the name 'guicy' instead of just 'guice'.
  • servlet Since the only common API for web applications done in Java still is the Servlet API, we provide an alternative to the springframework specific solutions in this module. It is therefore used in the guicy module and the dinistiq module.

Additional Modules

  • editor a more or less generic editor for any object manageable through the mutable content object layers (s.a.). A very simply implementation, yet extendable through the means of the framework itself.

  • ftp Gateway module to be able to access the (mutable) codes in the data repository of the data model layers with FTP access. Its not a generic access of any content, but meant as an integration tool with the many IDEs supporting syncing of code with remote ftp sites.

Clone this wiki locally