Tomcat is a web server of its own, so a separate web server like Apache is not required. You probably will want to change Tomcat’s port though, since it defaults to 8080 and web sites are usually on port 80. I think people generally put Apache in front of Tomcat so they can do things … Read more
The earlier answers on this page are correct that you can copy/move the WAR file into place and restart tomcat, but they omit to mention something: you must remove the previously exploded assets (from the previously deployed WAR file) if any are present. # My tomcat webapps are found at /var/lib/tomcat6/webapps # The application I … Read more
File -> Export -> Web -> WAR file OR in Kepler follow as shown below :
All your ant stuff will work fine except the javac task which needs the tools.jar, located in the /lib directory from the JDK, JRE is not sufficient in that case. Therefore the hint from ant : “Unable to find a javac compiler;…” When working with Eclipse the default setting points to your JRE installation. So, … Read more
If you want Tomcat to listen to multiple ports, you need to setup a connector for each port. To get each port mapped to a different application, you need need to wrap each connector in a service and create a host with it’s own appBase. Example of service definition in server.xml: <Service name=”foo”> <Connector port=”80″ … Read more
Use the jetty runner. java -jar jetty-runner.jar my.war With Maven, you can install by adding to your pom.xml: <build> … <plugins> … <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.3</version> <executions> <execution> <phase>package</phase> <goals><goal>copy</goal></goals> <configuration> <artifactItems> <artifactItem> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-runner</artifactId> <version>7.5.4.v20111024</version> <destFileName>jetty-runner.jar</destFileName> </artifactItem> </artifactItems> </configuration> </execution> </executions> </plugin> </plugins> </build> Run: mvn package And use as: java -jar target/dependency/jetty-runner.jar target/*.war … Read more
First of all, “J2EE” is an obsolete abbreviation, it is now simply called “Java Enterprise Edition” or Java EE. Contrary to the servlet container (e.g. Tomcat), “full” Java EE application servers contain also an EJB container. EJB are Enterprise Java Beans and you can read a lot about them for example here (chapter IV). EJBs … Read more
The link you have in your question provides most of what you need. However, there are a few things that need to be done in addition to that. Any class files that Jetty needs to start up will need to be located at the root of the war file when it’s packaged. We can leverage … Read more
I use a combination of the following to make this fairly painless: Cake (incl. the deploy command) A Cake template for webprojects developed by Lau Jensen. Vagrant (Ruby VM(Virtualbox) management tool, which relies on Chef or Puppet) VPS (from Slicehost) The key part is the webdev template that Lau made. The webdev folder should be … Read more
Spring Boot can be told to produce a ‘fat JAR’ which includes all of your module/service’s dependencies and can be run with java -jar <your jar>. See “Create an executable JAR with Maven” here. Spring Boot can also be told to produce a WAR file, in which case you’ll likely choose to deploy it to … Read more