Wrong response format error in published-data request
Posted: Fri Mar 19, 2021 10:09 am
Dear OPS Team,
we receive a wrong response using the published-data request in DOCDB format for the publication US.10910944.B2
The request is:
http://ops.epo.org/3.2/rest-services/pu ... .B2/biblio
The Response from the OPS service is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>OPS Error</title>
<link href="/style/common.css" media="all" rel="stylesheet" type="text/css"/>
<link href="/images/favicon.ico" rel="favicon"/>
</head>
<body lang="en" class="popup">
<div class="epoContentWrap clearfix">
<div id="pagebody">
<h1>Error</h1>
<h2>org.springframework.oxm.MarshallingFailureException: JiBX marshalling exception; nested exception is org.jibx.runtime.JiBXException: Error writing marshalled document</h2>
<!---->
</div>
</div>
</body>
</html>
As such HTML format error messages are not specified it is very hard to handle such responses in our backend programs. Would it be possible to wrap such error messages into a XML error message.
Many thanks
Thomas Stiefvater
we receive a wrong response using the published-data request in DOCDB format for the publication US.10910944.B2
The request is:
http://ops.epo.org/3.2/rest-services/pu ... .B2/biblio
The Response from the OPS service is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>OPS Error</title>
<link href="/style/common.css" media="all" rel="stylesheet" type="text/css"/>
<link href="/images/favicon.ico" rel="favicon"/>
</head>
<body lang="en" class="popup">
<div class="epoContentWrap clearfix">
<div id="pagebody">
<h1>Error</h1>
<h2>org.springframework.oxm.MarshallingFailureException: JiBX marshalling exception; nested exception is org.jibx.runtime.JiBXException: Error writing marshalled document</h2>
<!---->
</div>
</div>
</body>
</html>
As such HTML format error messages are not specified it is very hard to handle such responses in our backend programs. Would it be possible to wrap such error messages into a XML error message.
Many thanks
Thomas Stiefvater