On Thu, Feb 23, 2012 at 8:20 AM, M.KISHORE NAVEEN <[email protected]>wrote:

> Hi Shindig users,
>
> We have a query regarding calling the RESTFUL web service from shindig
> application.
>
> We have shindig application deployed in tomcat on app1. We use Ajax  calls
> to invoke the web service  that is also deployed in app1.the web service
> calls from the shindig works fine.
> We have a web service running in app2 and we need to call the web service
> URL from shindig application. Both app1 and app2 are running in same
> domain. But the web service URL is not getting invoked from application2.
> Can you suggest your ideas please.
>
> It sounds like you have run into the limitations that a browser sandbox
creates (Ajax calls can only go back to the host where the JavaScript code
for the gadget was loaded from).

Fortunately, OpenSocial provides APIs that lets Shindig serve as a proxy
server.  Check out the osapi.http family of APIs[1] in the OpenSocial
specification for details.  (You'll need to require the "osapi" feature in
your gadget.xml file to gain access to these APIs).

Craig

[1]
http://opensocial-resources.googlecode.com/svn/spec/2.0.1/Core-Gadget.xml#osapi.http



> In Brief
>
> 1.App1 contains shindig deployed and web service war deployed---working
> fine
> 2.App2 contains a web service deployed on Web logic and tried to hit app2
> from shindig which is running in app1.----not working.
>
> Regards,
> Naveen
>
>
>
>
>
> ________________________________
> ::DISCLAIMER::
>
> -----------------------------------------------------------------------------------------------------------------------
>
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only.
> It shall not attach any liability on the originator or HCL or its
> affiliates. Any views or opinions presented in
> this email are solely those of the author and may not necessarily reflect
> the opinions of HCL or its affiliates.
> Any form of reproduction, dissemination, copying, disclosure,
> modification, distribution and / or publication of
> this message without the prior written consent of the author of this
> e-mail is strictly prohibited. If you have
> received this email in error please delete it and notify the sender
> immediately. Before opening any mail and
> attachments please check them for viruses and defect.
>
>
> -----------------------------------------------------------------------------------------------------------------------
>

Reply via email to