And further to that (having tripped over this myself about five minutes
ago) - the url property in that file doesn't carry over to the
collection.url and servicedocument.url properties, so if you use a non
standard "url" value then (as stated in the comments of the file) you'll
have to adjust those two properties as well.

cheers,
Andrea

On Thu, 23 Aug 2018 at 09:23, Andrea Schweer <andrea.schw...@waikato.ac.nz>
wrote:

> Hi,
>
> check what you have configured as the service document URL - probably in
> [dspace]/config/modules/swordv2-server.cfg. It's the first property in that
> file "url". The default is {dspace.url}/swordv2 and the base URL you use in
> your sword deposit must match that exactly.
>
> cheers,
> Andrea
>
> On Thu, 23 Aug 2018 at 09:21, <tuf04...@temple.edu> wrote:
>
>>
>>
>> We're attempting to enable the SWORDv2 endpoint in our DSpace instance
>> for use in a DSpace-Symplectic Elements Repository Tools 2 integration.
>> The service document gives this error: "Unable to recognise URL as a
>> valid service document:..."
>>
>> Does anyone have any insight into what could be causing this error?
>>
>> Here's the full message:
>>
>> <sword:error xmlns:sword="http://purl.org/net/sword/terms/"; href="
>> http://www.dspace.org/ns/sword/2.0/errors/BadUrl";>
>> <atom:title xmlns:atom="http://www.w3.org/2005/Atom";>ERROR</atom:title>
>> <atom:updated xmlns:atom="http://www.w3.org/2005/Atom";>
>> 2018-08-22T17:05:38Z</atom:updated>
>> <atom:generator xmlns:atom="http://www.w3.org/2005/Atom"; uri="
>> http://www.dspace.org/ns/sword/2.0/"; version="2.0">[EmailRedacted]
>> </atom:generator>
>> <sword:treatment>Processing failed</sword:treatment>
>> <atom:summary xmlns:atom="http://www.w3.org/2005/Atom";>
>> Unable to recognise URL as a valid service document:
>> http://155.247.166.104:8080/swordv2/servicedocument
>> </atom:summary>
>> <sword:verboseDescription>
>> org.swordapp.server.SwordError: Unable to recognise URL as a valid
>> service document: http://155.247.166.104:8080/swordv2/servicedocument at
>> org.dspace.sword2.SwordUrlManager.extractDSpaceObject(SwordUrlManager.java:323)
>> at
>> org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:169)
>> at
>> org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:74)
>> at org.swordapp.server.ServiceDocumentAPI.get(ServiceDocumentAPI.java:56)
>> at
>> org.swordapp.server.servlets.ServiceDocumentServletDefault.doGet(ServiceDocumentServletDefault.java:32)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:624) at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445)
>> at
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1087)
>> at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
>> at
>> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>> at
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>> </sword:verboseDescription>
>> <atom:link xmlns:atom="http://www.w3.org/2005/Atom"; rel="alternate" type
>> ="text/html" href="http://localhost:8080/contact"/>
>> </sword:error>
>>
>> Thanks for any help you can give us!
>>
>> -GG
>>
>> --
>> All messages to this mailing list should adhere to the DuraSpace Code of
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Dr Andrea Schweer
> Research Technologies Manager, ITS Programme & Commercial
> The University of Waikato, Hamilton, New Zealand
> +64-7-837 9120
>


-- 
Dr Andrea Schweer
Research Technologies Manager, ITS Programme & Commercial
The University of Waikato, Hamilton, New Zealand
+64-7-837 9120

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to