_oeping error with progress.jsdo.3.0.js

Posted by agent_008_nl on 09-Dec-2014 07:29

Hi,

OE11.3.0

I have this code (see below the error) which gives me a customerdata in a html table. With F12 in chrome I get this in the console

GET http://localhost:8980/CustomerMobile/rest/_oeping?_ts=141813121-1381780000-1 404 (Not Found) progress.jsdo.3.0.js:6773

Is this a bug?

<!DOCTYPE html>
 <html>
 <head>
 <script src="http://localhost:8980/jsdo/progress.jsdo.3.0.js"></script>
 <script>

 session = new progress.data.Session();
 
 var loginResult = session.login("http://localhost:8980/CustomerMobile", "", "");

 session.addCatalog("http://localhost:8980/CustomerMobile/static/mobile/CustomerMobile.json");

 jsdo = new progress.data.JSDO({ name: "dsCustomer" });

 jsdo.subscribe("AfterFill", onAfterFillCustomers, this);

 jsdo.fill();
 function onAfterFillCustomers(jsdo, success, request) {
 document.write('<table border="1" cellspacing="1" cellpadding="5">');
 jsdo.eCustomer.foreach(function(customer) {
 document.write('<tr><td>' + customer.data.CustNum + '</td><td>' + customer.data.Name + '</td></tr>');
 });
 document.write('</table>'); 
 }
 </script>
 </head>
 <body>
 </body>
 </html>

--
Kind regards,

Stefan Houtzager

Houtzager ICT consultancy & development

www.linkedin.com/in/stefanhoutzager

All Replies

Posted by whenshaw on 09-Dec-2014 07:34

This is not an error. The JSDO code checks for the presence of a ping facility on the server during the login process. Only Web applications created with OpenEdge 11.4or later will have _oeping. You should only see the 404 once, at login.

Posted by Anil Kumar on 09-Dec-2014 07:35

Hi Stefan,
 
The error about _oeping not being found is essentially a warning and is expected in certain situations and handled by the JSDO client.
 
This is typically used for online/offline feature functionality which was introduced in OpenEdge 11.4 release. Currently the client invokes OE ping (which checks the availability of mobile service) on the server to see if 'ping' exists.  If this is not there, the client handles this situation gracefully.  However, as a side effect there will be an error in the console. This error can be safely ignored and should not have any impact on your application.
Thanks and Regards,
Anil Kumar.
 
[collapse]
From: agent_008_nl [mailto:bounce-agent_008_nl@community.progress.com]
Sent: Tuesday, December 09, 2014 7:00 PM
To: TU.Mobile@community.progress.com
Subject: [Technical Users - Mobile] _oeping error with progress.jsdo.3.0.js
 
Thread created by agent_008_nl

Hi,

OE11.3.0

I have this code (see below the error) which gives me a customerdata in a html table. With F12 in chrome I get this in the console

GET http://localhost:8980/CustomerMobile/rest/_oeping?_ts=141813121-1381780000-1 404 (Not Found) progress.jsdo.3.0.js:6773

Is this a bug?

<!DOCTYPE html>
 <html>
 <head>
 <script src="http://localhost:8980/jsdo/progress.jsdo.3.0.js"></script>
 <script>

 session = new progress.data.Session();
 
 var loginResult = session.login("http://localhost:8980/CustomerMobile", "", "");

 session.addCatalog("http://localhost:8980/CustomerMobile/static/mobile/CustomerMobile.json");

 jsdo = new progress.data.JSDO({ name: "dsCustomer" });

 jsdo.subscribe("AfterFill", onAfterFillCustomers, this);

 jsdo.fill();
 function onAfterFillCustomers(jsdo, success, request) {
 document.write('<table border="1" cellspacing="1" cellpadding="5">');
 jsdo.eCustomer.foreach(function(customer) {
 document.write('<tr><td>' + customer.data.CustNum + '</td><td>' + customer.data.Name + '</td></tr>');
 });
 document.write('</table>'); 
 }
 </script>
 </head>
 <body>
 </body>
 </html>

--
Kind regards,

Stefan Houtzager

Houtzager ICT consultancy & development

www.linkedin.com/in/stefanhoutzager

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by egarcia on 09-Dec-2014 10:09

Hello,

As whenshaw mentioned, the 404 error should be shown only once with progress.jsdo.3.1.js.

Also, the warning message "Default ping target not available, will use loginTarget instead." is now displayed to clarify on the 404 error.

You can see the new behavior if you look at the messages in the JavaScript Console using the following example:

   oemobiledemo.progress.com/.../example001.html

I hope this helps.

Posted by agent_008_nl on 09-Dec-2014 12:30

Thanks,

I see it and and not sure if it helps. :-)  Is the demo not working with oe 11.4?

oemobiledemo.progress.com/.../_oeping Failed to load resource: the server responded with a status of 404 (Not Found)

progress.jsdo.3.1.js:7912 Default ping target not available, will use loginTarget instead.

By the way, have you followed community.progress.com/.../14611.aspx.

I would appreciate a reaction of one of you guys (on the question on pro's / con's pure rest vs jsdo/rest).

Kind regards, Stefan.

Posted by egarcia on 09-Dec-2014 14:20

Hello Stefan,

Yes, as you suspected, the demo is currently running a version prior to 11.4.

Regards.

This thread is closed