404 error
Hey I install your gem and the end point on the leipzig corpus page is resulting in a 404 error. Any idea why? I was wondering if that could have be something with the Rest API.
Hi @janz93 ,
the endpoint is rather instable so it's a possible explanation. Could you post the whole error trace?
Sure the soap endpoint which is used the api class is returning a 404 result.

Savon::HTTPError: Not Found (404): <!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Fehlerseite</title>
<!-- FA-Icons -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css" />
<!-- Bootstrap -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css" />
<link rel="stylesheet" type="text/css" href="http://wortschatz.uni-leipzig.de/public/css/style.css" />
<!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
<link rel="shortcut icon" type="image/x-icon" href="http://wortschatz.uni-leipzig.de/public/images/favicon.ico
/>
</head>
<body>
<div class="wrapper center">
<div class="col-md-6 col-sm-8 col-md-offset-3 col-sm-offset-2">
<div id="header">
<h1>Corpora Collection</h1>
</div>
<h2>Es ist ein Fehler aufgetreten</h2>
<div>404</div>
<a href="http://wortschatz.uni-leipzig.de/de">Zurück zur Startseite</a>
</div>
</div>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.0/jquery.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.2.0/js/bootstrap.min.js"></script>
</body>
</html>
from D:/ruby/Ruby22/lib/ruby/gems/2.2.0/gems/savon-0.7.9/lib/savon/response.rb:168:in `handle_http_error'
from D:/ruby/Ruby22/lib/ruby/gems/2.2.0/gems/savon-0.7.9/lib/savon/response.rb:82:in `initialize'
from D:/ruby/Ruby22/lib/ruby/gems/2.2.0/gems/savon-0.7.9/lib/savon/client.rb:95:in `new'
from D:/ruby/Ruby22/lib/ruby/gems/2.2.0/gems/savon-0.7.9/lib/savon/client.rb:95:in `method_missing'
from D:/ruby/Ruby22/lib/ruby/gems/2.2.0/gems/wlapi-0.7.4/lib/wlapi/api.rb:288:in `query'
from D:/ruby/Ruby22/lib/ruby/gems/2.2.0/gems/wlapi-0.7.4/lib/wlapi/api.rb:142:in `synonyms'
from (irb):3
from D:/ruby/Ruby22/bin/irb:11:in `<main>'
irb(main):004:0>
So, that's easy :) They moved the endpoint. I'll investigate that now.
I figured :) Let me know what comes up. Also I was wondering what is with the rest api? OR you planning on using that too?
I'm planning to completely rewrite the client to use the restful API since the old SOAP backend will be shut down. I've just emailed the devs in Leipzig to get more insights about that.
The problem for now is that the old services are not online and the new ones are not complete.
Feel free to use the REST endpoint meanwhile.
Okay I see. Would it be useful to integrate the rest api endpoint into your gem or are you planning on using the new soap endpoint when it will be finished?
I think we should integrate the new RESTful API and map it onto the old methods if possible.