• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 400
  • Last Modified:

connecting to database using config.properties

Hi, I am fairly new to java. I want to put all the connection information like username, password, database name in config.properties and then make the java code use these values to connect to database. How do I do this.

Thanks in advance
0
muthiahmerchant
Asked:
muthiahmerchant
  • 10
  • 9
  • 8
  • +1
2 Solutions
 
CEHJCommented:
Use this approach

http://javaalmanac.com/egs/java.sql/ConnectSqlServer.html

, ignoring everything apart from the url.

Properties conProps = new Properties();
conProps.load(getClass().getResourceAsStream("db.properties"));

Then

connection = DriverManager.getConnection(url, conProps);
0
 
objectsCommented:
Best solution would be to use a data source, and define the details in the data source configuration.
0
 
objectsCommented:
following shows you to how to do it for tomcat

http://tomcat.apache.org/tomcat-5.0-doc/printer/jndi-datasource-examples-howto.html

for a standalone application the setup is similiar
Let me know your details and I'll walk u thru whats needed.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
objectsCommented:
Also allows you to add things like connection pooling w/out changing your code
0
 
CEHJCommented:
Is this in the context of a web server muthiahmerchant?
0
 
objectsCommented:
> Is this in the context of a web server muthiahmerchant?

irrelevant, you could (and probably should) always use a DataSource as it moves database dependant details out of your code and into config files.
0
 
CEHJCommented:
And how do you do that without JNDI?
0
 
muthiahmerchantAuthor Commented:
Sorry to get back so late, I don't have internet connection at home, So have to check in the office.

This is relevant to web server.

I will try both solutions and get back to you, hopefully by end of today

Thanks a lot guys
You folks are really really helping and thanks for that
0
 
Mayank SAssociate Director - Product EngineeringCommented:
>> This is relevant to web server.

Then you can use a data-source, that's the preferred approach.
0
 
muthiahmerchantAuthor Commented:
I am using tomcat and oracle 10g. Do you have a sample code that I can cut and paste and check.

Thanks
Muthiah
0
 
Mayank SAssociate Director - Product EngineeringCommented:
Hashtable env = new Hashtable () ;
env.put ( Context.INITIAL_CONTEXT_FACTORY, "com.ibm.ejs.ns.jndi.CNInitialContextFactory" ) ; // read this class-name from a properties-file - this name is for Websphere
env.put ( Context.PROVIDER_URL, "IIOP:///" ) ; // read this from a properties-file too
InitialContext mContext = new InitialContext ( env ) ;
DataSource datasource = ( DataSource ) mContext.lookup ( "jdbc/YourDataSource" ) ; // read this from a properties-file too
Connection connection = datasource.getConnection () ;
0
 
objectsCommented:
> I am using tomcat and oracle 10g. Do you have a sample code that I can cut and paste and check.

see the link I posted above, should only need minor tweaks to work with 10g

0
 
muthiahmerchantAuthor Commented:
I tried as per the following link

http://tomcat.apache.org/tomcat-5.0-doc/printer/jndi-datasource-examples-howto.html.

I copied the section in server.xml before </host>. The article talks about pasting it between </context> and </host>. My server.xml does not have a </context> tag.

I pasted the web.xml section in the web.xml under myproject/web/WEB-INF/web.xml

This is the class that returns a connection

public class DBConn {

    public static Connection  OracleConn() {
       Connection connection = null;
        try {
            // Load the JDBC driver. classes12.jar should be present in WEB-INF/lib/
            String driverName = "oracle.jdbc.driver.OracleDriver";
            Class.forName(driverName);
         
            Context initContext = new InitialContext();
            Context envContext  = (Context)initContext.lookup("java:/comp/env");
            DataSource ds = (DataSource)envContext.lookup("jdbc/myoracle");
           
            connection = DriverManager.getConnection("url","username","password");

        } catch (ClassNotFoundException e) {
            e.printStackTrace();
        }catch(SQLException e){
            e.printStackTrace();
        } catch (Exception NamingException) {
            NamingException.printStackTrace();
        }
       return  connection;
    }
   
}

I am assuming the "url", "username" and "password" is comming from server.xml.

When I try to run it I get the following error
java.sql.SQLException: No suitable driver
        at java.sql.DriverManager.getConnection(DriverManager.java:545)
        at java.sql.DriverManager.getConnection(DriverManager.java:171)
        at com.myapp.database.DBConn.OracleConn(DBConn.java:44)
        at com.myapp.struts.CustomerSearch.firstNameSearch(CustomerSearch.java:58)
        at com.myapp.struts.ProcessCustomerData.execute(ProcessCustomerData.java:22)

