My checklist would be:
- What version of Eclipse are you both using? From your comment it sounds like she is maybe using the base Eclipse install with no support for J2EE and Web added. Make sure you both have the same plug-ins used.
- What version of Java are you both using?
- I'd recommend the latest 7.0u67 (JDK 7u67)
- Why are you sending here a WAR file? At worst send a copy of your Eclipse Workspace. Better, use a shared repository using GIT or SVN.
- Make sure you are both deploying to the same container version. Tomcat 8 is required for Servlet Spec 3.1.. Or use Glassfish 4.1, or WildFly 8.1.0 - JBoss Public Version.
A great tool, especially if one is doing development on the Mac, is a package manager. After evaluating the ones available I chose to use HomeBrew
. I use HomeBrew to install my JDK versions, tomcat, ant, etc.
Use the web links or HomeBrew to get all of this installed and configure Eclipse to globally use that JDK for your development.
On the Mac, she would go to Preferences -> Java -> Installed JREs
I have installed the following:
1.6.0_65 installed as a "MacOS X VM" with a location of /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
1.7.0_67 installed as a "MacOS X VM" with a location of /Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home
1.8.0_20 installed as a "MacOS X VM" with a location of /Library/Java/JavaVirtualMachines/jdk1.8.0_20.jdk/Contents/Home
I have 1.7 selected as my default.
Another best practice would be to use Maven for your build. That way either of you can pull down updates from the repository and the Maven pom files can adjust the Eclipse build to pull in the proper libraries and other configuration items of your application.
You mention the J2EE errors. But then talk about "Dynamic Web Module" which is way different than the J2EE error.
is a technology you are using in your web application but doesn't seem relevant to the issues you are asking about.
I hope that helps get you both moving forward.