Java Web Project referencing another Java project

Question

I have a Java Project, for which I\'m now creating a Web interface, using a Dynamic Web Project from Eclipse. The Web project consists of a single

Answer 1

Connecting java app to web app for development :

right click on web project :

properties>project references> add the java project you want to refer

Now in properties tab of web project go to

properties>deployment assembly> add the project manually and run the app

Answer 2

Typically you would create an API interface using remote service beans from the Java application that expose the methods that you want to invoke in the web application. You would include a proxy of the API interface with your web application that calls the remote service bean in the Java application. Remember that you will need to register the remote bean in the web.xml file.

Answer 3

In Eclipse project properties, add the project to the Java EE Module Dependencies (Eclipse 3.5 or older)

or Deployment Assembly (Eclipse 3.6 or newer) entry in the project properties.

This way Eclipse will take care about doing the right thing to create a WAR out of this all (it will end in /WEB-INF/lib). No other configuration is necessary, even not some fiddling in Build Path.

Answer 4

Under Eclipse, you can declare Project References for a given project, the web application in your case. To do so, right click on your web application project, then go for Properties > Project References and select the JavaApplication project. This should allow you to call code from the JavaApplication project from the WebApplication without having to build a WAR. This is a solution for development.

For standard deployment (outside the IDE), you should indeed create a standard WAR. To do so, you'll have to package your JavaApplication as a JAR including the .class files and the files under /resources but not the libraries it depends on (JARs under /lib). These dependencies will actually end up in the WEB-INF/lib directory of the WAR, beside the JAR of your JavaApplication. These steps are typically automated with tools like Ant or Maven.

Answer 5

Consider moving up to EAR level, if your web container supports that.

The tricky part with shared code is where should the common code be put. A copy pr web application? A copy in the web container? Overdoing the "share these classes" might end up in class loader problems.

If you are creating two separate web applications refactor common java code into a separate Eclipse project and refer to it from both WAR projects.

---

EDIT: Apparently I have misread the problem description, and thought you asked about an existing and a new web application sharing code.

If you have an Eclipse project with your application, and another with your web frontend, then you can let your application export the necessary resources which the "Export WAR" in Eclipse Java EE can wrap up in a jar file and put in WEB-INF/lib for you. You need to say this explicitly with a checkmark in Properties -> Java EE Module Dependencies for your web project. Expect you have to experiment a bit - this took me a while to learn.