`

web.xml 配置参考文档

 
阅读更多

web.xml Deployment Descriptor Elements

The following sections describe the deployment descriptor elements defined in the web.xml file under the root element <web-app>:

 


icon

The icon element specifies the location within the Web application for a small and large image used to represent the Web application in a GUI tool. (The servlet element also has an element called the icon element, used to supply an icon to represent a servlet in a GUI tool.)

The following table describes the elements you can define within an icon element.

Element

Required/
Optional

Description

<small-icon>

Optional

Location for a small (16x16 pixel) .gif or .jpg image used to represent the Web application in a GUI tool. Currently, this is not used by WebLogic Server.

<large-icon>

Optional

Location for a large (32x32 pixel) .gif or .jpg image used to represent the Web application in a GUI tool. Currently, this element is not used by WebLogic Server.

 

 


display-name

The optional display-name element specifies the Web application display name, a short name that can be displayed by GUI tools.

Element

Required/
Optional

Description

<display-name>

Optional

Currently, this element is not used by WebLogic Server.

 

 


description

The optional description element provides descriptive text about the Web application.

Element

Required/
Optional

Description

<description>

Optional

Currently, this element is not used by WebLogic Server.

 

 


distributable

The distributable element is not used by WebLogic Server.

Element

Required/
Optional

Description

<distributable>

Optional

Currently, this element is not used by WebLogic Server.

 

 


context-param

The optional context-param element contains the declaration of a Web application's servlet context initialization parameters. The following table describes the reserved context parameters used by the Web application container, which have been deprecated and have replacements in weblogic.xml..

Deprecated Parameter

Description

Replacement Element in weblogic.xml

weblogic.httpd.inputCharset

Defines code set behavior for non-unicode operations.

input-charset (defined within charset-param) in weblogic.xml. See input-charset.

weblogic.httpd.servlet.reloadCheckSecs

Define how often WebLogic Server checks whether a servlet has been modified, and if so, reloads it. A value of -1 is never reload, 0 is always reload. The default is set to 1 second.

servlet-reload-check-secs (defined within container-descriptor) in weblogic.xml.See container-descriptor.

weblogic.httpd.servlet.classpath

When this values has been set, the container appends this path to the Web application classpath. This is not a recommended method and is supported only for backward compatibility.

No replacement. Use other means such as manifest classpath or WEB-INF/lib or WEB-INF/classes or virtual directories.

weblogic.httpd.defaultServlet

Sets the default servlet for the Web application. This is not a recommended
method and is supported only for backward compatibility.

No replacement. Instead use the servlet and servlet-mapping elements in web.xml to define a default servlet. The URL pattern for default-servlet should be "/". See servlet-mapping. For additional examples of servlet mapping, see Servlet Mapping.

 

The following context-param parameter is still valid.

Element

Required/
Optional

Description

weblogic.httpd.
clientCertProxy

optional

This attribute specifies that certifications from clients of the Web application are provided in the special WL-Proxy-Client-Cert header sent by a proxy plug-in or HttpClusterServlet.

This setting is useful if user authentication is performed on a proxy server—setting clientCertProxy causes the proxy server to pass on the certs to the cluster in a special header, WL-Proxy-Client-Cert.

A WL-Proxy-Client-Cert header could be provided by any client with access to WebLogic Server. WebLogic Server takes the certificate information from that header, trusting that is came from a secure source (the plug-in) and uses that information to authenticate the user.

For this reason, if you set clientCertProxy, use a connection filter to ensure that WebLogic Server accepts connections only from the machine on which the plug-in is running. See Using Network Connection Filters in Programming WebLogic Security.

In addition to setting this attribute for an individual Web application, you can define this attribute:

  • For all web applications hosted by a server instance, on the Server-->Configuration-->General page in the Administration Console

  • For all web applications hosted by server instances in a cluster, on the Cluster-->Configuration-->General page.

 

 


filter

The filter element defines a filter class and its initialization attributes. For more information on filters, see Configuring Filters.

The following table describes the elements you can define within a filter element.

Element

Required/
Optional

Description

<icon>

Optional

Specifies the location within the Web application for a small and large image used to represent the filter in a GUI tool. Contains a small-icon and large-icon element.

Currently, this element is not used by WebLogic Server.

<filter-name>

Required

Defines the name of the filter, used to reference the filter definition elsewhere in the deployment descriptor.

<display-name>

Optional

A short name intended to be displayed by GUI tools.

<description>

Optional

A text description of the filter.

<filter-class>

Required

The fully-qualified class name of the filter.

<init-param>

Optional

Contains a name/value pair as an initialization attribute of the filter.

Use a separate set of <init-param> tags for each attribute.

 

 


filter-mapping

The following table describes the elements you can define within a filter-mapping element.

Element

Required/
Optional

Description

<filter-name>

Required

The name of the filter to which you are mapping a URL pattern or servlet. This name corresponds to the name assigned in the <filter> element with the <filter-name> element.

<url-pattern>

Required - or map by <servlet>

Describes a pattern used to resolve URLs. The portion of the URL after the http://host:port + ContextPath is compared to the <url-pattern> by WebLogic Server. If the patterns match, the filter mapped in this element is called.

Example patterns:

/soda/grape/*
/foo/*
/contents
*.foo

The URL must follow the rules specified in the Servlet 2.3 Specification.

<servlet-name>

Required - or map by <url-pattern>

The name of a servlet which, if called, causes this filter to execute.

 

 


listener

Define an application listener using the listener element.

Element

Required/
Optional

Description

<listener-class>

Optional

Name of the class that responds to a Web application event.

 

For more information, see Configuring an Event Listener Class.

 


servlet

The servlet element contains the declarative data of a servlet.

If a jsp-file is specified and the <load-on-startup> element is present, then the JSP is precompiled and loaded when WebLogic Server starts.

The following table describes the elements you can define within a servlet element.

Element

Required/
Optional

Description

<icon>

Optional

Location within the Web application for a small and large image used to represent the servlet in a GUI tool. Contains a small-icon and large-icon element.

Currently, this element is not used by WebLogic Server.

<servlet-name>

Required

Defines the canonical name of the servlet, used to reference the servlet definition elsewhere in the deployment descriptor.

<display-name>

Optional

A short name intended to be displayed by GUI tools.

<description>

Optional

A text description of the servlet.

<servlet-class>

Required (or use <jsp-
file>)

The fully-qualified class name of the servlet.

Use only one of either the <servlet-class> tags or <jsp-file> tags in your servlet body.

<jsp-file>

Required (or use <servlet-
class>)

The full path to a JSP file within the Web application, relative to the Web application root directory.

Use only one of either the <servlet-class> tags or <jsp-file> tags in your servlet body.

<init-param>

Optional

Contains a name/value pair as an initialization attribute of the servlet.

Use a separate set of <init-param> tags for each attribute.

<load-on-startup>

Optional

WebLogic Server initializes this servlet when WebLogic Server starts up. The optional content of this element must be a positive integer indicating the order in which the servlet should be loaded. Lower integers are loaded before higher integers. If no value is specified, or if the value specified is not a positive integer, WebLogic Server can load the servlet in any order during application startup.

<run-as>

Optional

Specifies the run-as identity to be used for the execution of the Web application. It contains an optional description and the name of a security role.

<security-role-
ref>

Optional

Used to link a security role name defined by <security-role> to an alternative role name that is hard coded in the servlet logic. This extra layer of abstraction allows the servlet to be configured at deployment without changing servlet code.

 

icon

This is an element within the servlet.

The icon element specifies the location within the Web application for small and large images used to represent the servlet in a GUI tool.

The following table describes the elements you can define within an icon element.

Element

Required/
Optional

Description

<small-icon>

Optional

Specifies the location within the Web application for a small (16x16 pixel) .gif or .jpg image used to represent the servlet in a GUI tool.

Currently, this element is not used by WebLogic Server.

<large-icon>

Optional

Specifies the location within the Web application for a small (32x32 pixel) .gif or.jpg image used to represent the servlet in a GUI tool.

Currently, this element is not used by WebLogic Server.

 

init-param

This is an element within the servlet.

The optional init-param element contains a name/value pair as an initialization attribute of the servlet. Use a separate set of init-param tags for each attribute.

You can access these attributes with the javax.servlet.ServletConfig.getInitParameter() method.

The following table describes the elements you can define within a init-param element.

Element

Required/
Optional

Description

<param-name>

Required

Defines the name of this attribute.

<param-value>

Required

Defines a String value for this attribute.

<description>

Optional

Text description of the initialization attribute.

 

security-role-ref

This is an element within the servlet.

The security-role-ref element links a security role name defined by <security-role> to an alternative role name that is hard-coded in the servlet logic. This extra layer of abstraction allows the servlet to be configured at deployment without changing servlet code.

The following table describes the elements you can define within a security-role-ref element.

Element

Required/
Optional

Description

<description>

Optional

Text description of the role.

<role-name>

Required

Defines the name of the security role or principal that is used in the servlet code.

<role-link>

Required

Defines the name of the security role that is defined in a <security-role> element later in the deployment descriptor.

 

 


servlet-mapping

The servlet-mapping element defines a mapping between a servlet and a URL pattern.

The following table describes the elements you can define within a servlet-mapping element.

Element

Required/
Optional

Description

<servlet-name>

Required

The name of the servlet to which you are mapping a URL pattern. This name corresponds to the name you assigned a servlet in a <servlet> declaration tag.

<url-pattern>

Required

Describes a pattern used to resolve URLs. The portion of the URL after the http://host:port + WebAppName is compared to the <url-pattern> by WebLogic Server. If the patterns match, the servlet mapped in this element will be called.

Example patterns:

/soda/grape/*
/foo/*
/contents
*.foo

The URL must follow the rules specified in the Servlet 2.3 Specification.

For additional examples of servlet mapping, see Servlet Mapping.

 

 


session-config

The session-config element defines the session attributes for this Web application.

The following table describes the element you can define within a session-config element.

Element

Required/
Optional

Description

<session-timeout>

Optional

The number of minutes after which sessions in this Web application expire. The value set in this element overrides the value set in the TimeoutSecs attribute of the <session-descriptor> element in the WebLogic-specific deployment descriptor weblogic.xml, unless one of the special values listed here is entered.

Default value: -2

Maximum value: Integer.MAX_VALUE ÷ 60

Special values:

  • -2 = Use the value set by TimeoutSecs in <session-descriptor> element of weblogic.xml

  • -1 = Sessions do not timeout. The value set in <session-descriptor> element of weblogic.xml is ignored.

For more information, see session-descriptor.

 

 


mime-mapping

The mime-mapping element defines a mapping between an extension and a mime type.

The following table describes the elements you can define within a mime-mapping element.

Element

Required/
Optional

Description

<extension>

Required

A string describing an extension, for example: txt.

<mime-type>

Required

A string describing the defined mime type, for example: text/plain.

 

 


welcome-file-list

The optional welcome-file-list element contains an ordered list of welcome-file elements.

When the URL request is a directory name, WebLogic Server serves the first file specified in this element. If that file is not found, the server then tries the next file in the list.

For more information, see Configuring Welcome Pages and How WebLogic Server Resolves HTTP Requests.

The following table describes the element you can define within a welcome-file-list element.

Element

Required/
Optional

Description

<welcome-file>

Optional

File name to use as a default welcome file, such as index.html

 

 


error-page

The optional error-page element specifies a mapping between an error code or exception type to the path of a resource in the Web application.

When an error occurs—while WebLogic Server is responding to an HTTP request, or as a result of a Java exception—WebLogic Server returns an HTML page that displays either the HTTP error code or a page containing the Java error message. You can define your own HTML page to be displayed in place of these default error pages or in response to a Java exception.

For more information, see Customizing HTTP Error Responses and How WebLogic Server Resolves HTTP Requests

The following table describes the elements you can define within an error-page element.

Note: Define either an <error-code> or an <exception-type> but not both.

Element

Required/
Optional

Description

<error-code>

Optional

A valid HTTP error code, for example, 404.

<exception-type>

Optional

A fully-qualified class name of a Java exception type, for example, java.lang.string

<location>

Required

The location of the resource to display in response to the error. For example, /myErrorPg.html.

 

 


taglib

The optional taglib element describes a JSP tag library.

This element associates the location of a JSP Tag Library Descriptor (TLD) with a URI pattern. Although you can specify a TLD in your JSP that is relative to the WEB-INF directory, you can also use the <taglib> tag to configure the TLD when deploying your Web application. Use a separate element for each TLD.

The following table describes the elements you can define within a taglib element.

Element

Required/
Optional

Description

<taglib-location>

Required

Gives the file name of the tag library descriptor relative to the root of the Web application. It is a good idea to store the tag library descriptor file under the WEB-INF directory so it is not publicly available over an HTTP request.

<taglib-uri>

Required

Describes a URI, relative to the location of the web.xml document, identifying a Tag Library used in the Web application.

If the URI matches the URI string used in the taglib directive on the JSP page, this taglib is used.

 

 


resource-env-ref

The resource-env-ref element contains a declaration of a Web application's reference to an administered object associated with a resource in the Web application's environment. It consists of an optional description, the resource environment reference name, and an indication of the resource environment reference type expected by the Web application code.

For example:

<resource-env-ref>
 <resource-env-ref-name>jms/StockQueue</resource-env-ref-name>
 <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>

The following table describes the elements you can define within a resource-env-ref element.

Element

Required/
Optional

Description

<description>

Optional

Provides a description of the resource environment reference.

<resource-env-ref-name>

Required

Specifies the name of a resource environment reference; its value is the environment entry name used in the Web application code. The name is a JNDI name relative to the java:comp/env context and must be unique within a Web application.

<resource-env-ref-type>

Required

Specifies the type of a resource environment reference. It is the fully qualified name of a Java language class or interface.

 

 


resource-ref

The optional resource-ref element defines a reference lookup name to an external resource. This allows the servlet code to look up a resource by a "virtual" name that is mapped to the actual location at deployment time.

Use a separate <resource-ref> element to define each external resource name. The external resource name is mapped to the actual location name of the resource at deployment time in the WebLogic-specific deployment descriptor weblogic.xml.

The following table describes the elements you can define within a resource-ref element.

Element

Required/
Optional

Description

<description>

Optional

A text description.

<res-ref-name>

Required

The name of the resource used in the JNDI tree. Servlets in the Web application use this name to look up a reference to the resource.

<res-type>

Required

The Java type of the resource that corresponds to the reference name. Use the full package name of the Java type.

<res-auth>

Required

Used to control the resource sign on for security.

If set to APPLICATION, indicates that the application component code performs resource sign on programmatically. If set to CONTAINER, WebLogic Server uses the security context established with the login-config element. See login-config.

<res-sharing-scope>

Optional

Specifies whether connections obtained through the given resource manager connection factory reference can be shared.

Valid values:

  • Shareable

  • Unshareable

 

 


security-constraint

The security-constraint element defines the access privileges to a collection of resources defined by the <web-resource-collection> element.

For detailed instructions and an example on configuring security in Web applications, see Securing WebLogic Resources. Also, for more information on WebLogic Security, refer to Programming WebLogic Security.

The following table describes the elements you can define within a security-constraint element.

Element

Required/
Optional

Description

<web-resource-
collection>

Required

Defines the components of the Web application to which this security constraint is applied.

<auth-constraint>

Optional

Defines which groups or principals have access to the collection of web resources defined in this security constraint. See also auth-constraint.

<user-data-
constraint>

Optional

Defines how the client should communicate with the server.

See also user-data-constraint

 

web-resource-collection

Each <security-constraint> element must have one or more <web-resource-collection> elements. These define the area of the Web application to which this security constraint is applied.

This is an element within the security-constraint.

The following table describes the elements you can define within a web-resource-collection element.

Element

Required/
Optional

Description

<web-resource-
name>

Required

The name of this Web resource collection.

<description>

Optional

A text description of this security constraint.

<url-pattern>

Optional

Use one or more of the <url-pattern> elements to declare to which URL patterns this security constraint applies. If you do not use at least one of these elements, this <web-resource-collection> is ignored by WebLogic Server.

<http-method>

Optional

Use one or more of the <http-method> elements to declare which HTTP methods (usually, GET or POST) are subject to the authorization constraint. If you omit the <http-method> element, the default behavior is to apply the security constraint to all HTTP methods.

 

auth-constraint

This is an element within the security-constraint.

The optional auth-constraint element defines which groups or principals have access to the collection of Web resources defined in this security constraint.

The following table describes the elements you can define within an auth-constraint element.

Element

Required/
Optional

Description

<description>

Optional

A text description of this security constraint.

 

user-data-constraint

This is an element within the security-constraint.

The user-data-constraint element defines how the client should communicate with the server.

The following table describes the elements you may define within a user-data-constraint element.

Element

Required/
Optional

Description

<description>

Optional

A text description.

<transport-
guarantee>

Required

Specifies that the communication between client and server.

WebLogic Server establishes a Secure Sockets Layer (SSL) connection when the user is authenticated using the INTEGRAL or CONFIDENTIAL transport guarantee.

Range of values:

  • NONE—The application does not require any transport guarantees.

  • INTEGRAL—The application requires that the data be sent between the client and server in such a way that it cannot be changed in transit.

  • CONFIDENTIAL—The application requires that data be transmitted so as to prevent other entities from observing the contents of the transmission.

 

 


login-config

Use the optional login-config element to configure how the user is authenticated; the realm name that should be used for this application; and the attributes that are needed by the form login mechanism.

If this element is present, the user must be authenticated in order to access any resource that is constrained by a <security-constraint> defined in the Web application. Once authenticated, the user can be authorized to access other resources with access privileges.

The following table describes the elements you can define within a login-config element.

Element

Required/
Optional

Description

<auth-method>

Optional

Specifies the method used to authenticate the user. Possible values:

BASIC—uses browser authentication. (This is the default value.)
FORM—uses a user-written HTML form.
CLIENT-CERT

<realm-name>

Optional

The name of the realm that is referenced to authenticate the user credentials. If omitted, the realm defined with the Auth Realm Name field on the Web application—> Configuration—>Other tab of the Administration Console is used by default. For more information, see Managing WebLogic Security.

Note: The <realm-name> element does not refer to system security realms within WebLogic Server. This element defines the realm name to use in HTTP Basic authorization. The system security realm is a collection of security information that is checked when certain operations are performed in the server. The servlet security realm is a different collection of security information that is checked when a page is accessed and basic authentication is used.

<form-login-
config>

Optional

Use this element if you configure the <auth-method> to FORM. See form-login-config.

 

form-login-config

This is an element within the login-config.

Use the <form-login-config> element if you configure the <auth-method> to FORM.

.

Element

Required/
Optional

Description

<form-login-page>

Required

The URI of a Web resource relative to the document root, used to authenticate the user. This can be an HTML page, JSP, or HTTP servlet, and must return an HTML page containing a FORM-based authentication that conforms to a specific naming convention.

<form-error-page>

Required

The URI of a Web resource relative to the document root, sent to the user in response to a failed authentication login.

 

 


security-role

The following table describes the elements you can define within a security-role element.

Element

Required/
Optional

Description

<description>

Optional

A text description of this security role.

<role-name>

Required

The role name. The name you use here must have a corresponding entry in the WebLogic-specific deployment descriptor, weblogic.xml, which maps roles to principals in the security realm. For more information, see security-role-assignment.

 

 


env-entry

The optional env-entry element declares an environment entry for an application. Use a separate element for each environment entry.

The following table describes the elements you can define within an env-entry element.

Element

Required/
Optional

Description

<description>

Optional

A textual description.

<env-entry-name>

Required

The name of the environment entry.

<env-entry-value>

Required

The value of the environment entry.

<env-entry-type>

Required

The type of the environment entry.

Can be set to one of the following Java types:

java.lang.Boolean

java.lang.String

java.lang.Integer

java.lang.Double

java.lang.Float

 

 


ejb-ref

The optional ejb-ref element defines a reference to an EJB resource. This reference is mapped to the actual location of the EJB at deployment time by defining the mapping in the WebLogic-specific deployment descriptor file, weblogic.xml. Use a separate <ejb-ref> element to define each reference EJB name.

The following table describes the elements you can define within an ejb-ref element.

Element

Required/
Optional

Description

<description>

Optional

A text description of the reference.

<ejb-ref-name>

Required

The name of the EJB used in the Web application. This name is mapped to the JNDI tree in the WebLogic-specific deployment descriptor weblogic.xml. For more information, see ejb-reference-description.

<ejb-ref-type>

Required

The expected Java class type of the referenced EJB.

<home>

Required

The fully qualified class name of the EJB home interface.

<remote>

Required

The fully qualified class name of the EJB remote interface.

<ejb-link>

Optional

The <ejb-name> of an EJB in an encompassing J2EE application package.

<run-as>

Optional

A security role whose security context is applied to the referenced EJB. Must be a security role defined with the <security-role> element.

 

 


ejb-local-ref

The ejb-local-ref element is used for the declaration of a reference to an enterprise bean's local home. The declaration consists of:

  • An optional description
  • The EJB reference name used in the code of the Web application that references the enterprise bean. The expected type of the referenced enterprise bean
  • The expected local home and local interfaces of the referenced enterprise bean
  • Optional ejb-link information, used to specify the referenced enterprise bean

The following table describes the elements you can define within an ejb-local-ref element.

Element

Required/
Optional

Description

<description>

Optional

A text description of the reference.

<ejb-ref-name>

Required

Contains the name of an EJB reference. The EJB reference is an entry in the Web application's environment and is relative to the java:comp/env context. The name must be unique within the Web application. It is recommended that name is prefixed with ejb/.

For example:

<ejb-ref-name>ejb/Payroll</ejb-ref-name>

<ejb-ref-type>

Required

The ejb-ref-type element contains the expected type of the referenced enterprise bean. The ejb-ref-type element must be one of the following:

<ejb-ref-type>Entity</ejb-ref-type>
<ejb-ref-type>Session</ejb-ref-type>

<local-home>

Required

Contains the fully-qualified name of the enterprise bean's local home interface.

<local>

Required

Contains the fully-qualified name of the enterprise bean's local interface.

<ejb-link>

Optional

The ejb-link element is used in the ejb-ref or ejb-local-ref

elements to specify that an EJB reference is linked to an

EJB.

The name in the ejb-link element is composed of a path name. This path name specifies the ejb-jar containing the referenced EJB with the ejb-name of the target bean appended and separated from the path name by #.

The path name is relative to the WAR file containing the Web application that is referencing the EJB. This allows multiple EJBs with the same ejb-name to be uniquely identified.

Used in: ejb-local-ref and ejb-ref elements

Examples:

<ejb-link>EmployeeRecord</ejb-link>

<ejb-link>../products/product.jar#ProductEJB</ejb-link>

Element

Required/
Optional

Description

<description>

Optional

A text description of the reference.

<ejb-ref-name>

Required

Contains the name of an EJB reference. The EJB reference is an entry in the Web application's environment and is relative to the java:comp/env context. The name must be unique within the Web application. It is recommended that name is prefixed with ejb/.

For example:

<ejb-ref-name>ejb/Payroll</ejb-ref-name>

<ejb-ref-type>

Required

The ejb-ref-type element contains the expected type of the referenced enterprise bean. The ejb-ref-type element must be one of the following:

<ejb-ref-type>Entity</ejb-ref-type>
<ejb-ref-type>Session</ejb-ref-type>

<local-home>

Required

Contains the fully-qualified name of the enterprise bean's local home interface.

<local>

Required

Contains the fully-qualified name of the enterprise bean's local interface.

<ejb-link>

Optional

The ejb-link element is used in the ejb-ref or ejb-local-ref

elements to specify that an EJB reference is linked to an

EJB.

The name in the ejb-link element is composed of a path name. This path name specifies the ejb-jar containing the referenced EJB with the ejb-name of the target bean appended and separated from the path name by #.

The path name is relative to the WAR file containing the Web application that is referencing the EJB. This allows multiple EJBs with the same ejb-name to be uniquely identified.

Used in: ejb-local-ref and ejb-ref elements

Examples:

<ejb-link>EmployeeRecord</ejb-link>

<ejb-link>../products/product.jar#ProductEJB</ejb-link>

  

分享到:
评论

相关推荐

    web.xml配置参考文档-CHM格式--JAVA WEB开发必备参考文档

    《web.xml配置参考文档》是Java Web开发中的核心参考资料,主要涵盖了如何在Web应用程序中进行配置的详尽指南。此文档以CHM(Compiled Help Manual)格式提供,便于开发者快速检索和查阅。对于任何涉及Java Web、JSP...

    web.xml配置参考文档

    保准可以用,我之前下载过其他的有的不能用。所以我就自己传上来了,如果不能用,留言给我,我发给你!

    部署描述文件web.xml配置详解.doc

    ### 部署描述文件web.xml配置详解 #### 一、引言 在Java Web开发中,`web.xml`是一个非常重要的配置文件,它作为Web应用程序的部署描述符,负责管理与应用程序相关的各项配置信息。本文将深入解析`web.xml`的各项...

    web.xml文件配置参考文档 chm格式

    第一次发上来东西。希望大家多多支持,绝对能下载。

    weblogic.xml

    10. ****:映射Servlet到URL模式,扩展了Servlet的web.xml配置。 11. ****:定义文件扩展名与其对应的MIME类型。 三、weblogic.xml的实践应用 1. **性能优化**:通过调整session管理策略,可以优化服务器内存使用,...

    DWR 教程 中文API DWR.xml配置文件说明 DWR学习笔记

    "DWR中文API"是DWR库的中文参考文档,详细列出了各种接口、类和方法,是开发者查找和理解DWR功能的重要参考资料。API文档通常会包括每个类的描述、方法签名、参数说明和返回值,帮助开发者快速定位并使用所需的功能...

    Linux下配置JDK、Tomcat以及安装geowebcache各个xml配置参考.zip

    - 根据需求调整XML配置,优化缓存性能和资源使用。 以上是Linux环境下配置JDK、Tomcat以及安装GeoWebCache的基本流程。实际操作中,还需考虑系统安全、权限控制、日志管理和性能监控等细节。在配置过程中,阅读...

    tomcat的server.xml标签全解析.

    - Context是具体应用程序的容器,它对应于WAR文件或WEB-INF目录中的web.xml配置。每个Context定义了一个Web应用程序的上下文根,比如"/app1",并与特定的Host相关联。Context可以设置在Host内,也可以在Engine级别...

    JAVA WEB 开发详解:XML+XSLT+SERVLET+JSP 深入剖析与实例应用.part3

    本书不仅可以作为java web开发的学习用书,还可以作为从事java web开发的程序员的参考用书和必备手册。此外,本书的配套光盘还免费提供了价值人民币330元的java教学视频,对java语言进行了全面讲解,帮助一些不会...

    ASP.NET.2.0.XML高级编程(第3版)

    总之,《ASP.NET 2.0 XML 高级编程(第3版)》全面覆盖了ASP.NET 2.0框架下XML的高级应用,对于希望深入理解并充分利用XML来提升Web应用性能的开发者来说,是一本不可多得的参考书。同时,提供的代码示例和实践指导...

    Java解析xml配置文件,DOM4J解析xml配置文件,提供使用文档和源码下载

    在本教程中,我们将深入探讨如何使用DOM4J解析XML配置文件,并模拟处理`web.xml`中的`url-pattern`元素。 首先,让我们了解DOM4J的基本概念。DOM4J是一个基于Java的DOM模型的XML库,它扩展了标准的DOM API,增加了...

    structs的配置文件hbm.xml

    ### structs的配置文件hbm.xml知识点详解 #### 一、概述 在介绍具体的配置细节之前,我们先来了解一下struts2、Hibernate3.2以及Spring2.0这三种技术的基本概念及其整合的意义。 1. **Struts2**:是Apache基金会...

    jaxws java webservice需要的jar包

    例如,Apache CXF包含了一个完整的类库,可以处理从生成WSDL到部署Web服务的整个过程,而Metro则是Sun Microsystems(现Oracle)提供的官方参考实现。 通过理解这些核心组件及其作用,开发者能够更好地构建和维护...

    Jboss下开发EJB简介[借鉴].pdf

    2. 使用jboss.xml配置:此方法需要在ejb jar包同级目录下添加jboss.xml文件,用于定制JNDI名称。ejb-jar.xml中的会通过jboss.xml映射到JNDI中的特定名称,使得客户端能够通过自定义的名称查找EJB。 在部署过程中,...

    weblogic8.1设置简单代理转发功能注意事项

    - 实现集群分发可以通过`HttpClusterServlet`实现,具体的部署方式参见上述集群配置文章介绍的`web.xml`和`weblogic.xml`文件。 - 实现单一服务转发则通过`HttpProxyServlet`实现,配置`weblogic.xml`和`web.xml`...

    struts-config.xml

    ### Struts-config.xml配置文件详解 #### 一、引言 在Java Web开发领域中,Struts框架作为经典的MVC(Model-View-Controller)架构实现之一,为开发者提供了便捷的方式来构建可维护性和扩展性高的Web应用程序。...

    Apress.Pro.XML.Development.with.Java.Technology.Sep.2006

    XML(eXtensible Markup Language)是一种用于标记数据的语言,广泛应用于数据交换、配置文件、文档存储等多个领域。在Java平台上,XML的处理能力尤为强大,为开发者提供了丰富的API和工具。 1. **Java与XML的基础*...

    SpringSecurity3.0.x官方参考文档(英文+中文双解版)

    通过深入学习Spring Security 3.0.x 的官方参考文档,开发者能够掌握这个框架的核心概念和用法,为构建安全的企业级应用提供坚实的基础。文档的中文版有助于国内开发者更便捷地理解和使用这一强大的安全框架。

    ASP.NET 2.0.XML.高级编程(第3版)

    书中会详细讲解XML的语法、解析、验证、DOM模型、XPath查询、XSLT转换以及XML文档对象模型(XML DOM)等核心概念。 在高级编程方面,读者将了解到如何使用ASP.NET 2.0的XML Web服务(ASMX)和WCF(Windows ...

    html,css,javascript,xml,php等

    XML常用于Web服务、配置文件和数据集成。与HTML不同,XML不关心数据的显示,只关注数据的结构。 **PHP(Hypertext Preprocessor)** 是一种服务器端的脚本语言,用于创建动态网页和Web应用程序。PHP能与MySQL等...

Global site tag (gtag.js) - Google Analytics