Joerg Heinicke wrote:
You need to have the following in mind: Somebody wants to upgrade from
Cocoon 2.2.3 to 2.2.4. In that step to one of the schemas an additional
and optional attribute was added (like that case in Spring's AOP
schema). In theory the jars would be a drop-in replacement. With
increasing the version number of the schema you have to adapt all your
references to the new version just to get your app working again. Or
you'd need to hold all versions probably in use in your local XML
catalogue or access them remotely. Since Spring has the schemas on the
class path, they are just replaced with the jars. Despite the vagueness
nobody actually needs to care about the schema version. For that reason
I'd probably go with a constant number as long as it is backwards
compatible. And it should be for on particular minor level.
I agree with Jörg.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
