You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2005/11/10 14:55:12 UTC

[Db-derby Wiki] Update of "SharedComponentVersioningGuidelines" by KatheyMarsden

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by KatheyMarsden:
http://wiki.apache.org/db-derby/SharedComponentVersioningGuidelines

------------------------------------------------------------------------------
  
  == Mixed Version Support ==
  
- Two applications should be able to use one version of the Derby network client driver and a different version of the Derby embedded driver within the same Java VM without having to resort to creating specialized classloaders.  This is enabled by supporting forward compatibility as described below.  
+ Two applications should be able to use one version of the Derby network client driver and a different version of the Derby embedded driver within the same Java VM without having to resort to creating specialized classloaders.  Older versions of Derby jars will get their expected behavior in a mixed version environment regardless of jar ordering.  Newer versions
+ of Derby jars will get new behavior if the newer jar files are loaded first, and older behavior if the older jar files are loaded first.  This is enabled by supporting forward compatibility as described below.  
  
  == Guidelines for Forward Compatibility ==