Как я могу заставить Tomcat предварительно скомпилировать JSPs на запуске?
СУХОЙ (не повторяйся)
Я не на 100% уверен, что правильно выполнил комбо, но я бы использовал этот метод
Не нужно устанавливать отключенное, Я просто запускаю изменение нагрузки
$('#ordersdetailID_portion').on('change', function() {
var pl1 = +this.value, // partyloafportionID
$weight = $('#ordersdetailpartyloafweightID');
$('option[value="1"]',$weight).prop('disabled', pl1 != 1);
$('option[value="2"]',$weight).prop('disabled', pl1 != 2);
$('option[value="3"]',$weight).prop('disabled', pl1 != 3);
$('option[value="4"]',$weight).prop('disabled', pl1 != 4 && pl1 != 5);
$('option[value="5"]',$weight).prop('disabled', pl1 != 4 && pl1 != 5);
}).change();<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
<select id="ordersdetailID_portion" name="child-ID_portion" class="form-control select2 select2-hidden-accessible" tabindex="-1" aria-hidden="true" required="">
<option value="">** Veuillez saisir une option Nombre de sandwiches</option>
<option value="4">100</option>
<option value="1">30</option>
<option value="2">60</option>
<option value="3">80</option>
</select>
<select id="ordersdetailpartyloafweightID" name="child-partyloafweightID" class="form-control select2 select2-hidden-accessible" tabindex="-1" aria-hidden="true" required="">
<option value="">** Please choose the appropriate weight</option>
<option value="2">1 Kg</option>
<option value="3">1.5 Kg</option>
<option value="4">2 Kg</option>
<option value="5">2.5 Kg</option>
<option value="1">600 g</option>
</select>2 ответа
http://www.devshed.com/c/a/BrainDump/Tomcat-Capacity-Planning/
project name="pre-compile-jsps" default="compile-jsp-servlets">
<!-- Private properties. -- >
<property name="webapp.dir" value="${basedir}/webapp-dir"/>
<property name="tomcat.home" value="/opt/tomcat"/>
<property name="jspc.pkg.prefix" value="com.mycompany"/>
<property name="jspc.dir.prefix" value="com/mycompany"/>
<!-- Compilation properties. -->
<property name="debug" value="on"/>
<property name="debuglevel" value="lines,vars,source"/>
<property name="deprecation" value="on"/>
<property name="encoding" value="ISO-8859-1"/>
<property name="optimize" value="off"/>
<property name="build.compiler" value="modern"/>
<property name="source.version" value="1.5"/>
<!-- Initialize Paths. -->
<path id="jspc.classpath">
<fileset dir="${tomcat.home}/bin">
<include name="*.jar"/>
</fileset>
<fileset dir="${tomcat.home}/server/lib">
<include name="*.jar"/>
</fileset>
<fileset dir="${tomcat.home}/common/i18n">
<include name="*.jar"/>
</fileset>
<fileset dir="${tomcat.home}/common/lib">
<include name="*.jar"/>
</fileset>
<fileset dir="${webapp.dir}/WEB-INF">
<include name="lib/*.jar"/>
</fileset>
<pathelement location="${webapp.dir}/WEB-INF/classes"/>
<pathelement location="${ant.home}/lib/ant.jar"/>
<pathelement location="${java.home}/../lib/tools.jar"/>
</path>
<property name="jspc.classpath" refid="jspc.classpath"/>
<!--========================================================== -->
<!-- Generates Java source and a web.xml file from JSP files. -->
<!-- ==========================================================
-->
<target name="generate-jsp-java-src">
<mkdir dir="${webapp.dir}/WEB-INF/jspc-src/${jspc.dir.prefix}"/>
<taskdef classname="org.apache.jasper.JspC" name="jasper2">
<classpath>
<path refid="jspc.classpath"/>
</classpath>
</taskdef>
<touch file="${webapp.dir}/WEB-INF/jspc-web.xml"/>
<jasper2 uriroot="${webapp.dir}"
package="${jspc.pkg.prefix}"
webXmlFragment="${webapp.dir}/WEB-INF/jspc-web.xml"
outputDir="${webapp.dir}/WEB-INF/jspc-src/${jspc.dir.prefix}"
verbose="1"/>
</target>
<!-- ========================================================== -->
<!-- Compiles (generates Java class files from) the JSP servlet -->
<!-- source code that was generated by the JspC task. -->
<!-- ========================================================== -->
<target name="compile-jsp-servlets" depends="generate-jsp-java-src">
<mkdir dir="${webapp.dir}/WEB-INF/classes"/>
<javac srcdir="${webapp.dir}/WEB-INF/jspc-src"
destdir="${webapp.dir}/WEB-INF/classes"
includes="**/*.java"
debug="${debug}"
debuglevel="${debuglevel}"
deprecation="${deprecation}"
encoding="${encoding}"
optimize="${optimize}"
source="${source.version}">
<classpath>
<path refid="jspc.classpath"/>
</classpath>
</javac>
</target>
<!-- ========================================================= -->
<!-- Cleans any pre-compiled JSP source, classes, jspc-web.xml -->
<!-- ========================================================= -->
<target name="clean">
<delete dir="${webapp.dir}/WEB-INF/jspc-src"/>
<delete dir="${webapp.dir}/WEB-INF/classes/${jspc.dir.prefix}"/>
<delete file="${webapp.dir}/WEB-INF/jspc-web.xml"/>
</target>
</project
This build file will find all of your webapp’s JSP files, compile them into servlet classes, and generate servlet mappings for those JSP servlet classes. The servlet map pings it generates must go into your webapp’s WEB-INF/web.xml file, but it would be difficult to write an Ant build file that knows how to insert the servlet mappings into your web.xml file in a repeatable way every time the build file runs. Instead, we used an XML entity include so that the generated servlet mappings go into a new file every time the build file runs and that servlet mappings file can be inserted into your web.xml file via the XML entity include mechanism. To use it, your webapp’s WEB- INF/web.xml must have a special entity declaration at the top of the file, plus a reference to the entity in the content of the web.xml file where you want the servlet mappings file to be included. Here is how an empty servlet 2.5 webapp’s web.xml file looks with these modifications:
<!DOCTYPE jspc-webxml [
<!ENTITY jspc-webxml SYSTEM "jspc-web.xml">
]>
<web-app xmlns=http://java.sun.com/xml/ns/javaee
xmlns:xsi=http://www.w3.org/2001/ XMLSchema-instance
xsi:schemaLocation="http:// java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/
javaee/web-app_2_5.xsd"
version="2.5">
<!-- We include the JspC-generated mappings here. -->
&jspc-webxml;
<!-- Non-generated web.xml content goes here. -->
</web-app>
Make sure your webapp’s web.xml file has the inline DTD (the DOCTYPE tag) all the way at the top of the file and the servlet 2.5 web-app schema declaration below that. Then, wherever you want to insert the generated servlet mappings in your web.xml file, put the entity reference &jspc-webxml; . Remember, the entity reference begins with an ampersand ( & ), then has the name of the entity, and ends with a semicolon ( ; ).
To use the build file, just edit it and set all of the properties at the top to values that match your setup, and then run it like this:
$ ant -f pre-compile-jsps.xml
Если вы воспользуетесь решением, о котором упомянул duffymo, указав на блог Винни Карпентера, у меня есть совет. Там была одна область, из-за которой мой контейнер зависал на неопределенное время при обращении к localhost (в частности, в частном методе connect()). В качестве обходного пути я использовал следующий хак:
private void connect(final String urlString) {
HttpURLConnection conn;
try {
final URL url = new URL(urlString);
conn = (HttpURLConnection)url.openConnection();
conn.setConnectTimeout(5000);
//time it out quickly - otherwise hangs forever
//seems to be an issue hitting localhost
//will still precompile the page
conn.setReadTimeout(100);
conn.setAllowUserInteraction(true);
conn.getInputStream();
conn.disconnect();
}
catch (SocketTimeoutException e) {
log.debug(e);
}
catch (IOException ioe) {
log.error(ioe);
}
}
Установка таймаута и игнорирование SocketTimeoutException сработали (хотя, конечно, это не лучшее решение). Кроме того, использование этой процедуры означает, что вам нужно будет указать JSP в web.xml. Для моих нужд этого было достаточно.