On 21/01/2013 15:04, Jan Bernhardt wrote:
But if I understand the description in SYNCOPE-275 correctly, it would cause
problems to switch to Spring 3.2 without removing all Spring MVC's
components. And of cause without Spring MVC's the old REST Interface could
not be used. Correct?
You are right: we should then open another issue "Remove Spring MVC" for
1.2.0 and make SYNCOPE-275 requiring this. Right?
+1
This way we can continue using old REST API for 1.1.0 release and then remove
Spring MVC in 1.2.0 release.
Fine: I'll proceed with opening such "Remove Spring MVC" issue for 1.2.0
alongside with the rest of this discussion.
I personally would also have no problem in removing Spring MVC for 1.1.0
release. But we don't have any pressure on this decision. We can get CXF
services working (for most parts) and then we still have the chance to decide
whether to switch now or later.
No, please don't forget people out there running 1.0.X: we must provide
at least a transitional version without forcing them to upgrade to the
new REST interface.
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
