Due to recent updates, all users are required to create an Altair One account to login to the RapidMiner community. Click the Register button to create your account using the same email that you have previously used to login to the RapidMiner community. This will ensure that any previously created content will be synced to your Altair One account. Once you login, you will be asked to provide a username that identifies you to other Community users. Email us at Community with questions.

Decipher log message

sgenzersgenzer Administrator, Moderator, Employee, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM Moderator Posts: 2,959 Community Manager
edited November 2018 in Help
What does this log message mean?

Apr 21, 2016 10:02:30 AM WARNING: Could build DOM from XML! Just using plain text. Reason: Error on line 1: Content is not allowed in prolog.

Answers

  • Marco_BoeckMarco_Boeck Administrator, Moderator, Employee, Member, University Professor Posts: 1,996 RM Engineering
    Hi,

    it means that someone expected XML but did not get it, e.g. the first character was not '<'.

    What did you do to trigger this?

    Regards,
    Marco
  • sgenzersgenzer Administrator, Moderator, Employee, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM Moderator Posts: 2,959 Community Manager
    As you may have surmised, I am testing various APIs in RM.  I got the log message when using Enrich Data by Webservice, doing an API call to an IBM Watson API called "Language Translation".  As I mentioned in another post, I am having a LOT of trouble debugging API calls using this operator.
  • JEdwardJEdward RapidMiner Certified Analyst, RapidMiner Certified Expert, Member Posts: 578 Unicorn
    Generally if you are debugging a webservice for the first time try to get some sample outputs and store them locally using write document. 
    This way you can test expected outputs.  Try different variables in the call also to get some sample standard responses and sample error responses. 

    Then once you have it setup and working for all standard messages put it inside a Handle Exception operator and have several methods to deal with non-standard responses.  For example if it's an error you've met before in your testing your can capture the response in your process.  If it's a brand new error response you can store the content of the XML doc and alert you to update your process to investigate. 

    For example is the API perhaps returning JSON data rather than XML? 
Sign In or Register to comment.