This is a corrective release that fixes a serious issue in $entity.insert along with
a few minor bugfixes, some source refactoring and some more test cases.
Velosurf 2.0 has just been released.
It is a major upgrade release.
Main additions are :
- data validation constraints
- localization tool
- authentication tool
- test cases
If you upgrade from 1.4.x, be sure to upgrade velocity-tools to 1.3 (or 1.3-dev if not yet released) and to change velosurf.tools.VelosurfTool to velosurf.web.VelosurfTool in
toolbox.xml.
Velosurf 1.4.2 has just been released. It is a bug fix release that fixes the connection recovery process.
I'm pleased to anounce the release of Velosurf 1.4
About : Velosurf is a thin but efficient database mapping tool meant to
be used with Jakarta Velocity. Its aim is to generate a set of context
variables that automatically map database tables and relationships,
without the need for any recomplation.
Changes : The main purpose of this release is to allow the use of POJOs (Plain Old Java Objects) as row instances.
This release adds transparent encryption of database IDs (so that they can appear in URLs) along with automatic fetching of instances referenced by their ID in HTTP query parameters. Also, some database-specific corrections have been made for Sybase, Oracle and PostgreSQL, and a complete example webapp and a FAQ have been added. There is now a standalone version of the tool, meant to be used outside web-apps.
Velosurf is a database access tool for the Velocity template engine. It is meant for ease-of-use, genericity and efficiency.
Velosurf main features are :
- dynamic mapping : no need to recompile on any database change
- sql queries appear as standard VTL properties
easy VTL grammar
- automatic connection recovery
- statements pools
- very simple xml configuration file
- automatic reverse engeenering of database schema
- natural type mapping
- concurrent accesses
- transactions
- soft caching
- custom overloading of mapping java objects
...
Velosurf can be used as a standard Velocity tool, like in frameworks that use the Velocity Tools subproject (a great architectural component allowing re-usable tools to be easily plugged in web-applications).... read more
Velosurf is a database access tool for the Jakarta Velocity template engine.
The main goal of Velosurf is to avoid the pain of rewriting specific database mapping layers in java for each project involving velocity and database entities that template writers have to deal with.
Velosurf main features are :
- db access from VTL as from java
- easy VTL grammar
- soft caching
- automatic connection recovery
- statements pools
- very simple xml configuration file
- automatic reverse engeenering of schema
- natural type mapping
- concurrent accesses
... ... read more
Velosurf is a database access tool for the Velocity template engine.
The main goal of Velosurf is to avoid the pain of rewriting specific database mapping layers in java for each project involving velocity and database entities that template writers have to deal with.
Velosurf main features are :
- db access from VTL as from java
- easy VTL grammar
- automatic connection recovery
- statements pools
- very simple xml configuration file
- automatic reverse engeenering of schema
- natural type mapping
- concurrent accesses
...... read more
Velosurf is a thin but efficient database access layer for Jakarta Velocity
[0.4] This release adds several significant improvements and bug corrections.
Velosurf is a database abstraction layer for Jakarta Velocity: Velosurf is meant for ease of use, genericity and efficiency. It's purpose is to provide an access to entities and relationships from inside velocity templates with no specific java code.