On 9/21/15, 12:40 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>On Mon, Sep 21, 2015 at 9:12 AM, Alex Harui <aha...@adobe.com> wrote: > >>Did you try running from http:// and not just file://? I’m curious as to >> how it works around browser cross-domain security. >> > >We control the SuperProxy app on >https://apache-flex-dashboard.appspot.com, >so I went ahead and added a cross domain xml on the server. >https://apache-flex-dashboard.appspot.com/crossdomain.xml > >It works fine when I run it from http://locahost and an internal remote >server. I can try putting it up in a secret page on flex.apache.org if we >want test it for real. > >Once I get the javascript version building, I will see if it works by >default. If not, I believe I can set the Access-Control-Allow-Origin >header to * for the server responses which would take care of CORS in the >JS version. If you can control the crossdomain.xml and HTTP Headers we’ll probably be ok, but I wouldn’t use *, just a small whitelist, or maybe *.a.o. >> > >I created a new JSON input parser here: >https://github.com/apache/flex-asjs/blob/develop/examples/flexjs/FlexWebsi >teStatsViewer/src/controllers/GAJSONInputParser.as > >I assumed that the IInputParser would be available because it works in >other other examples. Now I realize that we need to add it to the JS >side. > > >I still need to get my FlexJS build fixed before I can do that. Perhaps >you can add that file in the js version so that we can quickly test if the >JS version works as well? Well, it would be faster for now if your input parser subclasses JSONInputParser. Then you wouldn’t need IInputParser or a new build. -Alex
