July 2011 - jbossweb-commits - Jboss List Archives

JBossWeb SVN: r1777 - trunk/webapps/docs/appdev.

by jbossweb-commits＠lists.jboss.org

Author: jfrederic.clere(a)jboss.com Date: 2011-07-08 11:19:03 -0400 (Fri, 08 Jul 2011) New Revision: 1777 Modified: trunk/webapps/docs/appdev/jbossweb.xml Log: Add missing elements. Modified: trunk/webapps/docs/appdev/jbossweb.xml =================================================================== --- trunk/webapps/docs/appdev/jbossweb.xml 2011-07-08 12:02:23 UTC (rev 1776) +++ trunk/webapps/docs/appdev/jbossweb.xml 2011-07-08 15:19:03 UTC (rev 1777) @@ -34,6 +34,54 @@ <attributes> + <attribute name="env-entry" required="false"> + An element <code>env-entry</code> as defined in J2EE + </attribute> + + <attribute name="ejb-ref" required="false"> + An element <code>ejb-ref</code> as defined in J2EE + </attribute> + + <attribute name="ejb-local-ref" required="false"> + An element <code>ejb-local-ref</code> as defined in J2EE + </attribute> + + <attribute name="service-ref" required="false"> + An element <code>service-ref</code> as defined in J2EE + </attribute> + + <attribute name="resource-ref" required="false"> + An element <code>resource-ref</code> as defined in J2EE + </attribute> + + <attribute name="resource-env-ref" required="false"> + An element <code>resource-env-ref</code> as defined in J2EE + </attribute> + + <attribute name="message-destination-ref" required="false"> + An element <code>message-destination-ref</code> as defined in J2EE + </attribute> + + <attribute name="persistence-context-ref" required="false"> + An element <code>persistence-context-ref</code> as defined in J2EE + </attribute> + + <attribute name="persistence-unit-ref" required="false"> + An element <code>persistence-unit-ref</code> as defined in J2EE + </attribute> + + <attribute name="post-construct" required="false"> + An element <code>post-construct</code> as defined in J2EE + </attribute> + + <attribute name="pre-destroy" required="false"> + An element <code>pre-destroy</code> as defined in J2EE + </attribute> + + <attribute name="data-source" required="false"> + An element <code>data-source</code> as defined in J2EE + </attribute> + <attribute name="context-root" required="false"> Root context of the web-app. It defaults to the filename of the deployememt without the .war suffix </attribute>

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1776 - trunk/webapps/docs/appdev.

by jbossweb-commits＠lists.jboss.org

Author: jfrederic.clere(a)jboss.com Date: 2011-07-08 08:02:23 -0400 (Fri, 08 Jul 2011) New Revision: 1776 Modified: trunk/webapps/docs/appdev/jbossweb.xml Log: Add listener-type. Modified: trunk/webapps/docs/appdev/jbossweb.xml =================================================================== --- trunk/webapps/docs/appdev/jbossweb.xml 2011-07-07 14:45:32 UTC (rev 1775) +++ trunk/webapps/docs/appdev/jbossweb.xml 2011-07-08 12:02:23 UTC (rev 1776) @@ -121,6 +121,22 @@ list of <code>condition</code>Elements. See condition below. </attribute> + <attribute name="listener-type" required="true"> + Tell what kind of listener to add to the Context of the webapp: + <ul> + <li>CONTAINER: Add a ContainerListener to the Context. + </li> + <li>LIFECYCLE: Add a LifecycleListener to the Context. + </li> + <li>SERVLET_INSTANCE: Add a InstanceListener to the Context. + </li> + <li>SERVLET_CONTAINER: Add a WrapperListener to the Context. + </li> + <li>SERVLET_LIFECYCLE: Add a WrapperLifecycle to the Context. + </li> + </ul> + </attribute> + <attribute name="module" required="true"> name of the module containing the listener class. </attribute> @@ -138,7 +154,7 @@ <subsection name="valve"> <code>valve</code> describes a valve of the webapp. - Like <code>listener</code> has <code>class-name</code>, <code>module</code> and <code><param/></code> + Similar to the <code>listener</code> has <code>class-name</code>, <code>module</code> and <code><param/></code> </subsection>

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1775 - trunk/webapps/docs/appdev.

by jbossweb-commits＠lists.jboss.org

