Hi Æde,

Currently there's no support for the MOVE method in the Java Adapter. Although it wouldn't be too hard to add the method you have to keep in mind the moving documents that are used by the CMS is considered a workflow step. Moving documents directly in the repository can break the workflow on the document.

Regards,
Bart


Æde van der Weij wrote:
Hello all,

I need to move resources from one location to another with the Hippo
Repository Java Adapter. I am using the CMSService that basically wraps
the WebdavService. The MOVE method does not seem to be supported
(neither does the COPY method).

Because this seems basic functionality I was wondering if I was over
looking things? Also because the repository supports the MOVE method.

Of course I can PUT and DELETE but than I have to implemented my own
atomic transaction whereas the repository would do this for me with the
MOVE method.

My question basically is how I should move a resource with the Hippo
Repository Java Adapter.

Any pointers anyone?

-- Æde

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/********************************************
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



--
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

Reply via email to