I have been working on a Durandal single page application and it’s working pretty well so far. Now I need to connect it to a backend system and my team wants me to use Java for the server side. The problem is I’m not sure how to set this up in Eclipse properly.
The project structure for Durandal apps is completely different from what Eclipse expects for Java projects. Should I try to import my existing Durandal code directly into an Eclipse workspace? That seems like it might cause issues since they use totally different folder layouts.
Maybe there’s a better approach than forcing everything into Eclipse? What other options do people usually go with for this kind of setup?
have you tried using Maven or Gradle? I’m really curious about how you’re managing your build – are you combining everything or keeping them apart? Also, which Java framework are you thinking for the backend? Spring Boot seems like a simpler option than going the old-school servlet route.
running em separately works best. like, durandal can chill on node, and let the java backend handle its own thing on tomcat or whatevr. way easier than cramming it all into eclipse. just set up cors for the requests and u should be all set!
Utilizing separate projects within the same Eclipse workspace is a practical approach. You can maintain your Durandal frontend as an independent project while establishing a Dynamic Web Project for the Java backend. This helps preserve the unique project structures of each technology. Configure your Java project to serve static files from a designated directory, and then use a build script or manual copying to transfer your Durandal build files there. Ensuring that your Java application exposes clear REST endpoints for AJAX calls from Durandal will streamline interactions between the two components. Keeping them distinct simplifies development and provides a cleaner deployment process when adjustments are necessary.