License     Codehaus     OpenEJB     OpenJMS     OpenORB     Tyrex     
 

Main
   Home
   About
   Features
   Download
   API
   Schema
   Mailing Lists
   SVN/JIRA
   Contributing
   Support
   RSS news feed
   Recent changes

XML
   Using XML
   Source Generator
   Schema Support
   XML Mapping
   XML FAQ
   XML HOW-TOs
   Custom Handlers

JDO
   Introduction
   Using JDO
   JDO Config
   Types
   JDO Mapping
   JDO FAQ
   JDO Examples
   JDO HOW-TOs
   Other Features
   JDO sample JAR

Advanced JDO
   Caching
   OQL
   Trans. & Locks
   Design
   KeyGen
   Long Trans.
   Nested Attrs.
   Pooling Examples
   LOBs
   Best practice

More
   Presentations
   The Examples
   3rd Party Tools
   JDO Tests
   XML Tests
   Configuration
   Tips & Tricks
   Full JavaDoc
   CastorWiki
  
  

About
   License
   Contributors
   Marketplace
   Status, Todo
   Changelog
   Library
   Contact
   Project Name

  



The Castor Project


Quick Description
Recent documentation changes
News


Quick Description

Castor is an Open Source data binding framework for Java[tm]. It's the shortest path between Java objects, XML documents and relational tables. Castor provides Java-to-XML binding, Java-to-SQL persistence, and more.

Recent documentation changes

Please check here for any information related to changes of the HTML documentation.

News


Castor 1.0.1 released

I've placed a copy of Castor 1.0.1 at the Codehaus.

This is mainly a maintenance release. For details about features added and bugs fixed, please have a look at the release notes.


Submitted by Werner Guttmann, on Jun 08 2006 @ 20:22:21

Mailing list subscriptions

Can I please ask everybody to check her (his) mailing list subscriptions at http://xircles.codehaus.org. It looks like, due to the Codehaus problems a few weeks ago, we might have lost some (though not many) mailing list subscriptions.

We do apologize for any inconvenience caused ....


Submitted by Werner Guttmann, on Jun 02 2006 @ 20:07:43

Jira and notifications

This is a short message for those who have created Jira issues in the past two or three months or so, or have commented upon existing issues.

It looks like during some Jira upgrade a few months ago, a couple of Jira settings got disabled. As a result, the original reporter of a Jira issue did not get notified about any changes to the issue (incl. e.g. state changes, comments, questions, etc.).

I have now reconfigured the notification scheme attached to the Castor Jira instance so that the following entities will receive notification emails upon a change to an issue:

- The SCM mailing list (somewhat high traffic)
- The reporter of the issue
- The assignee of the issue
- All watchers.

I hope that this will shorten feedback loops substantially in the future, and I would like to ask people who created issues in the last two or three months to 'manually' scan the issues they created for updates et alias.


Submitted by Werner Guttmann, on May 30 2006 @ 20:07:43

Castor up again ...

As you might (not) have noticed, all the project-related infrastructure (mailing lists, SVN repository, HTML docs, binaries etc.) has been off-line due to a hard disk failure on one of the Codehaus servers. As a result of a lot of dedication from the Codehaus folks, we are as of now in a position to re-start life as usual.

Please note that there's still a few minor issues related to things being setup and/or re-instated as we speak. As such, we won't be updating some HTML docs immediately, as a few things have not come to reach final stability yet.

Please watch this page and the mailing list(s) for more updates.


Submitted by Werner Guttmann, on May 23 2006 @ 20:07:43

Castor and Google Summer of Code

We are proud to participate in the Summer of Code initiative sponsored by Google, and you are invited to join in the fun.

At Codehaus, you'll find some suggestions we find suitable for the program, and per definition we would be glad to support a few projects.

Please understand, though, that mentoring capacities will be limited, though we will try to dedicate as much time as possible to the suggested projects. That implies that we depend on your dedication during the preparation of the detailed specification and description of the outcome.

The timeframe for applications is May 1 - May 8. So have a look at the projects at offer, before you are sign up to the program and apply as a student to be mentored by us.


Submitted by Werner Guttmann, on May 05 2006 @ 20:07:43

New source repository

On April 14. 2006 we have migrated Castor source repository from CVS to SVN. At the moment we still have read only access to CVS but this does not reflect commits to SVN after the migration. The read only access to CVS is intended for you to create patches of your current work and move it over to SVN. Be aware that we will switch off CVS soon. For details about SVN access please have a look at: SVN/JIRA.

Submitted by Ralf Joachim, on Apr 16 2006 @ 13:07:43

Castor 1.0 (final) released

I've placed a copy of the final Castor 1.0 release at the Codehaus.

For details about features added and bugs fixed, please have a look at the release notes.


Submitted by Werner Guttmann, on Apr 06 2006 @ 23:22:21

Castor 1.0M4 released

I've placed a copy of the Castor 1.0M4 release at the Codehaus.

This is the fourth (and last) milestone build for the upcoming 1.0 release. For details about the features added and the bugs fixed, please have a look at the release notes. Please note that we are imposing a feature/code freeze in preparation for the final 1.0 release, which is currently scheduled for April 6, 2006.


Submitted by Werner Guttmann, on Mar 23 2006 @ 23:22:21

More...

 
   
  
   
 


Copyright © 1999-2005 ExoLab Group, Intalio Inc., and Contributors. All rights reserved.
 
Java, EJB, JDBC, JNDI, JTA, Sun, Sun Microsystems are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. XML, XML Schema, XSLT and related standards are trademarks or registered trademarks of MIT, INRIA, Keio or others, and a product of the World Wide Web Consortium. All other product names mentioned herein are trademarks of their respective owners.