On 10/18/2011 09:50 AM, Jurij Čakardič wrote:
> I did some research by enabling logging on the Subversion server, when the
> developer connects to the SVN server through Oracle JDeveloper a request is
> formed incorrectly or at least in a strange manner:
>
> 2060 2011-10-18T13:03:12.893457Z 172.16.201.189 markoj INsurance2 open 2
> cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops)
> /javaProjekti/In2ADF1 - -
> 2060 2011-10-18T13:03:12.902529Z 172.16.201.189 markoj INsurance2 get-latest-rev
> 2060 2011-10-18T13:03:12.903482Z 172.16.201.189 markoj INsurance2 stat
> /javaProjekti/In2ADF1/javaProjekti/In2ADF1_at_2729
>
> Notice the path concatenation in the last request, the correct path is just
> "/javaProjekti/In2ADF1". I guess this is an error that occurs either in the
> SVN client or Oracle JDeveloper.
>
> The error is evidently not in the Subversion server but in either the client
> or Oracle JDeveloper.
Yeah, the URL_at_REVISION syntax is a meaningful construct at the Subversion
client level, but means nothing when you start looking at lower layers (such
as the repository access / networking layer). It appears that some bit of
code is trying to use URL_at_REVISION as an explicit URL, rather than
interpreting it as a URL and revision pair.
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2011-10-18 16:11:32 CEST