Thanks for the help
0
 
Mayank SAssociate Director - Product EngineeringCommented:
>> String driverName = "oracle.jdbc.driver.OracleDriver";
>> Class.forName(driverName);

- not required, since you are using data-source.
0
 
Mayank SAssociate Director - Product EngineeringCommented:
>> My server.xml does not have a </context> tag.

You can add it.
0
 
Mayank SAssociate Director - Product EngineeringCommented:
Ok. Thanks, Annie.
0
 
muthiahmerchantAuthor Commented:
This is what my class looks like

/*
 * DBConn.java
 *
 * Created on April 4, 2006, 1:47 PM
 *
 * To change this template, choose Tools | Template Manager
 * and open the template in the editor.
 */

package com.myapp.database;

import java.sql.*;
import javax.sql.*;
import javax.naming.*;

public class DBConn {
   
    /** Creates a new instance of DBConn */
    public static Connection  OracleConn() {
       Connection connection = null;
        try {
           
            Context initContext = new InitialContext();
            Context envContext  = (Context)initContext.lookup("java:/comp/env");
            DataSource ds = (DataSource)envContext.lookup("jdbc/myoracle");
            connection = ds.getConnection();

        }catch(SQLException e){
            e.printStackTrace();
        } catch (Exception NamingException) {
            NamingException.printStackTrace();
        }
       return  connection;
    }
   
}

My server.xml looks like this. I added the <context> tag at the bottom. Can someone please tell me if I added it at the right place.

