INSTALL

changeset 254
55ca6cafc3dd
parent 221
33d7833ca54c
child 262
c357c4e69b9e
--- a/INSTALL	Tue Nov 01 21:31:15 2022 +0100
+++ b/INSTALL	Wed Dec 28 13:21:30 2022 +0100
@@ -19,29 +19,19 @@
 3. Configure a data source in your application servlet or servlet container
 
 You may use absolutely anything: Tomcat, TomEE, Glassfish, Payara, you name it.
+If it supports Servlet 6.0, JSP 3.1, and EL 5.0, you are good to go.
 Just make sure to configure a data source with the name jdbc/lightpit/app.
 If you want another name, you can configure the JNDI resource in the
 WEB-INF/web.xml and META-INF/context.xml files. It is highly recommended to use
 the lightpit_app user which has less privileges to create the data source and
 leave the lightpit_dbo user for the database operator.
 
-4. Make sure JDBC driver and JSTL libraries are available
-
-This step may be optional depending on the container you are using. Most
-application servers already have JSTL libraries installed. More basic servlet
-containers like Tomcat don't. In that case you have to put the libraries of the
-javax.servlet:jstl:1.2 artifact manually into the library dir of your servlet
-container (jstl-1.2.jar and jstl-impl-1.2.jar).
-
-In most cases you also have to put the postgresql JDBC driver into the library
-directory of your server (e.g. postgres-42.x.x.jar).
-
-5. Deploy the WAR file of lightpit
+4. Deploy the WAR file of lightpit
 
 This is the most straight forward step. Just deploy the WAR file as you usually
 do in your application server.
 
-6. Configuring a web server and authentication
+5. Configuring a web server and authentication
 
 LightPIT can optionally detect the authenticated user. You may freely decide
 whether to enable authentication in your application server or put a web server

mercurial