> I personally would like to keep the dependency out if it doesn't require too > much copying of code.
Me too, and it would be a simple immutable data object with three properties. Internally I plan on using the webdav Lock class. With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Mon, Nov 10, 2008 at 3:13 PM, Bart van der Schans <[EMAIL PROTECTED]> wrote: > On 10-11-2008 15:06, Nick Stolwijk wrote: >> >> Hi Wander, >> >>> * Is it necessary to add a new Lock class? isn't it possible to reuse the >>> existing org.apache.webdav.lib.Lock? >> >> At this moment the WebdavService interface has no external >> dependencies. To keep it this way I proposed to add the Lock class. It >> external dependencies on the interface are no problem, we could use >> the org.apache.webdav.lib.Lock. This means that all clients of the >> WebdavRepository must have the webdav package on its compile time >> classpath and thus adding a dependency. > > > Regards, > Bart > > -- > Hippo B.V. - Amsterdam > Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466 > > Hippo USA Inc. - San Francisco > 101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646 > ----------------------------------------------------------------- > http://www.onehippo.com - [EMAIL PROTECTED] > ----------------------------------------------------------------- > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
