The version update was needed to remap renamed callbacks. So if you
upgrade a schema with "prePersist" callback, you'll see more changes.
I mentioned this on the list before - since there's generally no
direct correspondence between Cayenne runtime version and project
schema version, I figured I'd come up with some numbering scheme that
can't be mistaken for a Cayenne runtime version. So 3.0.0.1 is pretty
random based on the fact that we may have 3.0.1 Cayenne release, but
not a 3.0.0.1.
Also this does not affect the XSD schema version. I simply updated the
existing schema. I think of the schema as a Java class - during 3.0
development cycle we are allowed to change it without changing the
version.
It does look counterintuitive somewhat, but allows us to modify the
schema and implement automated XML upgrades between the milestone
releases.
Andrus
On Oct 28, 2009, at 4:03 PM, Aristedes Maniatis wrote:
On 26/10/09 3:49 AM, Andrus Adamchik wrote:
Release artifacts are posted here:
http://people.apache.org/~aadamchik/release/3.0B1/
Please evaluate and cast your votes.
One smallish issue. When it opened my model, it 'upgraded' it from
version 3.0 to 3.0.0.1. What is the versioning scheme we are using
here? Why 3.0.0.1? How does that relate to the XSD schema which is
currently set to version 3.0. Here is the only change made by the
modeller when opening a model previously saved with M6...
<data-map xmlns="http://cayenne.apache.org/schema/3.0/modelMap";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
- xsi:schemaLocation="http://cayenne.apache.org/schema/3.0/modelMap http://cayenne.apache.org/schema/3.0/modelMap
"
- project-version="3.0">
+ xsi:schemaLocation="http://cayenne.apache.org/schema/3.0/modelMap http://cayenne.apache.org/schema/3.0/modelMap.xsd
"
+ project-version="3.0.0.1">
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