<?xml version="1.0" encoding="UTF-8"?>
<!-- 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="8025" shutdown="SHUTDOWN">
  <!-- Comment these entries out to disable JMX MBeans support used for the
       administration web application -->
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
  <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
  <!-- Global JNDI resources -->
  <GlobalNamingResources>
    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users -->
    <Resource auth="Container" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" name="UserDatabase" pathname="conf/tomcat-users.xml" type="org.apache.catalina.UserDatabase"/>
  </GlobalNamingResources>
  <!-- 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="Catalina">
    <!-- 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 5 documentation bundle for more detailed
         instructions):
         * If your JDK version 1.3 or prior, 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 URIEncoding="utf-8" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="8084" redirectPort="8443"/>
    <!-- Note : To disable connection timeouts, set connectionTimeout value
     to 0 -->
    <!-- Note : To use gzip compression you could set the following properties :
      
                     compression="on"
                     compressionMinSize="2048"
                     noCompressionUserAgents="gozilla, traviata"
                     compressableMimeType="text/html,text/xml"
      -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector port="8443" maxHttpHeaderSize="8192"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector enableLookups="false" port="8009" protocol="AJP/1.3" redirectPort="8443"/>
    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector port="8082"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" acceptCount="100" connectionTimeout="20000"
               proxyPort="80" disableUploadTimeout="true" />
    -->
    <!-- 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). -->
    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">        
    -->
    <!-- Define the top level container in our container hierarchy -->
    <Engine defaultHost="localhost" name="Catalina">
      <!-- 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.4
           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"/>
      -->
      <!-- Because this Realm is here, an instance will be shared globally -->
      <!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  -->
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/>
      <!-- Comment out the old realm but leave here for now in case we
           need to go back quickly -->
      <!--
      <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"
             driverName="org.gjt.mm.mysql.Driver"
          connectionURL="jdbc:mysql://localhost/authority"
         connectionName="test" connectionPassword="test"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->
      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             driverName="oracle.jdbc.driver.OracleDriver"
          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
         connectionName="scott" connectionPassword="tiger"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->
      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             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
           Note: XML Schema validation will not work with Xerces 2.2.
       -->
      <Host appBase="webapps" autoDeploy="false" name="localhost" unpackWARs="true" xmlNamespaceAware="false" xmlValidation="false">
        <!-- Defines a cluster for this node,
             By defining this element, means that every manager will be changed.
             So when running a cluster, only make sure that you have webapps in there
             that need to be clustered and remove the other ones.
             A cluster has the following parameters:

             className = the fully qualified name of the cluster class

             name = a descriptive name for your cluster, can be anything

             mcastAddr = the multicast address, has to be the same for all the nodes

             mcastPort = the multicast port, has to be the same for all the nodes
             
             mcastBindAddr = bind the multicast socket to a specific address
             
             mcastTTL = the multicast TTL if you want to limit your broadcast
             
             mcastSoTimeout = the multicast readtimeout

             mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat

             mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received

             tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes

             tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
                                in case of multiple ethernet cards.
                                auto means that address becomes
                                InetAddress.getLocalHost().getHostAddress()

             tcpListenPort = the tcp listen port

             tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
                                  has a wakup bug in java.nio. Set to 0 for no timeout

             printToScreen = true means that managers will also print to std.out

             expireSessionsOnShutdown = true means that

             useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
                            false means to replicate the session after each request.
                            false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
                            <%
                            HashMap map = (HashMap)session.getAttribute("map");
                            map.put("key","value");
                            %>
             replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
                               * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
                               * Synchronous means that the thread that executes the request, is also the
                               thread the replicates the data to the other nodes, and will not return until all
                               nodes have received the information.
                               * Asynchronous means that there is a specific 'sender' thread for each cluster node,
                               so the request thread will queue the replication request into a "smart" queue,
                               and then return to the client.
                               The "smart" queue is a queue where when a session is added to the queue, and the same session
                               already exists in the queue from a previous request, that session will be replaced
                               in the queue instead of replicating two requests. This almost never happens, unless there is a
                               large network delay.
        -->
        <!--
            When configuring for clustering, you also add in a valve to catch all the requests
            coming in, at the end of the request, the session may or may not be replicated.
            A session is replicated if and only if all the conditions are met:
            1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
            2. a session exists (has been created)
            3. the request is not trapped by the "filter" attribute

            The filter attribute is to filter out requests that could not modify the session,
            hence we don't replicate the session after the end of this request.
            The filter is negative, ie, anything you put in the filter, you mean to filter out,
            ie, no replication will be done on requests that match one of the filters.
            The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.

            filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
            ending with .gif and .js are intercepted.
           
            The deployer element can be used to deploy apps cluster wide.
            Currently the deployment only deploys/undeploys to working members in the cluster
            so no WARs are copied upons startup of a broken node.
            The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
            When a new war file is added the war gets deployed to the local instance,
            and then deployed to the other instances in the cluster.
            When a war file is deleted from the watchDir the war is undeployed locally
            and cluster wide
        -->
        <!--
        <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
                 managerClassName="org.apache.catalina.cluster.session.DeltaManager"
                 expireSessionsOnShutdown="false"
                 useDirtyFlag="true"
                 notifyListenersOnReplication="true">

            <Membership
                className="org.apache.catalina.cluster.mcast.McastService"
                mcastAddr="228.0.0.4"
                mcastPort="45564"
                mcastFrequency="500"
                mcastDropTime="3000"/>

            <Receiver
                className="org.apache.catalina.cluster.tcp.ReplicationListener"
                tcpListenAddress="auto"
                tcpListenPort="4001"
                tcpSelectorTimeout="100"
                tcpThreadCount="6"/>

            <Sender
                className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
                replicationMode="pooled"
                ackTimeout="15000"/>

            <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
                   filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;"/>
                   
            <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
                      tempDir="/tmp/war-temp/"
                      deployDir="/tmp/war-deploy/"
                      watchDir="/tmp/war-listen/"
                      watchEnabled="false"/>
        </Cluster>
        -->
        <!-- 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" />
        -->
        <!-- 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" resolveHosts="false"/>
        -->
        <!-- 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.
             This access log implementation is optimized for maximum performance,
             but is hardcoded to support only the "common" and "combined" patterns.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->
        <!-- 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.
             This access log implementation is optimized for maximum performance,
             but is hardcoded to support only the "common" and "combined" patterns.

             This valve use NIO direct Byte Buffer to asynchornously store the
             log.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.ByteBufferAccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->
       
<context>
       
        <Resource name="jdbc/myoracle" auth="Container"
                    type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"
                    url="jdbc:oracle:thin:@xyz:1521:xyz"
                    username="xyz" password="xyz" maxActive="20" maxIdle="10"
            maxWait="-1"/>
      
      </context>
      </Host>
    </Engine>
  </Service>
</Server>

Thanks
0
 
Mayank SAssociate Director - Product EngineeringCommented:
Not sure, haven't worked with it since long :) you will find a working sample here:

http://www.experts-exchange.com/Programming/Programming_Languages/Java/Q_20954702.html BTW, I guess your structure is correct. Do you face any problems when you run it?
0
 
muthiahmerchantAuthor Commented:
Thanks mayankeagle

