Welcome!

Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

BlackBerry WebWorks Contributions

Reply
Contributor
zantoro
Posts: 14
Registered: ‎09-14-2012
My Carrier: Bouygues

Consume Web Service (JSON) via WebWorks

[ Edited ]

Update: I tried setting a debug point in my webservice and I do get there which means: the problem is on the way back from the webservice.

 

Hello,

I'm trying to consume a webservice (it's my first try) using Webworks. The webservice is written in ASP.NET (and it works fine).

As Emulator I use Ripple.

The code is the one from this post: http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Calling-a-web-service-from-a-Bla...

 

When I click on the button, it outputs "Reuqesting..." but then nothing happen.

Here is output from Ripple:

2012-09-20 08:13:55 GET /HelloWorld/index.html 200
2012-09-20 08:13:55 GET /HelloWorld/json-minified.js 200
2012-09-20 08:13:55 GET /favicon.ico 404
2012-09-20 08:13:55 GET /HelloWorld/config.xml 200
2012-09-20 08:13:55 GET /ripple/about 200
2012-09-20 08:13:55 GET /HelloWorld/index.html 200
2012-09-20 08:13:55 GET /HelloWorld/config.xml 200
2012-09-20 08:13:55 GET /HelloWorld/json-minified.js 200
2012-09-20 08:13:55 GET /favicon.ico 404

 

Do you know how can I troubleshoot it?

 

Thanks,

Roberto.

Please use plain text.
New Developer
dbthundercat
Posts: 33
Registered: ‎01-04-2012
My Carrier: o2

Re: Consume Web Service (JSON) via WebWorks

i too have been having trouble with json data in webworks... code works fine on playbook and smartphone os though :smileyfrustrated:

Please use plain text.
Trusted Contributor
nzcoderguy
Posts: 149
Registered: ‎12-18-2012
My Carrier: 2 Degrees NZ

Re: Consume Web Service (JSON) via WebWorks

I believe this error is regarding cross-domain access policies that Ripple/your web browser is enforcing. It happens when trying to access JSON feeds. See if you can get a JSONP feed instead, or just go with what is working!

+Like this post, if you find it useful/helpful!
Please use plain text.