Bruge en JNDI DataSource og konfigurere Tomcat

Der er inkonsistens.

Så vidt jeg kan se har du både HSQL og MySQL drivere defineret.

<parameter><name>driverClassName</name>
              <value>org.hsql.jdbcDriver</value></parameter>


og

<parameter>
    <name>driverClassName</name>
    <value>org.gjt.mm.mysql.Driver</value>
    </parameter>

Inkluderer "alle jar filer" den med HSQL JDBC driveren ?

Jeg kunne ikke finde HSQL JDBC driveren, eller en jar fil med noget af den tekst i.
Så jeg har fjernet inkonsistensen fra min servlet.xml, men det virker stadig ikke.
Hvad mere kan jeg gøre?

Jar filen hedder hsqldb.jar

Og hvis slet ikke du kan finde den, så kan du da downloade den:
  http://sourceforge.net/project/showfiles.php?group_id=23316&release_id=117043

Aha! Jeg fandt denne jar fil et obskurt sted, derefter puttede jeg den i common/lib og tilføjede den til pathen ... den siger stadig at den ikke kan finde filen. Hvad skal jeg nu gøre?

PS: Hvorfor vil du bruge HSQL fremfor MySQL.

Har du genstartet Tomcat efter at have kopieret den jar fil ?

Jeg har med sikkerhed nu sikret mig at Tomcat er blevet genstartet, efter jeg placerede den nye jar fil i common/lib og tilføjede den til path ... stadig flg fejl: TyrexDataSourceFactory:  Cannot create DataSource, Exception
java.lang.ClassNotFoundException: org.hsql.jdbcDriver

Jeg er tom for ideer.

Ah .. der er ikke nogen grund til at jeg vil bruge HSQL frem for MySQL, jeg vil gerne bruge MySQL - det er faktisk en MySQL database jeg forsøger at få adgang til gennem JNDI DataSource

Så er det:

    <name>driverClassName</name>
    <value>org.gjt.mm.mysql.Driver</value>
    </parameter>
    <parameter>
    <name>url</name>
    <value>jdbc:mysql://localhost:3306/binh</value>
    </parameter>           

du skal have fundet frem igen.

Og mysql-connector-java-x.x.x-bin.jar du skal have i common lib

mysql-connector-java-3.0.11-stable-bin.jar
ligger i common/lib og jeg har fundet den der frem igen.

Stadig denne fejl
TyrexDataSourceFactory:  Cannot create DataSource, Exception
java.lang.ClassNotFoundException: org.hsql.jdbcDriver

selvom der ikke står noget med hsql nogle steder, hverken i web.xml eller
i servlet.xml

Meget mytisk !

Bl.a. er Tyrex ikke engang default enablet i Tomcat.

her er hele min server.xml:

<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
    parent-child relationships with each other -->

<!-- A "Server" is a singleton element that represents the entire JVM,
    which may contain one or more "Service" instances.  The Server
    listens for a shutdown command on the indicated port.

    Note:  A "Server" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
-->

