empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Venditti (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] Updated: (EMPIREDB-52) CodeGenerator project setup
Date Sat, 14 Nov 2009 14:18:39 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Venditti updated EMPIREDB-52:
--------------------------------------

    Attachment: codegen-0.4.patch

Hi there,

I have created a new patch that will get rid of the additional Database, Table and Column
bean classes.
The codegen now uses the empire DBDatabase, DBTable and DBColumn classes instead.

The patch contains the following changes:
 modifications:
  - CodeGen.java
  - CodeGenConfig.java
  - config.xml
  - Database.vm
  - Record.vm
  - Table.vm

deletions:
  - package org.apache.empire.db.codegen.types
  - StringUtils.java  // partly moved to ParserUtil.java

additions:
  - CodeGenParser.java  // Used to create a empty DBDatabase and to populate that
  - ParserUtil.java              // Used by the velocity templates to get strings like accessor
name, mutator name, table class name, record class name ...

> CodeGenerator project setup
> ---------------------------
>
>                 Key: EMPIREDB-52
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-52
>             Project: Empire-DB
>          Issue Type: New Feature
>          Components: CodeGenerator
>    Affects Versions: empire-db-2.0.6-incubating
>            Reporter: Rainer Döbele
>             Fix For: empire-db-2.0.6-incubating
>
>         Attachments: codegen-0.4.patch, codegen.0.3.patch
>
>
> The empire-db code generator is a new subproject which should be capable of generating
source code classes from an existing database.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message