I’m new to GWT and want to create a project with a GWT frontend and PHP backend that use JSON to communicate. The official docs suggest compiling the GWT frontend and then moving it to a web server. But I’m wondering if there’s a way to skip this step.
Is it possible to set up both Jetty and Apache on localhost so I can work on the GWT frontend in hosted mode while also developing the PHP backend? This would make the development process much smoother.
Another option I’m considering is configuring GWT Host mode to use Apache or Tomcat on localhost instead of Jetty. Has anyone tried this before?
I’m looking for a setup that lets me work on both parts of my project at the same time without constantly having to compile and move files. Any suggestions or tips would be really helpful!
ooh, that sounds like an interesting project! have u considered using a reverse proxy setup? it could route requests to either gwt or php based on url patterns. might be worth exploring. what kinda app are u building, btw? im curious about how ur integrating gwt and php!
Setting up a simultaneous development environment for GWT frontend and PHP backend is indeed possible and can significantly streamline your workflow. One effective approach is to use Apache with mod_proxy to route requests appropriately. Configure Apache to serve your PHP files directly and proxy requests for your GWT application to the development server.
This setup allows you to run both environments concurrently without constant compilation. You’ll need to adjust your GWT configuration to point to the correct backend URL, typically something like ‘http://localhost/api’ for your PHP endpoints.
Remember to clear your browser cache regularly and consider using browser developer tools to disable caching during development. This approach has worked well in my experience, offering a seamless development process for hybrid GWT/PHP applications.
yeah, u can definitely do that! i use xampp for apache/php and run gwt in dev mode. just make sure to set up ur GWT.setProperty for the correct backend URL. it’s way easier than constantly rebuilding. just watch out for browser cache issues - they can be a pain sometimes.