e-Terminology and e-Translation chaining fails on one specific sentence

[borriellom]

When invoking e-Terminology and then e-Translation on the sentence below, e-Translation systematically fails.

Sentence

Our Xperia devices protect sensitive information through an initial combination of strong passwords, PINs and screen unlock patterns.

Response from e-Translation

{
  "exception": "eu.freme.common.exception.ExternalServiceFailedException",
  "path": "/e-translation/tilde",
  "message": "External service failed: {\"Message\":\"MT Internal server error. Reason: Response status code does not indicate success: 400 (Error).\"}",
  "error": "Internal Server Error",
  "status": 500,
  "timestamp": 1476194169293
}

Source language en - Target language de

It could be related to issue #43

[andish]

Can you reproduce this now? just tried, it works

[borriellom]

Yes, I can still reproduce it.

In order to reproduce it you have to chain the services. You can also execute the pipelining chain service in the FREME API documentation with the following body

[
    {
      "method": "POST",
      "endpoint": "http://api-dev.freme-project.eu/current/e-terminology/tilde",
      "parameters": {
        "source-lang": "en",
        "target-lang": "de"
      },
      "headers": {
        "content-type": "text/plain",
        "accept": "text/turtle"
      },
      "body": "Our Xperia devices protect sensitive information through an initial combination of strong passwords, PINs and screen unlock patterns."
    },
    {
      "method": "POST",
      "endpoint": "http://api-dev.freme-project.eu/current/e-translation/tilde",
      "parameters": {
        "source-lang": "en",
        "target-lang": "de"
      },
      "headers": {
        "content-type": "text/turtle",
        "accept": "text/turtle"
      }
    }
  ]

[andish]

Thanks, I reproduced it. Will fix this.

[andish]

Please check, should be resolved.

[borriellom]

Yes, it's fixed. Thank you!!