Bug 780001 (SOA-2361) - RepositorySourceException thrown when creating file using WebDav client and FileSystem connector
Summary: RepositorySourceException thrown when creating file using WebDav client and F...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2361
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-29 14:15 UTC by Boris Belovic
Modified: 2010-11-25 09:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-25 09:56:46 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2361 0 None None None Never

Description Boris Belovic 2010-09-29 14:15:58 UTC
project_key: SOA

When creating new file in Modeshape repository (configured to use Filesystem connector) using a WebDav client, there is a RepositorySourceException thrown. I tried WebDav methods provided in Jackrabbit Webdav package and also WebDav methods from Sardine framework, both resulted in org.modeshape.graph.connector.RepositorySourceException: Attempt to set or update invalid property names: [jcr:encoding]

Here is a code snippet which uses PutMethod class from Jackrabbits's WebDav package:

try {
DavMethodBase put = new PutMethod("http://127.0.0.1:8080/modeshape-webdav/file6.txt");
initClient().executeMethod(put);

System.out
.println(put.getStatusCode() + " " + put.getStatusText());

} catch (Exception e)
{
System.out.println(e.getCause());
e.printStackTrace();
}

and here's a stacktrace SOA-P's console:

16:07:57,941 ERROR [STDERR] org.modeshape.graph.connector.RepositorySourceException: Attempt to set or update invalid property names: [jcr:encoding]
16:07:57,942 ERROR [STDERR] at org.modeshape.connector.filesystem.FileSystemSource$StandardPropertiesFactory.ensureValidProperties(FileSystemSource.java:698)
16:07:57,942 ERROR [STDERR] at org.modeshape.connector.filesystem.FileSystemSource$StandardPropertiesFactory.recordResourceProperties(FileSystemSource.java:669)
16:07:57,942 ERROR [STDERR] at org.modeshape.connector.filesystem.FileSystemWorkspace.putNode(FileSystemWorkspace.java:235)
16:07:57,942 ERROR [STDERR] at org.modeshape.graph.connector.base.PathWorkspace$PutCommand.apply(PathWorkspace.java:258)
16:07:57,943 ERROR [STDERR] at org.modeshape.graph.connector.base.PathWorkspace.commit(PathWorkspace.java:192)
16:07:57,943 ERROR [STDERR] at org.modeshape.graph.connector.base.PathTransaction$WorkspaceChanges.commit(PathTransaction.java:830)
16:07:57,943 ERROR [STDERR] at org.modeshape.graph.connector.base.PathTransaction.commit(PathTransaction.java:721)
16:07:57,943 ERROR [STDERR] at org.modeshape.graph.connector.base.Connection.execute(Connection.java:130)
16:07:57,943 ERROR [STDERR] at org.modeshape.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:1129)
16:07:57,943 ERROR [STDERR] at org.modeshape.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193)
16:07:57,943 ERROR [STDERR] at org.modeshape.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:183)
16:07:57,944 ERROR [STDERR] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
16:07:57,944 ERROR [STDERR] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
16:07:57,944 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
16:07:57,944 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
16:07:57,944 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)

Comment 1 Boris Belovic 2010-09-29 14:16:23 UTC
Link: Added: This issue is related to MODE-920


Comment 2 Van Halbert 2010-10-01 15:56:40 UTC
ModeShape has fixed the issue and checked the changes into the 2.2.x branch, for which will be in the next pull for a build.

Comment 3 Boris Belovic 2010-11-25 09:56:46 UTC
Verified in SOA-P ER4 build, with FS connector no exception has been thrown during file creation. Put method was successful in creating a file, response returned 201 Created code.


Note You need to log in before you can comment on or make changes to this bug.