Hi Piotr, in our SampleAmfWebApp I want to write in the wiki but as Alex said you should do in target:
java -jar sampleamfwebapp-0.9.3-SNAPSHOT-exec.war This will run jetty and deploy the war with the example overplayed. Then in a browser put http://localhost:8080, and you'll see the example working. So avoid mvn spring-boot:run, since it doesn't work as expected. As I'm not a jetty user (I'm more familiar with tomcat), I don't know exactly why. For Java or PHP (with AMFPHP) you need always to run the client within the same context that your AMF backend due to how things work and restrictions. You can disable that restrictions for testing in the browser, but that's a dev trick ;) So if your royale app can't communicate with amf running in local, that's totally ok since is how things should work due to normal restrictions. If you want you can drop work on AMF, I'll be adding more communication examples as I have time. Thanks! 2018-04-23 22:48 GMT+02:00 piotrz <[email protected]>: > Hi Carlos, > > I followed your instruction. > > 1) I run spring-boot server > 2) I have it looks like similar problem as you had with restriction. I have > no idea how overcome them. > The second issue is with Access-Control-Allow-Origin. > > I have AMF PHP working and I had the same issue with cross origin - I > couldn't fixed it differently than deploying Example application to place > where AMF is running. > > Anyone have idea how I can fix both issue for JAVA? If it is time consuming > I will drop work on AMF. I have checked many cases in AMF PHP, so I can > assume that they should work in connection with JAVA. > > Screenshot: > <http://apache-royale-development.20373.n8.nabble. > com/file/t1/issues_cross_origin.png> > > Thanks, > Piotr > > > > -- > Sent from: http://apache-royale-development.20373.n8.nabble.com/ > -- Carlos Rovira http://about.me/carlosrovira
