glassfish-web.xml vs sun-web.xml vs web.xml

Asked 27/9, 2013 at 15:19 Answered 27/3, 2017 at 19:8

Could someone explain the main differences (or provide a link to) between glassfish-web.xml, sun-web.xml and web.xml?

Can I use just glassfish-web.xml in my webapp and skip the others?

Mombasa answered 27/9, 2013 at 15:19 Comment(1)

See also: #20540342 – Yocum 15/9, 2014 at 14:38

web.xml: Standard deployment descriptor defined by Java EE (Servlet JSR in particular, but used by many JSRs). It is used to specify the metadata used by the web container to deploy the application in a portable manner across application servers (such as the URL endpoint of a servlet). In Java EE 6 and beyond, it is optional (depending on technologies that you use) when metadata is provided by annotations in your Java code, like @WebServlet.
glassfish-web.xml: Each application server offers implementation-specific features. To configure these features for GlassFish, use glassfish-web.xml. This is documented in the GlassFish Documentation.
sun-web.xml: Legacy application-server specific deployment descriptor, and has been replaced by glassfish-web.xml. It no longer made sense to have this name after Sun was acquired by Oracle. This file name is still supported for backwards compatibility, but you should migrate to glassfish-web.xml.

You may or may not need a web.xml file. It depends on the Java EE features you use. By default, don't use any of these files and simply use Java EE annotations like @WebServlet. As you build out your app and perhaps begin using some features that require the web.xml file (like to define the JavaServer Faces FacesServlet), then use a web.xml file. As for the glassfish-web.xml, you only use one if you have GlassFish-specific features to configure for your application.

The Java EE tutorial is also a good way to learn Java EE, and is bundled with the Java EE 7 SDK along with GlassFish 4.

Lewd answered 27/9, 2013 at 21:23 Comment(2)

hi, could you explain to me where does web logic .xml in all of this thanks – Troytroyer 22/2, 2014 at 19:37

weblogic.xml is similar to glassfish-web.xml, but contains configuration options specific to WebLogic. See docs.oracle.com/middleware/1212/wls/WLPRG/overview.htm#WLPRG111 – Lewd 25/2, 2014 at 0:10

-5

Web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns="http://java.sun.com/xml/ns/javaee" 
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
  <display-name>BusProject</display-name>
  <welcome-file-list>
    <welcome-file>login.jsp</welcome-file>
  </welcome-file-list>
  <servlet>
    <servlet-name>spring</servlet-name>
    <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
     <load-on-startup>1</load-on-startup>
  </servlet>
  <servlet-mapping>
    <servlet-name>spring</servlet-name>
    <url-pattern>/</url-pattern>
  </servlet-mapping>
   <context-param>
  <param-name>contextConfigLocation</param-name>
  <param-value>/WEB-INF/spring-servlet.xml</param-value>
  </context-param>  
  <listener>
  <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
  </listener>
 </web-app>

Fulguration answered 27/3, 2017 at 19:8 Comment(1)

Some narrative would be nice here, especially since that is what OP is asking for. The heart of the question is "explain main differences", which this monolith of an answer clearly does not do. – Clothing 27/3, 2017 at 19:31

Recommended topics

Hot tags