| RAP Browser-Widget Cross-Domain [message #985924] |
Fri, 16 November 2012 12:10  |
 Thomas Weinstein
Messages: 1
Registered: November 2012 |
Junior Member |
|
|
I have a question regarding the RAP Browser-Widget. I currently try to use a browser widget to load a cross-domain legacy webapp and use javascript as a communication layer.
But to allow the loaded webapp to communicate I tried to set up the domains being on subdomains of each other (a.domain.com and b.domain.com) and modified the document.domain on both sides to domain.com to allow the cross domain communication.
The legacy javascript calls (on domain B) now get permission to call javascript functions defined natively in the opened html (on domain A). But due to the modification of the document.domain, the BrowserFunctions used for Callbacks to the RAP webapp (on domain A) now say permission denied. As far as I understand, the browser widget itself is rendered into an iframe, so now the cross-domain policy prevents these calls.
Do I miss something, because I don't think the scenario of using a cross-domain target in the browser widget is that special, so I wonder someone must have solved this problem already.
Thank you in advance for any hints or tips.
|
|
|
] 
Search
Help
Register
Login
Home
