Looks like I got it, last but not least due to the integration tests ;-) Regarding the integration tests (in PostServletVersionableTests.java) I would apply two "extract method" refactorings (createVersionedNode and createNonVersionedNode, which differ only in the fact that params is submitted or not which could yet be extracted), but that's just cosmetics...
Thx Clemens > -----Ursprüngliche Nachricht----- > Von: Justin Edelson [mailto:justinedel...@gmail.com] Im Auftrag von Justin > Edelson > Gesendet: Donnerstag, 9. Dezember 2010 00:52 > An: dev@sling.apache.org > Betreff: Re: SlingPOSTServlet : Auto Checkin Nodes > > > > On Dec 8, 2010, at 11:10 AM, Felix Meschberger <fmesc...@gmail.com> > wrote: > > > And: we must be very carefull to not create backwards compatibility > > issues around this automatic checkin/checkout. > > And that's what integration tests are for. > > Clemens - take a look at the integration tests. They should cover every > supported scenario. The only difference is that the integration tests use > parameters to specify the versioning configuration whereas I expect most > users to configure this stuff in ConfigAdmin. > > I can help you grok the test code if it isn't clear. > > Justin
