Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Texo"

(Texo Components)
(Current Status)
Line 33: Line 33:
  
 
Currently (January 2010) the following has been implemented:
 
Currently (January 2010) the following has been implemented:
* true pojo generation
+
* pojo generation with runtime model
 
* Featuremap support
 
* Featuremap support
 
* XML Serialization  
 
* XML Serialization  
Line 39: Line 39:
 
We are currently working on:
 
We are currently working on:
 
* Code generation: EOperation support, support for unsettable
 
* Code generation: EOperation support, support for unsettable
 +
* Support template overriding
 
* Model-driven JSON service
 
* Model-driven JSON service
 
* some initial tool support for creating annotated models
 
* some initial tool support for creating annotated models

Revision as of 17:39, 30 January 2010

Introduction

The goal of the proposed Texo project is to provide model and template driven development technology for web application development projects. Texo will be based on and use components currently present in the Eclipse Modeling Framework (EMF) and Eclipse Modeling Framework Technology (EMFT) projects. Texo is a proposed open source component in the Eclipse Modeling Framework Technology (EMFT) project.

The original project proposal can be found here.

Annotated Models

Texo Components

The initial release of Texo will consist of several components:

  • Code generation for server oriented applications with support for in-model and in-source annotations, manual code changes are supported in the EMF way. Templates can be added/overridden by users.
  • XML Serialization
  • Tool support for creating annotated models
  • JPA annotation generation
  • Model-driven JSON serialization support

Next phase:

  • Add more annotation models (for example: Hibernate Search, jaxb, Seam, EJB3)
  • The next phase will focus on generating User Interface code for GWT or RIA frameworks such as Smartclient or Extjs.
  • Test case/class generation

Documentation

Developing

Developer information (CVS, how to setup a developers environment) is described on the Developers page.

Texo and EMF

The

Current Status

Currently (January 2010) the following has been implemented:

  • pojo generation with runtime model
  • Featuremap support
  • XML Serialization

We are currently working on:

  • Code generation: EOperation support, support for unsettable
  • Support template overriding
  • Model-driven JSON service
  • some initial tool support for creating annotated models
  • JAP Annotation model

In the next phase support for Generic/Parameterized types will be added.

Back to the top