Author: jfrederic.clere(a)jboss.com Date: 2011-07-07 10:45:32 -0400 (Thu, 07 Jul 2011) New Revision: 1775 Added: trunk/webapps/docs/appdev/jbossweb.xml Log: Add description of jboss-web.xml Added: trunk/webapps/docs/appdev/jbossweb.xml =================================================================== --- trunk/webapps/docs/appdev/jbossweb.xml (rev 0) +++ trunk/webapps/docs/appdev/jbossweb.xml 2011-07-07 14:45:32 UTC (rev 1775) @@ -0,0 +1,155 @@ +<?xml version="1.0"?> +<!DOCTYPE document [ + <!ENTITY project SYSTEM "project.xml"> +]> +<document url="jbossweb.html"> + + &project; + + <properties> + <author email="jfclere(a)gmail.com">Jean-Frederic Clere</author> + <title>JBoss Web Application Deployment Descriptor</title> + </properties> + +<body> + + +<section name="Introduction"> + + The jboss-web.xml is an XML file containing + the JBossWeb specific behaviour of a webapp. It replaces + the Tomcat <code>context.xml</code> file. + You need only to use it if you want properties and behaviour + that extent the <code>web.xml</code> of the Servlet 3.0 specifications. + +</section> + + +<section name="Attributes"> + + <subsection name="Common Attributes"> + + The jboss-web.xml + supports the following attributes: + + <attributes> + + <attribute name="context-root" required="false"> + Root context of the web-app. It defaults to the filename of the deployememt without the .war suffix + </attribute> + + <attribute name="virtual-host" required="false"> + Name of the <code>virtual-host</code> the application will accept request from. + </attribute> + + <attribute name="annotation" required="false"> + Element describing an <code>annotation</code> of the webapp. + </attribute> + + <attribute name="listener" required="false"> + Element describing a <code>listener</code> of the webapp. + </attribute> + + <attribute name="session-config" required="false"> + Element describing the <code>session-config</code> of the webapp. + </attribute> + + <attribute name="valve" required="false"> + Element describing a <code>valve</code> of the webapp. + </attribute> + + <attribute name="overlay" required="false"> + name of the overlay to add the webapp + </attribute> + + <attribute name="security-domain" required="false"> + Name of the security domain to use for the webapp + </attribute> + + <attribute name="security-role" required="false"> + Element describing a <code>security-role</code> of the webapp. + </attribute> + + <attribute name="jacc-star-role-allow" required="false"> + NOT YET SUPPORTED: See <a href="https://issues.jboss.org/browse/JBMETA-134">JBMETA-134</a> + </attribute> + + <attribute name="disable-cross-context" required="false"> + Prevent application to call another application context. + Default: <code>true</code> + </attribute> + + </attributes> + + </subsection> + + +</section> + + +<section name="Nested Components"> + + <subsection name="annotation"> + + <code>annotation</code>describes how the annotation of the webapp + + <attributes> + <attribute name="class-name" required="false"> + name of class of the annotation. + </attribute> + + <attribute name="servlet-security" required="false"> + <code>servlet-security</code> Element (like @ServletSecurity) + </attribute> + + <attribute name="run-as" required="false"> + <code>servlet-security</code> Element (like @RunAs) + </attribute> + + <attribute name="multi-part" required="false"> + <code>servlet-security</code> Element (like @MultipartConfig) + </attribute> + </attributes> + </subsection> + + <subsection name="listener"> + <code>listener</code>describes a listener of the webapp. + + <attributes> + <attribute name="class-name" required="true"> + name of class of the listener. + list of <code>condition</code>Elements. See condition below. + </attribute> + + <attribute name="module" required="true"> + name of the module containing the listener class. + </attribute> + + <attribute name="param" required="true"> + A parameter: <code>param-name</code> and <code>param-name</code> + </attribute> + </attributes> + </subsection> + + <subsection name="session-config"> + <code>session-config</code> describes the session configuration of the web-app that is like + the <code><session-config></code> of the <code>web.xml</code>. It is here for compatibility + </subsection> + + <subsection name="valve"> + <code>valve</code> describes a valve of the webapp. + Like <code>listener</code> has <code>class-name</code>, <code>module</code> and <code><param/></code> + + </subsection> + + <subsection name="security-role"> + <code>security-role</code> describes a securite role of the web-app that is like + the <code><security-role;</code> of the <code>web.xml</code>. It is here for compatibility + </subsection> +</section> + + +</body> + + +</document>

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1774 - in trunk/webapps/docs: appdev and 1 other directories.

by jbossweb-commits＠lists.jboss.org

