0 Replies Latest reply on Nov 27, 2012 7:05 AM by ignacio

    Debugging + development sandbox setup for Jive app + Play 2 Java app + Heroku?


      Hi everyone!


      I'm new to Jive and am currently building a Jive app for my "Jive for Teams" community. The backend for this app will be a Play 2.0 Java server-side application which is running on Heroku. The app.xml and the initial html file for the Jive app also reside on Heroku. In addition, I use the osapi.http methods to make the calls to the Play 2.0 application. At the moment, my whole development process is completely inefficient because I deploy my changes directly to Heroku (which takes quite a bit of time) to see how the app will look from within the Jive community. Moreover, I cannot see any debugging information in the Jive app.


      Hence, I would be very grateful for any recommendations regarding a best practice development environment for this setup, including:


      1. I can run the Play 2.0 app locally, which is very efficient, but can I also run the Jive app locally in a sandbox to test their interaction locally?
      2. How can I access all the debugging information from within the Jive app?
      3. How can I access the debugging information for the osapi.http calls?
      4. Are osapi.http calls the only way of communicating with the server side application? My naive approach initially was to just have a frame that points to my external Play 2.0 app...but I guess that doesn't work...?
      5. How can I make sure the javascripts and css files which currently reside with my Play 2.0 application on Heroku are used in the exact same way in the app? Ideally, I would like the Jive app to look exactly like my current Play 2.0 application.


      Thank you very much in advance for your help! All the best and happy coding,