Thomas Kappler wrote: > > On 05/21/10 14:57, napple fabble wrote: >> >> We're starting a new project and thinking about using Wicket for >> presentation >> layer. >> >> One concern is about backwards compatibility and support. I understand >> 1.5 >> is coming and in not fully backwards compatible. >> >> The concerns: >> >> If we start with wicket 1.4.8, a few years from now all development is >> done >> to 1.5.x and no one cares about boring old 1.4 anymore. > > No different from any other web framework, or any software for that > matter. Do you have a specific concern with Wicket in that regard? > >
First, thanks for all the replies. I have no intention of bad-mouthing wicket. My questions are just related to management of project risks. The main alternative we're comparing wicket to is using JSF. The "vendor lockin" problem is less of a risk there. If we implement our app with JSF2.0, we're pretty much guaranteed support and bug fixes for that for 10 years by the commercial app server vendors. If we decide to use standards-based solution there's no risk of, for example, wicket suddenly going "out of fashion" and support and activity dying. Of course the same risk does exist if we compare to any other OS web framework. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-vendor-lockin-and-backwards-compatibility-1-4-1-5-tp2226109p2229621.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
