Yeah... Previously existing API that was not marked for deprecation
should remain fairly stable. Runtime, while undergoing a number of
changes, is still production quality. I am using it on a very active
live site...
Essentially the biggest risk is that the _new_ API introduced during
3.0 development cycle is not extensively tested just yet, and will be
changing. So upgrades between milestones may not be just jar
replacement. Here is one example - lifecycle callbacks. M3 will
introduce CayenneModeler support for callbacks for the first time, but
will also have changes to the manual callback API (using enums instead
of int callback types).
Andrus
On Nov 27, 2007, at 12:04 AM, Tore Halset wrote:
Hello.
We are using M2 in production in a pretty busy system. We use only
the "classic cayenne" stuff, but it is working very well.
Regards,
- Tore.
On Nov 26, 2007, at 22:56, Malcolm Edgar wrote:
Hi All,
I would like to know peoples experience in using Cayenne 3.0M2 for
Production applications, or is Cayenne 2.0.x still the recommended
release.
I am looking a upgrading our Cayenne 1.2.x applications. By the
way I like
the free search field in the Cayenne modeler.
regards Malcolm Edgar