<Server port="8005" shutdown="SHUTDOWN" debug="0">


  <!-- A "Service" is a collection of one or more "Connectors" that share
      a single "Container" (and therefore the web applications visible
      within that Container).  Normally, that Container is an "Engine",
      but this is not required.

      Note:  A "Service" is not itself a "Container", so you may not
      define subcomponents such as "Valves" or "Loggers" at this level.
  -->

  <!-- Define the Tomcat Stand-Alone Service -->
  <Service name="Tomcat-Standalone">

    <!-- A "Connector" represents an endpoint by which requests are received
        and responses are returned.  Each Connector passes requests on to the
        associated "Container" (normally an Engine) for processing.

        By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
        You can also enable an SSL HTTP/1.1 Connector on port 8443 by
        following the instructions below and uncommenting the second Connector
        entry.  SSL support requires the following steps (see the SSL Config
        HOWTO in the Tomcat 4.0 documentation bundle for more detailed
        instructions):
        * Download and install JSSE 1.0.2 or later, and put the JAR files
          into "$JAVA_HOME/jre/lib/ext".
        * Execute:
            %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
            $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
          with a password value of "changeit" for both the certificate and
          the keystore itself.

        By default, DNS lookups are enabled when a web application calls
        request.getRemoteHost().  This can have an adverse impact on
        performance, so you can disable it by setting the
        "enableLookups" attribute to "false".  When DNS lookups are disabled,
        request.getRemoteHost() will return the String version of the
        IP address of the remote client.
    -->

    <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
              port="8080" minProcessors="5" maxProcessors="75"
              enableLookups="true" redirectPort="8443"
              acceptCount="10" debug="0" connectionTimeout="60000"/>
    <!-- Note : To disable connection timeouts, set connectionTimeout value
    to -1 -->

    <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8081 -->
    <!--
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
              port="8081" minProcessors="5" maxProcessors="75"
              enableLookups="true" redirectPort="8443"
              acceptCount="10" debug="0" connectionTimeout="20000"/>
    -->

    <!-- Define an SSL HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
              port="8443" minProcessors="5" maxProcessors="75"
              enableLookups="true"
          acceptCount="10" debug="0" scheme="https" secure="true">
      <Factory className="org.apache.catalina.net.SSLServerSocketFactory"
              clientAuth="false" protocol="TLS"/>
    </Connector>
    -->

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
              port="8009" minProcessors="5" maxProcessors="75"
              acceptCount="10" debug="0"/>

    <!-- Define a Proxied HTTP/1.1 Connector on port 8081 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
              port="8082" minProcessors="5" maxProcessors="75"
              enableLookups="true"
              acceptCount="10" debug="0" connectionTimeout="60000"
              proxyPort="80"/>
    -->

    <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8082 -->
    <!--
    <Connector className="org.apache.catalina.connector.http10.HttpConnector"
              port="8083" minProcessors="5" maxProcessors="75"
              enableLookups="true" redirectPort="8443"
              acceptCount="10" debug="0"/>
    -->

    <!-- An Engine represents the entry point (within Catalina) that processes
        every request.  The Engine implementation for Tomcat stand alone
        analyzes the HTTP headers included with the request, and passes them
        on to the appropriate Host (virtual host). -->

    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Standalone" defaultHost="localhost" debug="0">

      <!-- The request dumper valve dumps useful debugging information about
          the request headers and cookies that were received, and the response
          headers and cookies that were sent, for all requests received by
          this instance of Tomcat.  If you care only about requests to a
          particular virtual host, or a particular application, nest this
          element inside the corresponding <Host> or <Context> entry instead.

          For a similar mechanism that is portable to all Servlet 2.3
          containers, check out the "RequestDumperFilter" Filter in the
          example application (the source for this filter may be found in
          "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").

          Request dumping is disabled by default.  Uncomment the following
          element to enable it. -->
      <!--
      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
      -->

      <!-- Global logger unless overridden at lower levels -->
      <Logger className="org.apache.catalina.logger.FileLogger"
              prefix="catalina_log." suffix=".txt"
              timestamp="true"/>

      <!-- Because this Realm is here, an instance will be shared globally -->

      <Realm className="org.apache.catalina.realm.MemoryRealm" />

      <!-- Replace the above Realm with one of the following to get a Realm
          stored in a database and accessed via JDBC -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
            driverName="org.gjt.mm.mysql.Driver"
          connectionURL="jdbc:mysql://localhost/authority?user=test;password=test"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
            driverName="oracle.jdbc.driver.OracleDriver"
          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL?user=scott;password=tiger"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
            driverName="sun.jdbc.odbc.JdbcOdbcDriver"
          connectionURL="jdbc:odbc:CATALINA"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!-- Define the default virtual host -->
      <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true">

        <!-- Normally, users must authenticate themselves to each web app
            individually.  Uncomment the following entry if you would like
            a user to be authenticated the first time they encounter a
            resource protected by a security constraint, and then have that
            user identity maintained across *all* web applications contained
            in this virtual host. -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn"
                  debug="0"/>
        -->

        <!-- Access log processes all requests for this virtual host.  By
            default, log files are created in the "logs" directory relative to
            $CATALINA_HOME.  If you wish, you can specify a different
            directory with the "directory" attribute.  Specify either a relative
            (to $CATALINA_HOME) or absolute path to the desired directory.
        -->
        <Valve className="org.apache.catalina.valves.AccessLogValve"
                directory="logs"  prefix="localhost_access_log." suffix=".txt"
                pattern="common"/>

        <!-- Logger shared by all Contexts related to this virtual host.  By
            default (when using FileLogger), log files are created in the "logs"
            directory relative to $CATALINA_HOME.  If you wish, you can specify
            a different directory with the "directory" attribute.  Specify either a
            relative (to $CATALINA_HOME) or absolute path to the desired
            directory.-->
        <Logger className="org.apache.catalina.logger.FileLogger"
                directory="logs"  prefix="localhost_log." suffix=".txt"
            timestamp="true"/>

        <!-- Define properties for each web application.  This is only needed
            if you want to set non-default properties, or have web application
            document roots in places other than the virtual host's appBase
            directory.  -->

        <!-- Tomcat Root Context -->
        <!--
          <Context path="" docBase="ROOT" debug="0"/>
        -->
   
          <Context path="/Advanced" docBase="Advanced" debug="5" reloadable="true" crossContext="true">
    <Logger className="org.apache.catalina.logger.FileLogger" prefix="localhost_Advanced_log." suffix=".txt" timestamp="true" />
    <Resource name="jdbc/binh" auth="Container" type="javax.sql.DataSource"/>
           
        <!-- Tomcat Manager Context -->
        <!-- <Context path="/manager" docBase="manager"
        debug="0" privileged="true"/>

        <!-- Tomcat Examples Context -->
      <!--  <Context path="/examples" docBase="examples" debug="0"
                reloadable="true" crossContext="true">
          <Logger className="org.apache.catalina.logger.FileLogger"
                    prefix="localhost_examples_log." suffix=".txt"
              timestamp="true"/>
          <Ejb  name="ejb/EmplRecord" type="Entity"
                home="com.wombat.empl.EmployeeRecordHome"
              remote="com.wombat.empl.EmployeeRecord"/> -->
          <!-- PersistentManager: Uncomment the section below to test Persistent
              Sessions.
                       
              saveOnRestart: If true, all active sessions will be saved
                to the Store when Catalina is shutdown, regardless of
                other settings. All Sessions found in the Store will be
                loaded on startup. Sessions past their expiration are
                ignored in both cases.
              maxActiveSessions: If 0 or greater, having too many active
                sessions will result in some being swapped out. minIdleSwap
                limits this. -1 means unlimited sessions are allowed.
                0 means sessions will almost always be swapped out after
                use - this will be noticeably slow for your users.
              minIdleSwap: Sessions must be idle for at least this long
                (in seconds) before they will be swapped out due to
              maxActiveSessions. This avoids thrashing when the site is
                highly active. -1 or 0 means there is no minimum - sessions
                can be swapped out at any time.
              maxIdleSwap: Sessions will be swapped out if idle for this
                long (in seconds). If minIdleSwap is higher, then it will
                override this. This isn't exact: it is checked periodically.
                -1 means sessions won't be swapped out for this reason,
                although they may be swapped out for maxActiveSessions.
                If set to >= 0, guarantees that all sessions found in the
                Store will be loaded on startup.
              maxIdleBackup: Sessions will be backed up (saved to the Store,
                but left in active memory) if idle for this long (in seconds),
                and all sessions found in the Store will be loaded on startup.
                If set to -1 sessions will not be backed up, 0 means they
                should be backed up shortly after being used.

              To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
              and minIdleBackup all to -1, saveOnRestart to false, then restart
              Catalina.
          -->
          <!--
          <Manager className="org.apache.catalina.session.PersistentManager"
              debug="0"
              saveOnRestart="true"
              maxActiveSessions="-1"
              minIdleSwap="-1"
              maxIdleSwap="-1"
              maxIdleBackup="-1">
                <Store className="org.apache.catalina.session.FileStore"/>
          </Manager>
          -->
          <Environment name="maxExemptions" type="java.lang.Integer"
                      value="15"/>
          <Parameter name="context.param.name" value="context.param.value"
                    override="false"/>
          <Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
                    type="javax.sql.DataSource"/>
          <ResourceParams name="jdbc/EmployeeAppDb">
          <!-- <parameter><name>user</name><value>sa</value></parameter>
            <parameter><name>password</name><value></value></parameter>
            <parameter><name>driverClassName</name>
              <value>org.hsql.jdbcDriver</value></parameter>
            <parameter><name>driverName</name>
              <value>jdbc:HypersonicSQL:database</value></parameter>  -->
    <parameter>
    <name>factory</name>
    <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
    </parameter>
    <parameter>
    <name>maxActive</name>
    <value>100</value>
    </parameter>
    <parameter>
    <name>maxIdle</name>
    <value>30000</value>
    </parameter>
    <parameter>
    <name>maxWait</name>
    <value>100</value>
    </parameter>
    <parameter>
    <name>username</name>
    <value>scott</value>
    </parameter>
    <parameter>
    <name>password</name>
    <value>tiger</value>
    </parameter>
    <parameter>
    <name>driverClassName</name>
    <value>org.gjt.mm.mysql.Driver</value>
    </parameter>
    <parameter>
    <name>url</name>
    <value>jdbc:mysql://localhost:3306/binh</value>
    </parameter>             
         
          </ResourceParams>
          <Resource name="mail/Session" auth="Container"
                    type="javax.mail.Session"/>
          <ResourceParams name="mail/Session">
            <parameter>
              <name>mail.smtp.host</name>
              <value>localhost</value>
            </parameter>
          </ResourceParams>
       
 
      </Context>
   
   
   
      </Host>

    </Engine>

  </Service>

  <!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
      as its servlet container. Please read the README.txt file coming with
      the WebApp Module distribution on how to build it.
      (Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)

      To configure the Apache side, you must ensure that you have the
      "ServerName" and "Port" directives defined in "httpd.conf".  Then,
      lines like these to the bottom of your "httpd.conf" file:

        LoadModule webapp_module libexec/mod_webapp.so
        WebAppConnection warpConnection warp localhost:8008
        WebAppDeploy examples warpConnection /examples/

      The next time you restart Apache (after restarting Tomcat, if needed)
      the connection will be established, and all applications you make
      visible via "WebAppDeploy" directives can be accessed through Apache.
  -->

  <!-- Define an Apache-Connector Service -->
  <Service name="Tomcat-Apache">

    <Connector className="org.apache.catalina.connector.warp.WarpConnector"
    port="8008" minProcessors="5" maxProcessors="75"
    enableLookups="true" appBase="webapps"
    acceptCount="10" debug="0"/>

    <!-- Replace "localhost" with what your Apache "ServerName" is set to -->
    <Engine className="org.apache.catalina.connector.warp.WarpEngine"
    name="Apache" debug="0">

      <!-- Global logger unless overridden at lower levels -->
      <Logger className="org.apache.catalina.logger.FileLogger"
              prefix="apache_log." suffix=".txt"
              timestamp="true"/>

      <!-- Because this Realm is here, an instance will be shared globally -->
      <Realm className="org.apache.catalina.realm.MemoryRealm" />

    </Engine>

  </Service>

