JPOX 1.2.0-rc-1 (1.2 branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News JPOX 1.2.0-rc-1 (1.2 branch)
# 1  
Old 01-29-2008
JPOX 1.2.0-rc-1 (1.2 branch)

JPOX provides transparent persistence of Java objects. It fully complies with the JDO1.0/JDO2.0/JDO2.1 specifications, as well as implementing the JPA1 specification. It supports persistence to all of the major RDBMS on the market today, as well as DB4O. It allows querying using either JDOQL, SQL, or JPQL. It comes with its own byte-code enhancer. Its 1.1 release is Sun's "Reference Implementation" (RI) for JDO2.0, and its 1.2 release is the RI for JDO2.1. It is highly extensible using OSGi technology. License: The Apache License 2.0 Changes:
Support for JDOQL and JPQL subqueries has been added along with support for JPQL IN, ESCAPE, TRIM, CURRENT_DATE, CURRENT_TIME, and CURRENT_TIMESTAMP. JPOX extensions have been added to allow more control over generated SQL for problematic JDOQL queries. Several bugs have been fixed. Full compliance with JDO2.1 has been achieved.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ARCHPATH(1)                                                   General Commands Manual                                                  ARCHPATH(1)

NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches SYNOPSIS
archpath archpath branch archpath branch--version DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy. In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working copy. If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current archive and category and with the same version as the current working copy. This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com- mand like this: baz branch $(archpath) $(archpath new-feature) Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this: baz branch $(archpath) $(archpath releases--1.0) That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result. AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public License, version 2 or later. DEBIAN Debian Utilities ARCHPATH(1)