I replaced <context> with
<Context path="/Grayline" docBase="C:\Documents and Settings\mradha\Grayline\" debug="5" reloadable="true" crossContext="true">

I suppose /Grayline is the name of the application. when I run the application It does not go to index.jsp instead it shows me the directory listing for Grayline.

I am using tomcat, but my application is not under the webapps folder of tomcat. its in the following dir structure.
C:\Documents and Settings\mradha\Grayline.

My directory structure if of this sort
C:\Documents and Settings\mradha\Grayline
C:\Documents and Settings\mradha\Grayline\build
C:\Documents and Settings\mradha\Grayline\build\web
C:\Documents and Settings\mradha\Grayline\build\index.jsp
C:\Documents and Settings\mradha\Grayline\build\web\WEB-INF\classes

Can someone direct me, how to do this, please.

Thanks

0
 
objectsCommented:
> I suppose /Grayline is the name of the application. when I run the application It does not go to index.jsp instead it shows me the directory listing for Grayline.

Is index.jsp in your welcome file list in web.xml?
0
 
muthiahmerchantAuthor Commented:
I fixed the last issue by setting the docBase to docBase="C:\Documents and Settings\mradha\Grayline\build\web", but now I get this error

org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver'

I am using the tomcat that is bundled with netbeans. My tomcat folder does not come with common folder,hence I created a common/lib folder and placed classes12.jar in it. I also added classes12.jar in the classpath. but still get the same error.

I have increased the points for all the help that is being provided.

Thanks
0
 
objectsCommented:
> hence I created a common/lib folder and placed classes12.jar in it

where did u create it?
0
 
muthiahmerchantAuthor Commented:
When I installed netbeans there was no common/lib

I added common/lib, now my folder structure looks like this

C:\Documents and Settings\mradha\.netbeans\5.0\jakarta-tomcat-5.5.9_base\common\lib\classes12.jar

Thanks

0
 
Mayank SAssociate Director - Product EngineeringCommented:
What happens when you put classes12.jar onto your WEB-INF\lib folder?
0
 
muthiahmerchantAuthor Commented:
when I put classes12.jar in WEB-INF/lib folder it works fine for regular database connection, where you specify the username, password, url etc. but it dosn't work when I use a datasource.

I read a post somewhere that when you use datasouce, you have put the classes12.jar file in common/lib. only problem is that I don't know how to make the tomcat that came with netbeans to look for it in some other place. Is there a config file that tells tomcat or netbeans or struts or ... to look for classes12.jar in common/lib folder.

Also I download a new version of tomcat, this one came with the common/lib folder, I dropped the classes12.jar in this folder and copied the war file to this location and walla, it worked.

But I would like to configure netbeans to work.
0
 
Mayank SAssociate Director - Product EngineeringCommented:
>> Is there a config file that tells tomcat or netbeans or struts or ... to look for classes12.jar in common/lib folder

No, generally all JARs available in common\lib are available to all applications that run on the server.

>> I dropped the classes12.jar in this folder and copied the war file to this location and walla, it worked

That means for some reason, the one which comes bundled with Netbeans is looking in some other location. I haven't worked with Tomcat bundled with Netbeans, so I'm not sure. What directories do you have under "jakarta-tomcat-5.5.9_base"?
0
 
muthiahmerchantAuthor Commented:
Folder struture is of this sort

C:\Documents and Settings\mradha\.netbeans\5.0\jakarta-tomcat-5.5.9_base\conf\catalina\localhost
C:\Documents and Settings\mradha\.netbeans\5.0\jakarta-tomcat-5.5.9_base\logs
C:\Documents and Settings\mradha\.netbeans\5.0\jakarta-tomcat-5.5.9_base\temp
C:\Documents and Settings\mradha\.netbeans\5.0\jakarta-tomcat-5.5.9_base\webapps
C:\Documents and Settings\mradha\.netbeans\5.0\jakarta-tomcat-5.5.9_base\work\cataline\localhost
0
 
muthiahmerchantAuthor Commented:
Hi Folks

A big hearty thanks to all of you who helped to set up a datasource. I was finally able to add to get everything up and running. The thing is netbeans has another copy under programfiles where it looks for classes12.jar. I added it there and it worked. Netbeans keeps a config file where it looks for stuff.

Thanks
0
 
objectsCommented:
no worries :)
0
 
Mayank SAssociate Director - Product EngineeringCommented:
:-)
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 10
  • 9
  • 8
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now