Agreed.
I found the following article very useful (after reading it three
times):
http://www.xml.com/pub/a/2004/10/27/extend.html
The nice thing is that it describes compatible versioning so your
version upgrades don't ripple out all over.
Guy
On 23-apr-07, at 16:59, Dan Diephouse wrote:
No. Stepping away from CXF - there is no BEST versioning strategy
in my
mind. Only various bad ones :-)
Some various things I've come up with are:
- Namespace versioning: Create a new schema namespace and new set
of DTOs
for each new version
- Unified Domain Objects: In this scenario you try to map all the
different
versions of your XML data to one set of domain objects. Easier said
then
done... JiBX has some limited support for this, but not enough IMO
to really
be able to do it.
- Deployment versioning: Run multiple versions of your application
at the
same time and give each new version a new URL
- XSLT transformations
There are many sub categories, but I tend to stick to Namespace
versioning
as its relatively straightforward to do, although maintenance can
be a pain.
- Dan
On 4/23/07, Christopher Moesel <[EMAIL PROTECTED]> wrote:
Does CXF have a recommended service versioning strategy?
-Chris
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog
