Craig- I believe this is the defined behavior for WebDAV, but I honestly have never looked it up.
Regards, Justin On Wed, Apr 4, 2012 at 5:16 PM, Craig S. Dickson <[email protected]>wrote: > Hi, > > I have the following configuration for the maven-sling-plugin in my > project - notice I have the usePut configuration parameter set to true as I > want to upload the bundle to a specific location in JCR tree. > > <plugin> > <groupId>org.apache.sling</groupId> > <artifactId>maven-sling-plugin</artifactId> > <executions> > <execution> > <id>install-bundle</id> > <goals> > <goal>install</goal> > </goals> > <configuration> > <slingUrl> > http://${cq.host}:${cq.port}</slingUrl> > > <slingUrlSuffix>/apps/cqblueprints/examples/apachecxf/install</slingUrlSuffix> > <user>${cq.user}</user> > <password>${cq.password}</password> > <usePut>true</usePut> > <failOnError>true</failOnError> > </configuration> > </execution> > </executions> > </plugin> > > This works as expected if the path that the slingUrlSuffix points to > already exists in the JCR tree. > > However if the path does not exist, the Maven build errors out with a > message like: > > > [ERROR] Failed to execute goal > org.apache.sling:maven-sling-plugin:2.1.0:install (install-bundle) on > project cqblueprints-examples-apachecxf-service: Installation on > http://localhost:4502/apps/cqblueprints/examples/apachecxf/install failed, > cause: Installation failed, cause: Conflict -> [Help 1] > > > I am wondering if this is the correct/desired behavior? Is PUT'ing to a > non-existent path not considered semantically correct from a REST > standpoint? Or, is this just a bug or missing feature? > > Thanks > > > > ========================== > Craig S. Dickson > Independent Consultant > http://craigsdickson.com > http://www.linkedin.com/in/craigsdickson > >