Author: jfrederic.clere(a)jboss.com Date: 2011-07-06 10:39:25 -0400 (Wed, 06 Jul 2011) New Revision: 1774 Modified: trunk/webapps/docs/appdev/deployment.xml trunk/webapps/docs/appdev/installation.xml trunk/webapps/docs/appdev/introduction.xml trunk/webapps/docs/appdev/processes.xml trunk/webapps/docs/appdev/source.xml trunk/webapps/docs/building.xml trunk/webapps/docs/config/host.xml Log: Arrange the webapp doc example... Note that webapp itself need to be arranged too. Modified: trunk/webapps/docs/appdev/deployment.xml =================================================================== --- trunk/webapps/docs/appdev/deployment.xml 2011-07-06 11:30:20 UTC (rev 1773) +++ trunk/webapps/docs/appdev/deployment.xml 2011-07-06 14:39:25 UTC (rev 1774) @@ -8,6 +8,7 @@ <properties> <author email="craigmcc(a)apache.org">Craig R. McClanahan</author> + <author email="jfclere(a)apache.org">Jean-Frederic Clere</author> <title>Deployment</title> </properties> @@ -36,7 +37,7 @@ files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section -of this manual describes deployment on Tomcat). Thus, if the +of this manual describes deployment on JBossWeb). Thus, if the system administrator assigns your application to the context path <code>/catalog</code>, then a request URI referring to <code>/catalog/index.html</code> will retrieve the <code>index.html</code> @@ -49,7 +50,7 @@ To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web -application (that is, the files that Tomcat actually uses when executing +application (that is, the files that JBossWeb actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory: @@ -68,6 +69,11 @@ security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection. </li> +<li>/WEB-INF/jboss-web.xml - The JBoss Web Application Deployment + Descriptor for your application. This is an XML file describing the + JBossWeb extensions to /WEB-INF/web.xml. + See <a href="./jbossweb.html">jboss-web.xml</a> for more. + </li> <li>/WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined @@ -102,30 +108,14 @@ <section name="Shared Library Files"> -Like most servlet containers, Tomcat 5 also supports mechanisms to install -library JAR files (or unpacked classes) once, and make them visible to all -installed web applications (without having to be included inside the web -application itself. The details of how Tomcat locates and shares such -classes are described in the -<a href="../class-loader-howto.html">Class Loader HOW-TO</a> documentation. -For the purposes of our discussion, there are two locations that are commonly -used within a Tomcat 5 installation for shared code: -<ul> -<li>$CATALINA_HOME/common/lib - JAR files placed here are - visible both to web applications and internal Tomcat code. This is a - good place to put JDBC drivers that are required for both your application - and internal Tomcat use (such as for a JDBCRealm). - </li> -<li>$CATALINA_BASE/shared/lib - JAR files placed here are - visible to all web applications, but not to internal Tomcat code. This - is the right place for shared libraries that are specific to your - application. </li> -</ul> +If you want to share libraries between webapps put them in a ear file +with the libraries you want to share. + -Out of the box, a standard Tomcat 5 installation includes a variety +Out of the box, a standard JBossWeb installation includes a variety of pre-installed shared library files, including: <ul> -<li>The Servlet 2.4 and JSP 2.0 APIs that are fundamental +<li>The Servlet 3.0 and JSP 2.2 APIs that are fundamental to writing servlets and JavaServer Pages. </li> <li>An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of @@ -137,16 +127,6 @@ <section name="Web Application Deployment Descriptor"> - <blockquote> - The description below uses the variable name $CATALINA_HOME - to refer to the directory into which you have installed Tomcat 5, - and is the base directory against which most relative paths are - resolved. However, if you have configured Tomcat 5 for multiple - instances by setting a CATALINA_BASE directory, you should use - $CATALINA_BASE instead of $CATALINA_HOME for each of these - references. - </blockquote> - As mentioned above, the <code>/WEB-INF/web.xml</code> file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about @@ -155,7 +135,7 @@ deployed). The complete syntax and semantics for the deployment descriptor is defined -in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it +in Chapter 13 of the Servlet API Specification, version 3.0. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a <a href="web.xml.txt" target="_new">basic web.xml file</a> @@ -164,7 +144,7 @@ NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and -Tomcat 5 enforces the rules defined here when processing your application's +JBossWeb enforces the rules defined here when processing your application's <code>/WEB-INF/web.xml</code> file. In particular, you must enter your descriptor elements (such as <code><filter></code>, <code><servlet></code>, and <code><servlet-mapping></code> in @@ -173,71 +153,49 @@ </section> -<section name="Tomcat Context Descriptor"> +<section name="JBoss Web Application Deployment"> - <blockquote> - The description below uses the variable name $CATALINA_HOME - to refer to the directory into which you have installed Tomcat 5, - and is the base directory against which most relative paths are - resolved. However, if you have configured Tomcat 5 for multiple - instances by setting a CATALINA_BASE directory, you should use - $CATALINA_BASE instead of $CATALINA_HOME for each of these - references. - </blockquote> - -A /META-INF/context.xml file can be used to define Tomcat specific +A /WEB-INF/jboss-web.xml file can be used to define JBossWeb specific configuration options, such as loggers, data sources, session manager -configuration and more. This XML file must contain one Context element, which -will be considered as if it was the child of the Host element corresponding -to the Host to which the The Tomcat configuration documentation contains -information on the Context element. +configuration and more. This XML file is describe in <a href="./jbossweb.html">jboss-web.xml</a>. + </section> -<section name="Deployment With Tomcat 5"> +<section name="Deployment With JBossWeb"> In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. -A web application can be deployed in Tomcat by one of the following +A web application can be deployed in JBossWeb by one of the following approaches: <ul> <li>Copy unpacked directory hierarchy into a subdirectory in directory - <code>$CATALINA_HOME/webapps/</code>. Tomcat will assign a + <code>${jboss.server.base.dir}/standalone/deployments/</code>. JBossWeb will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the <code>build.xml</code> file that we construct, because it is the quickest and easiest approach - during development. Be sure to restart Tomcat after installing or - updating your application. + during development. + you have to create a file named like <code>myapp.war.dodeploy</code> to + start the deployement scanner on the myapp.war directory. </li> <li>Copy the web application archive file into directory - <code>$CATALINA_HOME/webapps/</code>. When Tomcat is started, it will + <code>${jboss.server.base.dir}/standalone/deployments/</code>. When JBossWeb is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing - Tomcat installation. NOTE - If you use this approach, - and wish to update your application later, you must both replace the - web application archive file AND delete the expanded - directory that Tomcat created, and then restart Tomcat, in order to reflect - your changes. + JBossWeb installation. The web-app will be automaticaly deployed. </li> -<li>Use the Tomcat 5 "Manager" web application to deploy and undeploy - web applications. Tomcat 5 includes a web application, deployed - by default on context path <code>/manager</code>, that allows you to - deploy and undeploy applications on a running Tomcat server without - restarting it. See the administrator documentation (TODO: hyperlink) - for more information on using the Manager web application. </li> -<li>Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 - includes a set of custom task definitions for the <code>Ant</code> - build tool that allow you to automate the execution of commands to the - "Manager" web application. These tasks are used in the Tomcat deployer. +<li>Use the command line or the Web Management Interface of AS7. + web applications. For example something like: +<source> +[standalone@localhost:9999 /] deploy /home/jfclere/jbossweb_sandbox/webapps/myapp.war +'myapp.war' deployed successfully. +</source> + In the above example <code>myapp.war</code> will be deployed under the context <code>/myapp</code> </li> -<li>Use the Tomcat Deployer. Tomcat 5 includes a packaged tool - bundling the Ant tasks, and can be used to automatically precompile JSPs - which are part of the web application before deployment to the server. - </li> </ul> Deploying your app on other servlet containers will be specific to each Modified: trunk/webapps/docs/appdev/installation.xml =================================================================== --- trunk/webapps/docs/appdev/installation.xml 2011-07-06 11:30:20 UTC (rev 1773) +++ trunk/webapps/docs/appdev/installation.xml 2011-07-06 14:39:25 UTC (rev 1774) @@ -9,6 +9,7 @@ <properties> <author email="craigmcc(a)apache.org">Craig R. McClanahan</author> <author email="yoavs(a)apache.org">Yoav Shapira</author> + <author email="jfclere(a)apache.org">Jean-Frederic Clere</author> <title>Installation</title> </properties> @@ -17,13 +18,13 @@ <section name="Installation"> -In order to use Tomcat 6 for developing web applications, you must first +In order to use AS7 (JBossWeb) for developing web applications, you must first install it (and the software it depends on). The required steps are outlined in the following subsections. <subsection name="JDK"> -Tomcat 6.0 was designed to run on J2SE 5.0. +AS7 was designed to run on J2SE 6.0. Compatible JDKs for many platforms (or links to where they can be found) @@ -32,18 +33,14 @@ </subsection> -<subsection name="Tomcat"> +<subsection name="AS7"> -Binary downloads of the Tomcat server are available from -<a href="http://tomcat.apache.org/download-60.cgi">http://tomcat.apache.org/download-60.cgi</a>. +Binary downloads of the AS7 server are available from +<a href="http://www.jboss.org/jbossas/downloads/">JBoss Application Server downloads</a>. This manual assumes you are using the most recent release -of Tomcat 6. Detailed instructions for downloading and installing -Tomcat 6 are available <a href="../setup.html">here</a>. +of AS7. Detailed instructions for downloading and installing +AS7 are available <a href="https://docs.jboss.org/author/display/AS7/Getting+Started+Developing+Appl...">here</a>. -In the remainder of this manual, example shell scripts assume that you have -set an environment variable <code>CATALINA_HOME</code> that contains the -pathname to the directory in which Tomcat 6 has been installed. - </subsection> Modified: trunk/webapps/docs/appdev/introduction.xml =================================================================== --- trunk/webapps/docs/appdev/introduction.xml 2011-07-06 11:30:20 UTC (rev 1773) +++ trunk/webapps/docs/appdev/introduction.xml 2011-07-06 14:39:25 UTC (rev 1774) @@ -8,6 +8,7 @@ <properties> <author email="craigmcc(a)apache.org">Craig R. McClanahan</author> + <author email="jfclere(a)apache.org">Jean-Frederic Clere</author> <title>Introduction</title> </properties> @@ -37,6 +38,9 @@ Environment (IDE) tool, you will need to adapt the advice given here to the details of your particular environment. +See <a href="https://docs.jboss.org/author/display/AS7/Getting+Started+Developing+Appl...">Getting Started Developing Applications Guide</a> If you want to use Eclipse. + + </section> @@ -44,10 +48,10 @@ The following links provide access to selected sources of online information, documentation, and software that is useful in developing -web applications with Tomcat. +web applications with JBossWeb. <ul> <li><a href="http://java.sun.com/products/jsp/download.html">http://java.sun.com/products/jsp/download.html</a> - - JavaServer Pages (JSP) Specfication, Version 2.0. Describes + JavaServer Pages (JSP) Specfication, Version 2.2. Describes the programming environment provided by standard implementations of the JavaServer Pages (JSP) technology. In conjunction with the Servlet API Specification (see below), this document describes @@ -57,7 +61,7 @@ API Documentation is included in the specification, and with the Tomcat download. </li> <li><a href="http://java.sun.com/products/servlet/download.html">http://java.sun.com/products/servlet/download.html</a> - - Servlet API Specification, Version 2.4. Describes the + Servlet API Specification, Version 3.0. Describes the programming environment that must be provided by all servlet containers conforming to this specification. In particular, you will need this document to understand the web application @@ -74,7 +78,6 @@ chapters on servlet and JSP design are useful even when your application does not require other J2EE platform components. </li> -<li>TODO -- Add more entries here!</li> </ul> </section> Modified: trunk/webapps/docs/appdev/processes.xml =================================================================== --- trunk/webapps/docs/appdev/processes.xml 2011-07-06 11:30:20 UTC (rev 1773) +++ trunk/webapps/docs/appdev/processes.xml 2011-07-06 14:39:25 UTC (rev 1774) @@ -17,7 +17,7 @@ <section name="Development Processes"> Although application development can take many forms, this manual proposes -a fairly generic process for creating web applications using Tomcat. The +a fairly generic process for creating web applications using JBossWeb. The following sections highlight the commands and tasks that you, as the developer of the code, will perform. The same basic approach works when you have multiple programmers involved, as long as you have an appropriate source code @@ -31,31 +31,6 @@ will need to figure out the corresponding commands for your system. -<subsection name="One-Time Setup of Ant and Tomcat for Development"> - -In order to take advantage of the special Ant tasks that interact with the -Manager web application, you need to perform the following tasks -once (no matter how many web applications you plan to develop). -<ul> -<li>Configure the Ant custom tasks. The implementation code for the - Ant custom tasks is in a JAR file named - <code>$CATALINA_HOME/server/lib/catalina-ant.jar</code>, which must be - copied in to the <code>lib</code> directory of your Ant installation. - </li> -<li>Define one or more Tomcat users. The Manager web - application runs under a security constraint that requires a user to be - logged in, and have the security role <code>manager</code> assigned to - him or her. How such users are defined depends on which Realm you have - configured in Tomcat's <code>conf/server.xml</code> file -- see the - <a href="../realm-howto.html">Realm Configuration HOW-TO</a> for more - information. You may define any number of users (with any username - and password that you like) with the <code>manager</code> role. - </li> -</ul> - -</subsection> - - <subsection name="Create Project Source Code Directory"> The first step is to create a new project source directory, and customize @@ -111,7 +86,7 @@ directory. The supported properties are listed in the comments inside the sample <code>build.xml</code> script. At a minimum, you will generally need to define the <code>catalina.home</code> property defining where -Tomcat 5 is installed, and the manager application username and password. +JBossWeb is installed, and the manager application username and password. You might end up with something like this: <source> # Context path to install this application on @@ -120,9 +95,6 @@ # Tomcat 5 installation directory catalina.home=/usr/local/apache-tomcat-6.0 -# Manager webapp username and password -manager.username=myusername -manager.password=mypassword </source> In general, you will not want to check the @@ -224,12 +196,12 @@ <subsection name="Test Your Web Application"> -To test your application, you will want to install it under Tomcat. The +To test your application, you will want to install it under JBossWeb. The quickest way to do that is to use the custom Ant tasks that are included in the sample <code>build.xml</code> script. Using these commands might follow a pattern like this: <ul> -<li>Start Tomcat 5 if needed. If Tomcat 5 is not already running, +<li>Start JBossWeb if needed. If JBossWeb is not already running, you will need to start it in the usual way. </li> <li>Compile your application. Use the <code>ant compile</code> @@ -237,9 +209,9 @@ sure that there are no compilation errors. </li> <li>Install the application. Use the <code>ant install</code> - command. This tells Tomcat to immediately start running your app on + command. This tells JBossWeb to immediately start running your app on the context path defined in the <code>app.path</code> build property. - Tomcat does NOT have to be restarted for this to + JBossWeb does NOT have to be restarted for this to take effect. </li> <li>Test the application. Using your browser or other testing tools, test the functionality of your application. @@ -251,7 +223,7 @@ be available to be saved (via <code>cvs commit</code>) later on -- the output build directory is deleted and recreated as necessary. </li> -<li>Reload the application. Tomcat will recognize changes in +<li>Reload the application. JBossWeb will recognize changes in JSP pages automatically, but it will continue to use the old versions of any servlet or JavaBean classes until the application is reloaded. You can trigger this by executing the <code>ant reload</code> command. Modified: trunk/webapps/docs/appdev/source.xml =================================================================== --- trunk/webapps/docs/appdev/source.xml 2011-07-06 11:30:20 UTC (rev 1773) +++ trunk/webapps/docs/appdev/source.xml 2011-07-06 14:39:25 UTC (rev 1774) @@ -8,6 +8,7 @@ <properties> <author email="craigmcc(a)apache.org">Craig R. McClanahan</author> + <author email="jfclere(a)apache.org">Jean-Frederic Clere</author> <title>Source Organization</title> </properties> @@ -17,13 +18,9 @@ <section name="Directory Structure"> <blockquote> - The description below uses the variable name $CATALINA_HOME - to refer to the directory into which you have installed Tomcat 5, - and is the base directory against which most relative paths are - resolved. However, if you have configured Tomcat 5 for multiple - instances by setting a CATALINA_BASE directory, you should use - $CATALINA_BASE instead of $CATALINA_HOME for each of these - references. + The description below uses the variable name ${jboss.server.base.dir} + to refer to the directory into which you have installed AS7. + </blockquote> A key recommendation of this manual is to separate the directory @@ -88,11 +85,10 @@ <li>build/ - When you execute a default build (<code>ant</code>), this directory will contain an exact image of the files in the web application archive for this application. - Tomcat 5 allows you to deploy an application in an unpacked + JBossWeb allows you to deploy an application in an unpacked directory like this, either by copying it to the - <code>$CATALINA_HOME/webapps</code> directory, or by installing - it via the "Manager" web application. The latter approach is very - useful during development, and will be illustrated below. + <code>$jboss.server.base.dir}/standalone/deployments</code> directory, or by installing + it via the command line or the Web Management Interface of AS7. </li> <li>dist/ - When you execute the <code>ant dist</code> target, this directory will be created. It will create an exact image @@ -137,12 +133,6 @@ developer can be customized on a per-application basis, or defaulted to "standard" build properties stored in the developer's home directory. - In many cases, your development system administrator will have already - installed the required JAR files into Tomcat 5's <code>common/lib</code> - or <code>shared/lib</code> directories. If this has been done, you need - to take no actions at all - the example <code>build.xml</code> file - automatically constructs a compile classpath that includes these files. - </subsection> </section> @@ -276,22 +266,21 @@ </ul> For interactive development and testing of your web application using -Tomcat 5, the following additional targets are defined: +JBossWeb 5, the following additional targets are defined: <ul> -<li>install - Tell the currently running Tomcat 5 to make +<li>install - Tell the currently running JBossWeb to make the application you are developing immediately available for execution - and testing. This action does not require Tomcat 5 to be restarted, but - it is also not remembered after Tomcat is restarted the next time. + and testing. This action does not require JBossWeb to be restarted. </li> <li>reload - Once the application is installed, you can continue to make changes and recompile using the <code>compile</code> - target. Tomcat 5 will automatically recognize changes made to JSP pages, - but not to servlet or JavaBean classes - this command will tell Tomcat + target. JBossWeb will automatically recognize changes made to JSP pages, + but not to servlet or JavaBean classes - this command will tell JBossWeb to restart the currently installed application so that such changes are recognized. </li> <li>remove - When you have completed your development and - testing activities, you can optionally tell Tomcat 5 to remove this + testing activities, you can optionally tell JBossWeb to remove this application from service. </li> </ul> Modified: trunk/webapps/docs/building.xml =================================================================== --- trunk/webapps/docs/building.xml 2011-07-06 11:30:20 UTC (rev 1773) +++ trunk/webapps/docs/building.xml 2011-07-06 14:39:25 UTC (rev 1774) @@ -94,7 +94,7 @@ NOTE: That build jar files in output/jars, the <code>jbossweb.jar</code> -have to be copied in <code>${jboss.server.data.dir)/modules/org/jboss/as/web/main</code> to be +have to be copied in <code>${jboss.server.base.dir)/modules/org/jboss/as/web/main</code> to be used in AS7. Modified: trunk/webapps/docs/config/host.xml =================================================================== --- trunk/webapps/docs/config/host.xml 2011-07-06 11:30:20 UTC (rev 1773) +++ trunk/webapps/docs/config/host.xml 2011-07-06 14:39:25 UTC (rev 1774) @@ -100,7 +100,7 @@ <attributes> <attribute name="relative-to" required="false"> directory location based on the global path configuration in the domain model. - If not specified, it defaults to the JBoss Application data directory (jboss.server.data.dir). + If not specified, it defaults to the JBoss Application data directory (jboss.server.base.dir). </attribute> <attribute name="path" required="false">

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1773 - branches.

by jbossweb-commits＠lists.jboss.org

Author: mmusaji Date: 2011-07-06 07:30:20 -0400 (Wed, 06 Jul 2011) New Revision: 1773 Added: branches/JBOSSWEB_2_0_0_GA_CP08_JBPAPP-6794/ Log: Create JBPAPP-6794 patch branch from JBossWeb_2_0_0_GA_CP08 tag

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1771 - branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/webapps/docs.

by jbossweb-commits＠lists.jboss.org

Author: bmaxwell Date: 2011-07-05 13:13:17 -0400 (Tue, 05 Jul 2011) New Revision: 1771 Modified: branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/webapps/docs/changelog.xml Log: [JBPAPP-6778] JBWEB148: Possible NPE on set/removeAttribute, JBWEB185: Fix thread safety in two EL caches Modified: branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/webapps/docs/changelog.xml =================================================================== --- branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/webapps/docs/changelog.xml 2011-07-05 17:12:56 UTC (rev 1770) +++ branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/webapps/docs/changelog.xml 2011-07-05 17:13:17 UTC (rev 1771) @@ -15,6 +15,30 @@ </properties> <body> +<section name="JBoss Web 2.1.11.GA (remm)"> + <subsection name="Catalina"> + <changelog> + <fix> + <jira>148</jira>: Fix possible NPE on request.set/removeAttribute. (remm) + </fix> + </changelog> + </subsection> + <subsection name="Coyote"> + <changelog> + <fix> + <jboss-jira>JBPAPP-5293</jboss-jira>: ConcurrentModificationException in HandshakeCompletedNotify-Thread. (remm) + </fix> + </changelog> + </subsection> + <subsection name="Jasper"> + <changelog> + <fix> + <jira>185</jira>: Fix cache thread safety issue for EL expression builder. + Patch submitted by Takayoshi Kimura. (remm) + </fix> + </changelog> + </subsection> +</section> <section name="JBoss Web 2.1.10.GA (remm)"> <subsection name="Coyote">

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1770 - in branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java: org/apache/catalina/connector and 2 other directories.

by jbossweb-commits＠lists.jboss.org

Author: bmaxwell Date: 2011-07-05 13:12:56 -0400 (Tue, 05 Jul 2011) New Revision: 1770 Modified: branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/javax/el/BeanELResolver.java branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/catalina/connector/Request.java branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/el/lang/ExpressionBuilder.java branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/el/util/ConcurrentCache.java Log: [JBPAPP-6778] JBWEB148: Possible NPE on set/removeAttribute, JBWEB185: Fix thread safety in two EL caches Modified: branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/javax/el/BeanELResolver.java =================================================================== --- branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/javax/el/BeanELResolver.java 2011-07-05 17:08:41 UTC (rev 1769) +++ branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/javax/el/BeanELResolver.java 2011-07-05 17:12:56 UTC (rev 1770) @@ -25,6 +25,8 @@ import java.lang.reflect.InvocationTargetException; import java.lang.reflect.Method; import java.lang.reflect.Modifier; +import java.security.AccessController; +import java.security.PrivilegedAction; import java.util.Arrays; import java.util.HashMap; import java.util.Iterator; @@ -34,10 +36,29 @@ public class BeanELResolver extends ELResolver { + private static final int CACHE_SIZE; + private static final String CACHE_SIZE_PROP = + "org.apache.el.BeanELResolver.CACHE_SIZE"; + + static { + if (System.getSecurityManager() == null) { + CACHE_SIZE = Integer.parseInt( + System.getProperty(CACHE_SIZE_PROP, "1000")); + } else { + CACHE_SIZE = AccessController.doPrivileged( + new PrivilegedAction<Integer>() { + public Integer run() { + return Integer.valueOf( + System.getProperty(CACHE_SIZE_PROP, "1000")); + } + }).intValue(); + } + } + private final boolean readOnly; - private final ConcurrentCache<String, BeanProperties> cache = new ConcurrentCache<String, BeanProperties>( - 1000); + private final ConcurrentCache<String, BeanProperties> cache = + new ConcurrentCache<String, BeanProperties>(CACHE_SIZE); public BeanELResolver() { this.readOnly = false; @@ -324,7 +345,9 @@ public V get(K key) { V value = this.eden.get(key); if (value == null) { - value = this.longterm.get(key); + synchronized (longterm) { + value = this.longterm.get(key); + } if (value != null) { this.eden.put(key, value); } @@ -334,11 +357,12 @@ public void put(K key, V value) { if (this.eden.size() >= this.size) { - this.longterm.putAll(this.eden); + synchronized (longterm) { + this.longterm.putAll(this.eden); + } this.eden.clear(); } this.eden.put(key, value); } - } } Modified: branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/catalina/connector/Request.java =================================================================== --- branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/catalina/connector/Request.java 2011-07-05 17:08:41 UTC (rev 1769) +++ branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/catalina/connector/Request.java 2011-07-05 17:12:56 UTC (rev 1770) @@ -1369,6 +1369,9 @@ return; } + if (context == null) + return; + // Notify interested application event listeners Object listeners[] = context.getApplicationEventListeners(); if ((listeners == null) || (listeners.length == 0)) @@ -1439,6 +1442,9 @@ coyoteRequest.setAttribute(name, value); } + if (context == null) + return; + // Notify interested application event listeners Object listeners[] = context.getApplicationEventListeners(); if ((listeners == null) || (listeners.length == 0)) Modified: branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/el/lang/ExpressionBuilder.java =================================================================== --- branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/el/lang/ExpressionBuilder.java 2011-07-05 17:08:41 UTC (rev 1769) +++ branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/el/lang/ExpressionBuilder.java 2011-07-05 17:12:56 UTC (rev 1770) @@ -50,7 +50,7 @@ */ public final class ExpressionBuilder implements NodeVisitor { - private static final ConcurrentCache cache = new ConcurrentCache(5000); + private static final ConcurrentCache cache = new ConcurrentCache(10000); private FunctionMapper fnMapper; Modified: branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/el/util/ConcurrentCache.java =================================================================== --- branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/el/util/ConcurrentCache.java 2011-07-05 17:08:41 UTC (rev 1769) +++ branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/java/org/apache/el/util/ConcurrentCache.java 2011-07-05 17:12:56 UTC (rev 1770) @@ -1,3 +1,19 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ package org.apache.el.util; import java.util.Map; @@ -6,34 +22,38 @@ public final class ConcurrentCache<K,V> { - private final int size; - - private final Map<K,V> eden; - - private final Map<K,V> longterm; - - public ConcurrentCache(int size) { - this.size = size; - this.eden = new ConcurrentHashMap<K,V>(size); - this.longterm = new WeakHashMap<K,V>(size); - } - - public V get(K k) { - V v = this.eden.get(k); - if (v == null) { - v = this.longterm.get(k); - if (v != null) { - this.eden.put(k, v); - } - } - return v; - } - - public void put(K k, V v) { - if (this.eden.size() >= size) { - this.longterm.putAll(this.eden); - this.eden.clear(); - } - this.eden.put(k, v); - } + private final int size; + + private final Map<K,V> eden; + + private final Map<K,V> longterm; + + public ConcurrentCache(int size) { + this.size = size; + this.eden = new ConcurrentHashMap<K,V>(size); + this.longterm = new WeakHashMap<K,V>(size); + } + + public V get(K k) { + V v = this.eden.get(k); + if (v == null) { + synchronized (longterm) { + v = this.longterm.get(k); + } + if (v != null) { + this.eden.put(k, v); + } + } + return v; + } + + public void put(K k, V v) { + if (this.eden.size() >= size) { + synchronized (longterm) { + this.longterm.putAll(this.eden); + } + this.eden.clear(); + } + this.eden.put(k, v); + } }

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1769 - branches.

by jbossweb-commits＠lists.jboss.org

Author: bmaxwell Date: 2011-07-05 13:08:41 -0400 (Tue, 05 Jul 2011) New Revision: 1769 Added: branches/JBOSSWEB_2_1_10_GA_JBPAPP-6778/ Log: [JBPAPP-6778] create one off patch branch

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1768 - trunk/webapps/docs.

by jbossweb-commits＠lists.jboss.org

Author: jfrederic.clere(a)jboss.com Date: 2011-07-05 10:54:38 -0400 (Tue, 05 Jul 2011) New Revision: 1768 Modified: trunk/webapps/docs/sysprops.xml Log: Remove link. Modified: trunk/webapps/docs/sysprops.xml =================================================================== --- trunk/webapps/docs/sysprops.xml 2011-07-05 14:50:31 UTC (rev 1767) +++ trunk/webapps/docs/sysprops.xml 2011-07-05 14:54:38 UTC (rev 1768) @@ -59,8 +59,8 @@ <properties> <property name="jvmRoute"> - Provides a default value for the <code>jvmRoute</code> attribute of the - <a href="engine.html">Engine</a> element. It does not override the automaticaly + Provides a default value for the <code>jvmRoute</code> attribute. + It does not override the automaticaly generated value used when using ha read with using configuration like <code>standalone-ha.xml</code> It supports <code>:reload</code>. </property>

12 years, 10 months

1
0
0 / 0

JBossWeb SVN: r1767 - trunk/webapps/docs.

by jbossweb-commits＠lists.jboss.org

Author: jfrederic.clere(a)jboss.com Date: 2011-07-05 10:50:31 -0400 (Tue, 05 Jul 2011) New Revision: 1767 Modified: trunk/webapps/docs/sysprops.xml Log: Arrange it and remove the properties we don't support. Modified: trunk/webapps/docs/sysprops.xml =================================================================== --- trunk/webapps/docs/sysprops.xml 2011-07-05 09:26:09 UTC (rev 1766) +++ trunk/webapps/docs/sysprops.xml 2011-07-05 14:50:31 UTC (rev 1767) @@ -30,67 +30,65 @@ <section name="Introduction"> The follow sections list the system properties that may be set to modify - the default Tomcat behaviour. + the default JBossWeb behaviour. + The <code>system-properties</code>can be set in the AS7 configuration (you need to + restart it to get them applied to the web sub system, for example: +<source> +standalone@localhost:9999 /] ./system-property=org.apache.catalina.JSESSIONID:add(value="MYID") +{"outcome" => "success"} +standalone@localhost:9999 /] :shutdown +Communication error: Channel closed +Closed connection to localhost:9999 +</source> + then restart it for some properties a reload command is enough: +<source> +[standalone@localhost:9999 /] :reload +{ + "outcome" => "success", + "response-headers" => { + "operation-requires-reload" => true, + "process-state" => "reload-required" + } +} +</source> + </section> <section name="Servlet container and connectors"> <properties> - <property name="catalina.useNaming"> - If this is <code>false</code> it will override the - <code>useNaming</code> attribute for all <a href="context.html"> - Context</a> elements. - </property> - <property name="jvmRoute"> Provides a default value for the <code>jvmRoute</code> attribute of the - <a href="engine.html">Engine</a> element. It does not override the a value - configured on the <a href="engine.html">Engine</a> element. + <a href="engine.html">Engine</a> element. It does not override the automaticaly + generated value used when using ha read with using configuration like <code>standalone-ha.xml</code> + It supports <code>:reload</code>. </property> - <property - name="org.apache.catalina.loader. WebappClassLoader.ENABLE_CLEAR_REFERENCES"> - If <code>true</code>, Tomcat attempts to null out any static or final - fields from loaded classes when a web application is stopped as a work - around for apparent garbage collection bugs and application coding errors. - - There have been some issues reported with log4j when this option is - <code>true</code>. - Applications without memory leaks using recent JVMs should operate - correctly with this option set to <code>false</code>. - If not specified, the default value of <code>true</code> will be used. - - </property> - - <property name="catalina.config"> - The URL for the catalina.properties configuration file. - </property> - - <property name="org.apache.tomcat.tomcat.util.buf.StringCache.byte.enabled"> + <property name="org.apache.tomcat.util.buf.StringCache.byte.enabled"> If <code>true</code>, the String cache is enabled for <code>ByteChunk</code>. If not specified, the default value of <code>false</code> will be used. </property> - <property name="org.apache.tomcat.tomcat.util.buf.StringCache.char.enabled"> + <property name="org.apache.tomcat.util.buf.StringCache.char.enabled"> If <code>true</code>, the String cache is enabled for <code>CharChunk</code>. If not specified, the default value of <code>false</code> will be used. </property> - <property name="org.apache.tomcat.tomcat.util.buf.StringCache.trainThreshold"> + <property name="org.apache.tomcat.util.buf.StringCache.trainThreshold"> The number of times <code>toString()</code> must be called before the cache is activated. If not specified, the default value of <code>20000</code> will be used. </property> - <property name="org.apache.tomcat.tomcat.util.buf.StringCache.cacheSize"> + <property name="org.apache.tomcat.util.buf.StringCache.cacheSize"> The size of the String cache. If not specified, the default value of <code>200</code> will be used. </property> - <property name="org.apache.tomcat.tomcat.util.buf.StringCache.maxStringSize"> + <property name="org.apache.tomcat.util.buf.StringCache.maxStringSize"> The maximum length of String that will be cached. If not specified, the default value of <code>128</code> will be used. </property> @@ -112,7 +110,7 @@ </property> <property - name="org.apache.coyote. USE_CUSTOM_STATUS_MSG_IN_HEADER"> + name="org.apache.coyote.Constants.USE_CUSTOM_STATUS_MSG_IN_HEADER"> If this is <code>true</code> custom HTTP status messages will be used within HTTP headers. Users must ensure that any such message is ISO-8859-1 encoded, particularly if user provided input is included in @@ -120,12 +118,6 @@ the default value of <code>false</code> will be used. </property> - <property name="org.apache.tomcat.util. http.ServerCookie.VERSION_SWITCH"> - If using cookie values which have to be quoted to be valid and v0 cookies, - this will cause an automatic switch to v1 cookies. If not - specified, the default value of <code>true</code> will be used. - </property> - </properties> </section> @@ -148,63 +140,61 @@ <section name="JSP"> <properties> - <property name="org.apache.jasper.compiler. Generator.VAR_EXPRESSIONFACTORY"> + <property name="org.apache.jasper.compiler.Generator.VAR_EXPRESSIONFACTORY"> The name of the variable to use for the expression language expression factory. If not specified, the default value of <code>_el_expressionfactory</code> will be used. </property> - <property name="org.apache.jasper.compiler. Generator.VAR_INSTANCEMANAGER"> + <property name="org.apache.jasper.compiler.Generator.VAR_INSTANCEMANAGER"> The name of the variable to use for the instance manager factory. If not specified, the default value of <code>_jsp_instancemanager</code> will be used. </property> - <property name="org.apache.jasper.compiler. Parser.STRICT_QUOTE_ESCAPING"> + <property name="org.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING"> If <code>false</code> the requirements for escpaing quotes in JSP attributes will be relaxed so that a missing required quote will not cause an error. If not specified, the specification compliant default of <code>true</code> will be used. </property> - - <property name="org.apache.jasper.runtime. JspFactoryImpl.USE_POOL"> + <property name="org.apache.jasper.runtime.JspFactoryImpl.USE_POOL"> If <code>true</code>, a ThreadLocal <code>PageContext</code> pool will be used. If not specified, the default value of <code>true</code> will be used. </property> - <property name="org.apache.jasper.runtime. JspFactoryImpl.POOL_SIZE"> + <property name="org.apache.jasper.runtime.JspFactoryImpl.POOL_SIZE"> The size of the ThreadLocal <code>PageContext</code>. If not specified, the default value of <code>8</code> will be used. </property> - <property name="org.apache.jasper.Constants. JSP_SERVLET_BASE"> + <property name="org.apache.jasper.Constants.JSP_SERVLET_BASE"> The base class of the Servlets generated from the JSPs. If not specified, the default value of <code>org.apache.jasper.runtime.HttpJspBase</code> will be used. </property> - <property name="org.apache.jasper.Constants. SERVICE_METHOD_NAME"> + <property name="org.apache.jasper.Constants.SERVICE_METHOD_NAME"> The name of the service method called by the base class. If not specified, the default value of <code>_jspService</code> will be used. </property> - <property name="org.apache.jasper.Constants. SERVLET_CLASSPATH"> + <property name="org.apache.jasper.Constants.SERVLET_CLASSPATH"> The name of the ServletContext attribute that provides the classpath for the JSP. If not specified, the default value of <code>org.apache.catalina.jsp_classpath</code> will be used. </property> - <property name="org.apache.jasper.Constants. JSP_FILE"> + <property name="org.apache.jasper.Constants.JSP_FILE"> The name of the request attribute for <code><jsp-file></code> element of a servlet definition. If present on a request, this overrides the value returned by <code>request.getServletPath()</code> to select the @@ -212,41 +202,34 @@ <code>org.apache.catalina.jsp_file</code> will be used. </property> - <property name="org.apache.jasper.Constants. PRECOMPILE"> + <property name="org.apache.jasper.Constants.PRECOMPILE"> The name of the query parameter that causes the JSP engine to just pregenerate the servlet but not invoke it. If not specified, the default value of <code>org.apache.catalina.jsp_precompile</code> will be used. </property> - <property name="org.apache.jasper.Constants. JSP_PACKAGE_NAME"> + <property name="org.apache.jasper.Constants.JSP_PACKAGE_NAME"> The default package name for compiled jsp pages. If not specified, the default value of <code>org.apache.jsp</code> will be used. </property> - <property name="org.apache.jasper.Constants. TAG_FILE_PACKAGE_NAME"> + <property name="org.apache.jasper.Constants.TAG_FILE_PACKAGE_NAME"> The default package name for tag handlers generated from tag files. If not specified, the default value of <code>org.apache.jsp.tag</code> will be used. </property> - <property name="org.apache.jasper.Constants. ALT_DD_ATTR"> - The servlet context attribute under which the alternate deployment - descriptor for this web application is stored. If not specified, the - default value of <code>org.apache.catalina.deploy.alt_dd</code> will - be used. - </property> - - <property name="org.apache.jasper.Constants. TEMP_VARIABLE_NAME_PREFIX"> + <property name="org.apache.jasper.Constants.TEMP_VARIABLE_NAME_PREFIX"> Prefix to use for generated temporary variable names. If not specified, the default value of <code>_jspx_temp</code> will be used. </property> - <property name="org.apache.jasper.Constants. USE_INSTANCE_MANAGER_FOR_TAGS"> + <property name="org.apache.jasper.Constants.USE_INSTANCE_MANAGER_FOR_TAGS"> If <code>true</code>, the instance manager is used to obtain tag handler instances. If not specified, <code>false</code> will be used. </property> - <property name="org.apache.jasper.Constants. USE_INSTANCE_MANAGER_FOR_TAGS"> + <property name="org.apache.jasper.Constants.INJECT_TAGS"> If <code>true</code>, annotations specified in tags will be processed and injected. This can have a performance impact when using simple tags, or if tag pooling is disabled. If not specified, <code>true</code> will be used. @@ -261,21 +244,21 @@ <properties> - <property name="org.apache.catalina.connector. RECYCLE_FACADES"> + <property name="org.apache.catalina.connector.RECYCLE_FACADES"> If this is <code>true</code> or if a security manager is in use a new facade object will be created for each request. If not specified, the default value of <code>false</code> will be used. </property> <property - name="org.apache.catalina.connector. CoyoteAdapter.ALLOW_BACKSLASH"> + name="org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH"> If this is <code>true</code> the '\' character will be permitted as a path delimiter. If not specified, the default value of <code>false</code> will be used. </property> <property - name="org.apache.tomcat.util.buf. UDecoder.ALLOW_ENCODED_SLASH"> + name="org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH"> If this is <code>true</code> '%2F' and '%5C' will be permitted as path delimiters. If not specified, the default value of <code>false</code> will be used. @@ -290,7 +273,7 @@ <properties> - <property name="org.apache.catalina. STRICT_SERVLET_COMPLIANCE"> + <property name="org.apache.catalina.STRICT_SERVLET_COMPLIANCE"> If this is <code>true</code> the following actions will occur: <ul> <li>any wrapped request or response object passed to an application @@ -311,7 +294,7 @@ </property> - <property name="org.apache.catalina.core. StandardWrapperValve.SERVLET_STATS"> + <property name="org.apache.catalina.core.StandardWrapperValve.SERVLET_STATS"> If <code>true</code> or if <code>org.apache.catalina.STRICT_SERVLET_COMPLIANCE</code> is <code>true</code>, the wrapper will collect the JSR-77 statistics for @@ -320,7 +303,7 @@ </property> <property - name="org.apache.catalina.session. StandardSession.ACTIVITY_CHECK"> + name="org.apache.catalina.session.StandardSession.ACTIVITY_CHECK"> If this is <code>true</code> or if <code>org.apache.catalina.STRICT_SERVLET_COMPLIANCE</code> is <code>true</code> Tomcat will track the number of active requests for each @@ -335,4 +318,4 @@ </body> -</document> \ No newline at end of file +</document>

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossweb-commits July 2011