Where is web.xml

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. The external resource name is mapped to the actual location name of the resource at deployment time in the WebLogic-specific deployment descriptor weblogic. The following table describes the elements you can define within a resource-ref element. 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. The Java type of the resource that corresponds to the reference name. Use the full package name of the Java type. See login-config. Specifies whether connections obtained through the given resource manager connection factory reference can be shared.

For detailed instructions and an example on configuring security in Web applications, see Securing WebLogic Resources. The following table describes the elements you can define within a security-constraint element.

Defines the components of the Web application to which this security constraint is applied. Defines which groups or principals have access to the collection of web resources defined in this security constraint.

See also auth-constraint. See also user-data-constraint. 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. 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.

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. NONE— The application does not require any transport guarantees. 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.

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. Specifies the method used to authenticate the user. Possible values:. BASIC —uses browser authentication. This is the default value. The name of the realm that is referenced to authenticate the user credentials.

For more information, see Managing WebLogic Security. 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. See form-login-config. This is an element within the login-config. The URI of a Web resource relative to the document root, used to authenticate the user.

The URI of a Web resource relative to the document root, sent to the user in response to a failed authentication login. The following table describes the elements you can define within a security-role element. The role name.

The name you use here must have a corresponding entry in the WebLogic-specific deployment descriptor, weblogic. For more information, see security-role-assignment. 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. 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.

The following table describes the elements you can define within an ejb-ref element. Custom machine learning model training and development. Video classification and recognition using machine learning. Options for every business to train deep learning and machine learning models cost-effectively. Conversation applications and systems development suite for virtual agents. Service for training ML models with structured data.

A single interface for your data, analytics, and machine learning workflow. API Management. Manage the full life cycle of APIs anywhere with visibility and control.

API-first integration to connect existing data and applications. Solution to bridge existing care systems and apps on Google Cloud. No-code development platform to build and extend applications.

Develop, deploy, secure, and manage APIs with a fully managed gateway. Serverless application platform for apps and back ends. Server and virtual machine migration to Compute Engine. Compute instances for batch jobs and fault-tolerant workloads.

Reinforced virtual machines on Google Cloud. Dedicated hardware for compliance, licensing, and management. Infrastructure to run specialized workloads on Google Cloud. Usage recommendations for Google Cloud products and services. Fully managed, native VMware Cloud Foundation software stack. Registry for storing, managing, and securing Docker images. Container environment security for each stage of the life cycle. Solution for running build steps in a Docker container.

Containers with data science frameworks, libraries, and tools. Containerized apps with prebuilt deployment and unified billing. Package manager for build artifacts and dependencies. Components to create Kubernetes-native cloud-based software. IDE support to write, run, and debug Kubernetes applications. Platform for BI, data applications, and embedded analytics.

Messaging service for event ingestion and delivery. Service for running Apache Spark and Apache Hadoop clusters. Data integration for building and managing data pipelines. Workflow orchestration service built on Apache Airflow. Service to prepare data for analysis and machine learning. Intelligent data fabric for unifying data management across silos. Metadata service for discovering, understanding, and managing data.

Service for securely and efficiently exchanging data analytics assets. Cloud-native wide-column database for large scale, low-latency workloads. Cloud-native document database for building rich mobile, web, and IoT apps. In-memory database for managed Redis and Memcached.

Cloud-native relational database with unlimited scale and Serverless, minimal downtime migrations to Cloud SQL. Infrastructure to run specialized Oracle workloads on Google Cloud. NoSQL database for storing and syncing data in real time. Serverless change data capture and replication service. Universal package manager for build artifacts and dependencies. Continuous integration and continuous delivery platform. Service for creating and managing Google Cloud resources. Command line tools and libraries for Google Cloud.

Cron job scheduler for task automation and management. Private Git repository to store, manage, and track code. Task management service for asynchronous task execution. Private Docker storage for container images on Google Cloud. Fully managed continuous delivery to Google Kubernetes Engine.

Full cloud control from Windows PowerShell. Healthcare and Life Sciences. Solution for bridging existing care systems and apps on Google Cloud.

Tools for managing, processing, and transforming biomedical data. Real-time insights from unstructured medical text. Integration that provides a serverless development platform on GKE. Tool to move workloads and existing applications to GKE. Service for executing builds on Google Cloud infrastructure. Traffic control pane and management for open service mesh.

API management, development, and security platform. Fully managed hardware and software solutions for the edge and data centers. Internet of Things. IoT device management, integration, and connection service. Automate policy and security for your deployments. Dashboard to view and export your Google Cloud carbon emissions report. Programmatic interfaces for Google Cloud services. Web-based interface for managing and monitoring cloud apps.

App to manage Google Cloud services from your mobile device. Interactive shell environment with a built-in command line. Kubernetes add-on for managing Google Cloud resources. Tools for monitoring, controlling, and optimizing your costs. Tools for easily managing performance, security, and cost.

Service catalog for admins managing internal enterprise solutions. 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. Table A env-entry Elements. 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. The following table describes the elements you can define within an ejb-ref element. Table A ejb-ref Elements.

The name of the EJB used in the Web application. For more information, see ejb-reference-description. A security role whose security context is applied to the referenced EJB. The ejb-local-ref element is used for the declaration of a reference to an enterprise bean's local home. The declaration consists of:. 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 following table describes the elements you can define within an ejb-local-ref element. Table A ejb-local-ref Elements. Contains the name of an EJB reference. The name must be unique within the Web application. 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:. The ejb-link element is used in the ejb-ref or ejb-local-ref e lements 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. This allows multiple EJBs with the same ejb-name to be uniquely identified. However, the version attributed must be set to 2. The following table describes the elements you can define within an web-app element. Table A web-app Elements. All Servlet deployment descriptors must indicate the 2. The following table describes the elements you can define within an icon element.

The following table describes the elements you can define within a filter element. The following table describes the elements you can define within a servlet element. Default value: 60 Maximum value: Integer. For more information, see session-descriptor.

For more information, see Configuring Welcome Files. The following table describes the elements you can define within a taglib element. Valid values: Shareable Unshareable. See also user-data-constraint. This is an element within the security-constraint. This is the default value. Can be set to one of the following Java types: java.

Boolean java. String java. Integer java. Double java. 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.

Used in: ejb-local-ref and ejb-ref elements. Defines code set behavior for non-unicode operations. Sets the default servlet for the Web application. A short name intended to be displayed by GUI tools. The fully-qualified class name of the filter. The name of a servlet which, if called, causes this filter to execute.

Name of the class that responds to a Web application event. A text description of the servlet. The fully-qualified class name of the servlet. Defines the name of this attribute.

Defines a String value for this attribute. Text description of the initialization attribute. Defines the name of the security role or principal that is used in the servlet code.

A string describing an extension, for example: txt. What else should I know about web. Improve this question. Sensei 1 1 silver badge 10 10 bronze badges. Ravi Gupta Ravi Gupta 4, 12 12 gold badges 50 50 silver badges 84 84 bronze badges. Add a comment. Active Oldest Votes. Is there any configuration parameter which should be avoided like plague? No, such things are not configured at the application level but at the container level.

Improve this answer. Pascal Thivent Pascal Thivent k gold badges silver badges bronze badges. What all should I know about web. Civil Disobedient Civil Disobedient 1, 11 11 silver badges 5 5 bronze badges.

No, there isn't anything that should be avoided The parameters related to performance are not in web. Bozho Bozho k gold badges silver badges bronze badges.