</Server>

Jeg bruger Netbeans med intern Tomcat version 4.0.6 og jeg har læst i min jsp bog at versioner af Tomcat, der kommer før version 4.1 bruger en Tyrex EnabledDataSource som default. Med en opdatering af Tomcat versionen til en 4.1 eller nyere vil måske løse problemet (?), så det vil jeg forsøge at gøre.

Der er ikke noget i den server.xml som springer i øjnene på mig.

Jeg synes absolut at du skulle installere en standalone Tomcat, fordi:
  - 4.0.6 er meget gammel og en opdatering både kan indeholde fejlrettelser
    og gøre nyere dokumentation mere brugbar
  - principielt foretrækker jeg at holde IDE og server skarpt adskilt

Har installeret en Tomcat 5 nu og forsøger at implementere den i Netbeans (så¨den bruger den eksterne Netbeans), men jeg får en NullPointerException når jeg forsøger at starte serveren fra IDE'et. Ved du tilfældigvis hvordan man får en ekstern server op at køre i Netbeans?

jeg mener så den bruger den eksterne Tomcat

Nej.

Jeg kører altid IDE og server adskilt.

Jeg bygger en war fil i IDE'en og den deployer jeg så til serveren,
som jeg starter og stopper udenfor IDE'en.

Jeg skal lige have en ekstern Tomcat konfiguration op at køre, så vender jeg
tilbage!

