I should have read both your email and the source code more carefully before responding =) I jumped to the conclusion Fedora was actually failing on modifies when it's actually just logging WARNings that it shouldn't.
DefaultDOManager had been revised just prior to the 3.3 release and looks like this crept in then. The warning shouldn't be a warning for valid internal dsLocations. I've opened http://www.fedora-commons.org/jira/browse/FCREPO-665 for this.
On 12 Mar 2010, at 6:04 PM, Edwin Shin wrote:
> DefaultDOManager is expecting a dsLocation that is prefixed with a recognizable URL scheme, specifically, your datastream's dsLocation isn't matching the following pattern string: "^\\w+:\\/.*$".
> If you're using Fedora's upload method, the dsLocation should begin with "uploaded://".
> The excess of messages is because DefaultDOManager is iterating through the datastreams and their revisions and evidently having the same issue with their dsLocations.
> There should be some more info in the logs to help indicate what's going on (the log level will need to be at INFO if it isn't already):
> 1) The log for the first add of managed datastream via upload method should begin with: "Getting managed datastream from internal uploaded location: XXX"
> 2) Followed by "Replaced managed datastream location with internal id: YYY"
> If you can report back with what XXX and YYY are, that should help run down the problem.
> On 12 Mar 2010, at 4:14 PM, Pierre-Yves JALLUD wrote:
>> Dear community,
>> I just installed FedoraCommons 3.3 and I'm making test on it. I'm using the same JAVA program to ingest data, but with the new version (the last version of FedoraCommons was 3.2.1), I have the following inconvenient message in the server/logs/fedora.log file:
>> WARN 2010-03-12 15:26:07.099 [http-8080-1] (DefaultDOManager) Inoperable DSLocation "MY_NS:MY_ID+DS1.0" given for MY_NS:MY_ID+DS1.0
>> The datstream is created correctly and I can download it. I create the datastream using the upload function so I'm using temporary DSLocation. The message is all the more strange that each time I create a new datastream in the same object, a new message per existing datastream is create. I.e. when I create the 5th datastream in a object, there'are 4 new warnings in my logs. The number of warning message is exponential! And some objects can have 1000 datastreams. The log file is exploding.
>> Does anyone knows what this message means?
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> Fedora-commons-users mailing list