OK! har fået styr på min eksterne Tomcat, men den kan stadig ikke integreres i min IDE, men det er nu ligemeget, bare den kan køre eksternt. I min WEB-INF/classes har jeg en pakke med en bean nede i, der bare har en metode, der returnerer en default værdi (en streng), måden jeg kunne bruge min bean på, var at sætte nogle tags i min web.xml-fil .. så kunne den se min klasse. De tags hedder eksempelvis:
<servlet>
        <servlet-name>myBean</servlet-name>
        <servlet-class>myBean</servlet-class>
    </servlet>

Jeg har et tvivlsspørgmål:
mapper man en bean som en servlet?

Nej

Dem bruger man normalt fra servlet eller JSP side

Men det er ikke forkert at mappe en klasse således?

Det er ihvertfald ikke som det er tiltænkt.

Put din bean ned i en pakke og kald den fra en servlet.

Eller bedre fra en JSP side.

Foretrækker du at bruge <jsp:useBean .... eller at kalde klassen ved at lave en instans af den?

altså jeg mener ved selv at lave en instans af den

<jsp:useBean id="mb" class="MyBean" scope="request"/>

er en pæn måde at gøre det på, men hvis du foretrækker:

<%
MyBean mb = new MyBean();
%>

så gør det det samme.

OK har nu genskrevet det man skal skrive i server.xml og web.xml. Har lavet klassen der kører lookup på Context ... forsøger at bruge klassen, men får flg fejl:
"Name jdbc is not bound in this Context" (fra Tomcat output vinduet).
Jeg har disse jar filer i min Common/lib:
commons-collections.jar
commons-dbcp-1.1.jar
commons-pool-1.1.jar
Jeg har ikke lagt dem der, de lå der i forvejen og jeg mener det er de jar's den benytter i hele dette JNDI puslespil? Mangler jeg nogle flere jar filer?

Har lige forsøget at lægge jdbc driveren ned i Common/lib også, stadig samme fejl, jeg troede det var den den ville have, men nej

Fejlen betyder at JNDI træet ikke indeholder "jdbc" så det er
konfigurationen af den JNDI source du skal kigge på - ikke jar filer

Got connection org.apache.commons.dbcp.PoolableConnection@16089a5

:) :) :) :)

Betyder det at det virker nu ?

Ja! Som tak for din tålmodighed burde du have nogle point

Så ligger jeg et svar