How to lookup a datasource

In Jdevleoper 9i(9.0.3.1) when I am developing servlets there are codes like :
DataSource ds = null;
public void init() throws ServletException {
try {
InitialContext ic = new InitialContext();
ds = (DataSource) ic.lookup("java:comp/env/jdbc/Conn_scottDS");
catch (NamingException ne) {
throw new ServletException(ne);
the IE displays: cannot find jdbc/Conn_scottDS
I don't know what files I should config and how I can config files in jdevloper9i.
anybody help me,thanks

Check up JDEV_HOME\j2ee\home\config\data-sources.xml make sure that you have datasource that you are accessing is configured here. And also establish a database connection from Jdev to this datasource.

Similar Messages

  • How to handle multiple datasources in a web application?

    I have a J2EE Web application with Servlets and Java ServerPages. Beside this I have a in-house developed API for certain services built using Hibernate and Spring with POJO's and some EJB.
    There are 8 databases which will be used by the web application. I have heard that multiple datasources with Spring is hard to design around. Considering that I have no choice not to use Spring or Hibernate as the API's are using it.
    Anyone have a good design spesification for how to handle multiple datasources. The datasource(database) will be chosen by the user in the web application.

    Let me get this straight. You have a web application that uses spring framework and hibernate to access the database. You want the user to be able to select the database that he wants to access using spring and hibernate.
    Hopefully you are using the Spring Framework Hibernate DAO. I know you can have more that one spring application context. You can then trying to load a seperate spring application context for each database. Each application context would have it's own configuration files with the connection parameters for each datasource. You could still use JNDi entries in the web.xml for each datasource.
    Then you would need a service locater so that when a user selected a datasource he would get the application context for that datasource which he would use for the rest of his session.
    I think it is doable. It means a long load time. And you'll need to keep the application contexts as small as possible to conserve resources.

  • How to create  a datasource for 0COSTCENTER to load data in csv file  in BI

    how to create  a datasource for 0COSTCENTER to load data in csv file  in BI 7.0 system
    can you emil me the picture of the step about how to  loaded individual values of the hierarchy using CSV file
    thank you very much
    my emil is <Removed>
    allen

    Step 1: Load Required Master Data for 0CostCenter in to BI system
    Step 2: Enable Characteristics to support Hierarchy for this 0Cost Center and specify the External Characteristic(In the Lowest Node or Last Node) while creation of this Characteristic InfoObject
    Step 3: On Last Node of Hierarchy Structure in the InfoObject, Right Click and then Create Hierarchy MANUALLY by Inserting the Master Data Value as BI dosent Support the Hierarchy load directly you need to do it manually....
    Step 4: Mapping
    Create Text Node thats the first node (Root Node)
    Insert Characteristic Nodes
    Insert the Last Node of the Hierarchy
    Then you need to create a Open hub Destination for extracting data into the .csv file...
    Step1 : Create the Open Hub Destination give the Master Data table name and enter all the fields required....and create the transformations for this Open Hub connecting to the External file or excel file source...then give the location on to your local disk or path of the server in the first tab and request for the data...It should work alright let me know if you need anything else...
    Thanks,
    Sandhya

  • What is Data source? How to create a datasource?

    Hi All,
        anybody could you explain me What is Data source and how to create data source?
    How it is related to BW.
    Points will be rewarded for all the useful answers.
    Priya.

    Hi Priya,
    You can Create DataSource for Different Source systems.
    Chech these URLs.
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/01ed2fe3811a77e10000000a422035/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/00153831035167e10000000a1553f6/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/42/fdccb72aa95277e10000000a1553f7/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/93dbdbff0b274ee10000000a422035/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/03b1f4dc636e72e10000000a422035/content.htm
    steps in 'how to delta generic datasource'
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    /message/3471234#3471234 [original link is broken]
    Re: How to create datasource
    <b>Reward points for helpful answers</b>
    Satish

  • Caching of JNDI lookup'ed DataSources???

    What is the recommened pratice, using bean-managed Entity Beans, in regards to
    looking up the DataSource object from the JNDI tree?
    Is the best way to store the DataSource object in the session context when setEntityContext
    is called and release it on unsetEntityContext?
    or
    is it best if we lookup the DataSource object in every method and returns it back
    to the pool at the end of the same method? Like in the PETStore example from SUN.
    In a article from SUN "Seven Rules for Optimizing Entity Beans" they recommend
    to cache even DataSource objects. What is BEA's recommendation on this?
    http://developer.java.sun.com/developer/technicalArticles/ebeans/sevenrules
    Regards,
    Steen
    http://developer.java.sun.com/developer/technicalArticles/ebeans/sevenrules/

    I recommend doing the JNDI look-up in the setEntityContext method and
    storing the DataSource in a member variable.
    You should get the JDBC connection from the DataSource in each method
    and return it in each method.
    -- Rob
    Steen Laursen wrote:
    >
    What is the recommened pratice, using bean-managed Entity Beans, in regards to
    looking up the DataSource object from the JNDI tree?
    Is the best way to store the DataSource object in the session context when setEntityContext
    is called and release it on unsetEntityContext?
    or
    is it best if we lookup the DataSource object in every method and returns it back
    to the pool at the end of the same method? Like in the PETStore example from SUN.
    In a article from SUN "Seven Rules for Optimizing Entity Beans" they recommend
    to cache even DataSource objects. What is BEA's recommendation on this?
    http://developer.java.sun.com/developer/technicalArticles/ebeans/sevenrules
    Regards,
    Steen
    http://developer.java.sun.com/developer/technicalArticles/ebeans/sevenrules/
    AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
    by Michael Girdley, Rob Woollen, and Sandra Emerson
    http://learnWebLogic.com

  • Format of the JNDI name for lookup in DataSource

    Hi
    a) I have made a datasource in Weblogic 10.3 called SQL and its JNDI name as jdbc/SQLDS.
    The driver was BEA'S Type 4 Driver for MS SQL Server
    Now I am trying to lookup the datasource through an application. I have used the following
    lines of code:
    InitialContext context = new InitialContext();
    DataSource ds = context.lookup("jdbc/SQLDS");
    Connection conn = ds.getConnection();
    The Application was a success.
    I saw in some articles that you can refer to the datasource by even java:comp/env/jdbc/SQLDS,
    instead of just jdbc/SQLDS. I tried both ways and I was able to run the application.
    b) Then I made another datasource in Weblogic 10.3 called SQL1 and its JNDI name as jdbc/SQL1.
    The driver was MS SQL Server Type 4 Driver for versions 2000, 2005
    Now I am trying to lookup the datasource through an application. I have used the following
    lines of code:
    InitialContext context = new InitialContext();
    DataSource ds = context.lookup("jdbc/SQL1");
    Connection conn = ds.getConnection();
    The Application was a success.
    I saw in some articles that you can refer to the datasource by even java:comp/env/jdbc/SQL1,
    instead of just jdbc/SQL1. I tried the first way and it didnt work. It gave me a NullPointerException
    at the line Connection conn = ds.getConnection();
    c)Then I made a 3rd datasource in Weblogic 10.3 called SQL2 and its JNDI name as jdbc/SQL2DS.
    The driver was MS SQL Server Type 4 Driver for versions 2000, 2005
    Now I am trying to lookup the datasource through an application. I have used the following
    lines of code:
    InitialContext context = new InitialContext();
    DataSource ds = context.lookup("jdbc/SQL2DS");
    Connection conn = ds.getConnection();
    The Application was a success.
    I saw in some articles that you can refer to the datasource by even java:comp/env/jdbc/SQL2DS,
    instead of just jdbc/SQL2DS. I tried the first way and it didnt work. Again, it gave me a NullPointerException
    at the line Connection conn = ds.getConnection();
    I was confused why the 2nd and 3rd way didnt work . Is it becaue I used Microsoft's MS SQL Server Type 4 Driver?
    I have added the jar file in the WEBLOGIC_CLASSPATH. Why is it not recognising java:comp/env/jdbc/SQL2DS ?
    I would be grateful if somebody could give me ideas on this...
    Thanks
    Neeti

    To use application scoped or indirect JNDI lookups (i.e. java:comp/env/...) you usually need to define a &lt;resource-ref&gt; entry in your deployment descriptor(s). Not sure what type of application you are using to test (web-app, EJB,) but for java:comp/env/ lookups to work, you need to define resource references. The fact that your first test succeeded is somewhat strange. Without the resource reference definitions, I would have expected your JNDI lookups to fail with a NamingException instead of the lookup returning NULL for the datasource.
    Assuming you are doing your test from a web-app, you need to add &lt;resource-ref&gt; definitions to your web.xml file similar to the following:
    &lt;resource-ref&gt;
    &lt;res-ref-name&gt;*jdbc/SQL2DS*&lt;/res-ref-name&gt;
    &lt;res-type&gt;java.sql.DataSource&lt;/res-type&gt;
    &lt;res-auth&gt;Container&lt;/res-auth&gt;
    &lt;/resource-ref&gt;
    and then add &lt;reference-descriptor&gt; definitions to your weblogic.xml file similar to the following:
    &lt;reference-descriptor&gt;
    &lt;resource-description&gt;
    &lt;res-ref-name&gt;*jdbc/SQL2DS*&lt;/res-ref-name&gt;
    &lt;jndi-name&gt;*jdbc/SQL2DS*&lt;/jndi-name&gt;
    &lt;/resource-description&gt;
    &lt;/reference-descriptor&gt;
    Once you do these steps your lookup("java:comp/env/jdbc/SQL2DS") should function properly from within your web-app.

  • How to find which datasource are using  tables AFRU ,CAUFV and AUFM

    *how to find which datasource are using  tables AFRU ,CAUFV and AUFM*

    Hi,
    You can enter your table names in SE11 transaction and click "Display" and again click "Where -Used-List". Then it will show all the places where these tables are used(Datasources)
    Hope this helps.....
    Regards,
    SUman

  • How to find the datasource of the planned ship date

    Hi All,
    how to find the datasource of the planned ship date in shipping history report , whether we go for enhancement or we can get from SAP Std. pls help me on step by step process.
    Thanks and Regards
    malempati

    Hi Govardhan,
    The best place to start looking for the standard data source will be http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm .
    If you can not find anything, from the source table, find if the table is included in any of the structures/views for BW. Hope this helps.
    Thanks and Regards
    Subray Hegde

  • How   to extract retail  datasources please describe clearely

    how   to extract retail  datasources please describe clearely

    Dear,
    http://help.sap.com/saphelp_nw04/helpdata/en/39/e531c93747da4a8806612212b013b4/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/8e/65f438c842cc2be10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/35/e58282fe8711d3b49f006094b9301e/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/73/d26594107711d4af1e080009d2232d/content.htm
    Also check in:
    www.service.sap.com/bi -->>solution detail -->>Industry Portfolios -->> Sap Retail
    Thanks

  • How to find which datasource is using table JCDS?

    How to find which datasource is using table JCDS?

    Hi,
    Please find the below link and identify whether will it meet your requirement or not ... If it meets your requirement then I can provide you more documents related to the same which we have in our project.   We were using the same for Plant Maintanance project...
    For this report the required information is gathering from the different data sources from the ECC system. This report requires object status functional location attributes, Equipment attributes and some specific information apart from normal transaction data for an order.
    u2022     Main feeding data sources for this report are 2LIS_17_ORDER and 2LIS_18_ORDER.
    u2022     Requires the object status data (system status, number object status and un-number system status) is feeding from different DSO where the status data is staging with different data flow.
    u2022     Requires the Order planned end date which is dependent on the operation  planned completion date. so we are feeding this field from Operationu2019s DSO where the planned date is staging with different data flow.
    u2022     Required characteristic data and attributes of the Functional location  is getting from the master data .The 0FUNCT_LOC is updating by master data data sources
    u2022     Required standard class  of the functional location is updating from other DSO where the  classification  data is staging with the help of different data flow.
    2LIS_17_ORDER and 2LIS_18_ORDER Data flow Details : No enhancement was done for these data sources .
    Status Data Flow Details:
    The status data is staged because ,this dat is required for the reports based on the Orders, Operations , Notifications, Functional Location and Equipment.
    To load suitable data to different DSOs from the Status DSO we maintain the Filters for status profile and status at DTP level.
    Required status change dates  are deriving based on changed on date ,system status while loading from status DSO to Order DSO.
    The system status ,Number object status and un- numberd object status are feeding from status DSO only.The status DSO is updating by u20180TE_OBJ_STATUS_HISTu2019.This Is based on the tables JCDS,JSTO and T000.
    JCDS     MANDT     =     JSTO     MANDT
    JCDS     OBJNR          =     JSTO     OBJNR
    T000     MANDT     =     JCDS     MANDT
    This DS has enhanced for the below  two fields
    1.     Order Number
    2.     Operation/Activity Number
    The Logic to populate the above two fileds is as below.
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e4/1522bae6aa46b8802dca454e846d58/frameset.htm
    regards
    BVR

  • Error while configuring kodo to lookup a datasource

    We had a working application using EEPersistenceManagerFactory
    I changed the kodo.properties to lookup a non XA JDBC datasource.
    After that the application is working fine (it creates
    ,updates,deletes,finds record in the DB)
    but SystemOut.log has the following error for every operation
    We are using Kodo 2.5.0, Websphere 5.0 and Oracle 8
    How can we avoid getting this error ?.
    We tried to find any property on the Websphere datasource which can be
    altered to avoid this error but no luck.
    Thanks
    Paresh
    [10/7/03 15:30:45:467 IST] 3d8b2d1a MCWrapper E J2CA0081E: Method
    destroy failed while trying to execute method destroy on ManagedConnection
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@437f6d23 from resource
    <null>. Caught exception: com.ibm.ws.exception.WsException: DSRA0080E: An
    exception was received by the Data Store Adapter. See original exception
    message: Cannot call 'cleanup' on a ManagedConnection while it is still in
    a transaction..
         at
    com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:222)
         at
    com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:172)
         at
    com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:182)
         at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions(WSRdbManagedConnectionImpl.java:1826)
         at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.destroy(WSRdbManagedConnectionImpl.java:1389)
         at com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1032)
         at
    com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:259)
         at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:777)
         at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1304)
         at
    com.ibm.ejs.j2c.ConnectionEventListener.connectionClosed(ConnectionEventListener.java:195)
         at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConnectionClosedEvent(WSRdbManagedConnectionImpl.java:843)
         at
    com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.closeWrapper(WSJdbcConnection.java:569)
         at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:132)
         at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:814)
         at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java(Inlined
    Compiled Code))
         at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java(Compiled
    Code))
         at
    com.solarmetric.kodo.runtime.StateManagerImpl.loadFields(StateManagerImpl.java(Compiled
    Code))
         at
    com.solarmetric.kodo.runtime.StateManagerImpl.preSerialize(StateManagerImpl.java:784)
         at com.paresh.core.vo.Release.jdoPreSerialize(Release.java)
         at com.paresh.core.vo.Release.writeObject(Release.java)
         at java.lang.reflect.Method.invoke(Native Method)
         at
    com.ibm.rmi.io.IIOPOutputStream.invokeObjectWriter(IIOPOutputStream.java:703)
         at com.ibm.rmi.io.IIOPOutputStream.outputObject(IIOPOutputStream.java:671)
         at
    com.ibm.rmi.io.IIOPOutputStream.simpleWriteObject(IIOPOutputStream.java:146)
         at
    com.ibm.rmi.io.ValueHandlerImpl.writeValueInternal(ValueHandlerImpl.java:217)
         at com.ibm.rmi.io.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:144)
         at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1590)
         at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1107)
         at
    com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie.findCorrectionAction(_EJSRemoteStatelessValidation_da16513c_Tie.java:309)
         at
    com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie._invoke(_EJSRemoteStatelessValidation_da16513c_Tie.java:104)
         at
    com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:582)
         at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:437)
         at com.ibm.rmi.iiop.ORB.process(ORB.java:320)
         at com.ibm.CORBA.iiop.ORB.process(ORB.java:1544)
         at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2063)
         at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
         at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
    kodo.properties
    com.solarmetric.kodo.LicenseKey=
    #com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=java:/TransactionManager
    com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=TransactionFactory
    TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager
    #com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.InvocationManagedRuntime
    com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.AutomaticManagedRuntime
    #javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
    javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory
    javax.jdo.option.ConnectionFactoryName=ds/kodo/DataSource1
    javax.jdo.option.Optimistic=true
    javax.jdo.option.RetainValues=true
    javax.jdo.option.NontransactionalRead=true
    #com.solarmetric.kodo.DataCacheClass=com.solarmetric.kodo.runtime.datacache.plugins.CacheImpl
    # Changing these to a non-zero value will dramatically increase
    # performance, but will cause in-memory databases such as Hypersonic
    # SQL to never exit when your main() method exits, as the pooled
    # connections in the in-memory database will cause a daemon thread to
    # remain running.
    javax.jdo.option.MinPool=5
    javax.jdo.option.MaxPool=10

    We do have a makeTransientAll() before the object returns from Session
    Bean.
    We also tried the JCA path
    After installing the JCA RAR and doing a lookup for
    PersistenceManagetFactory the same code is not throwing any exception.
    The exception is thrown only if datasource is used.
    Thanks
    Paresh
    Marc Prud'hommeaux wrote:
    Paresh-
    It looks like you are returning a collection of instances from an EJB,
    which will cause them to be serialized. The serialization is happening
    outside the context of a transaction, and Kodo needs to obtain a
    connection. Websphere seems to not like that.
    You have a few options:
    1. Call makeTransientAll() on all the instances before you return them
    from your bean methods
    2. Manually instantiate all the fields yourself before sending them
    back. You could use a bogus ObjectOutputStream to do this.
    3. In 3.0, you can use the new detach() API to detach the instances
    before sending them back to the client.
    In article <[email protected]>, Paresh wrote:
    We had a working application using EEPersistenceManagerFactory
    I changed the kodo.properties to lookup a non XA JDBC datasource.
    After that the application is working fine (it creates
    ,updates,deletes,finds record in the DB)
    but SystemOut.log has the following error for every operation
    We are using Kodo 2.5.0, Websphere 5.0 and Oracle 8
    How can we avoid getting this error ?.
    We tried to find any property on the Websphere datasource which can be
    altered to avoid this error but no luck.
    Thanks
    Paresh
    [10/7/03 15:30:45:467 IST] 3d8b2d1a MCWrapper E J2CA0081E: Method
    destroy failed while trying to execute method destroy on ManagedConnection
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@437f6d23 from resource
    <null>. Caught exception: com.ibm.ws.exception.WsException: DSRA0080E: An
    exception was received by the Data Store Adapter. See original exception
    message: Cannot call 'cleanup' on a ManagedConnection while it is still in
    a transaction..
         at
    com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:222)
         at
    com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:172)
         at
    com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:182)
         at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions(WSRdbManagedConnectionImpl.java:1826)
         at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.destroy(WSRdbManagedConnectionImpl.java:1389)
         at com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1032)
         at
    com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:259)
         at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:777)
         at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1304)
         at
    com.ibm.ejs.j2c.ConnectionEventListener.connectionClosed(ConnectionEventListener.java:195)
         at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConnectionClosedEvent(WSRdbManagedConnectionImpl.java:843)
         at
    com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.closeWrapper(WSJdbcConnection.java:569)
         at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:132)
         at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:814)
         at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java(Inlined
    Compiled Code))
         at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java(Compiled
    Code))
         at
    com.solarmetric.kodo.runtime.StateManagerImpl.loadFields(StateManagerImpl.java(Compiled
    Code))
         at
    com.solarmetric.kodo.runtime.StateManagerImpl.preSerialize(StateManagerImpl.java:784)
         at com.paresh.core.vo.Release.jdoPreSerialize(Release.java)
         at com.paresh.core.vo.Release.writeObject(Release.java)
         at java.lang.reflect.Method.invoke(Native Method)
         at
    com.ibm.rmi.io.IIOPOutputStream.invokeObjectWriter(IIOPOutputStream.java:703)
         at com.ibm.rmi.io.IIOPOutputStream.outputObject(IIOPOutputStream.java:671)
         at
    com.ibm.rmi.io.IIOPOutputStream.simpleWriteObject(IIOPOutputStream.java:146)
         at
    com.ibm.rmi.io.ValueHandlerImpl.writeValueInternal(ValueHandlerImpl.java:217)
         at com.ibm.rmi.io.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:144)
         at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1590)
         at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1107)
         at
    com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie.findCorrectionAction(_EJSRemoteStatelessValidation_da16513c_Tie.java:309)
         at
    com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie._invoke(_EJSRemoteStatelessValidation_da16513c_Tie.java:104)
         at
    com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:582)
         at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:437)
         at com.ibm.rmi.iiop.ORB.process(ORB.java:320)
         at com.ibm.CORBA.iiop.ORB.process(ORB.java:1544)
         at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2063)
         at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
         at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
    kodo.properties
    com.solarmetric.kodo.LicenseKey=
    #com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=java:/TransactionManager
    >>
    >
    com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=TransactionFactory
    >>
    >
    TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager
    >>
    >>
    >
    #com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.InvocationManagedRuntime
    >>
    >
    com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.AutomaticManagedRuntime
    >>
    >>
    >
    #javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
    >>
    >
    javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory
    >>
    javax.jdo.option.ConnectionFactoryName=ds/kodo/DataSource1
    javax.jdo.option.Optimistic=true
    javax.jdo.option.RetainValues=true
    javax.jdo.option.NontransactionalRead=true
    #com.solarmetric.kodo.DataCacheClass=com.solarmetric.kodo.runtime.datacache.plugins.CacheImpl
    >>
    >>
    # Changing these to a non-zero value will dramatically increase
    # performance, but will cause in-memory databases such as Hypersonic
    # SQL to never exit when your main() method exits, as the pooled
    # connections in the in-memory database will cause a daemon thread to
    # remain running.
    javax.jdo.option.MinPool=5
    javax.jdo.option.MaxPool=10
    Marc Prud'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com

  • HELP : How to access a datasource rowset in the AM class ?

    Hi,
    i have an AM "TestAM" which contains the viewobject "ViewTest".
    in the class "TestAMImpl.java" i added a method called "verify()".
    in my JSP i have initialised the AM and a datasource based on the VO "ViewTest" :
    <jbo:ApplicationModule id="am" configname="TestAM.TestAMLocal" releasemode="Stateful" />
    <jbo:DataSource id="ds" appid="am" viewobject="ViewTest" />
    <%
    TestAM am = (TestAM) am.useApplicationModule();
    String Message = am.verify();
    %>
    My question is how to access to the rowset of the datasource "ds" in the code of the method
    "verify()" ?
    public class TestAMImpl extends ApplicationModuleImpl implements TestAM {
    public String verify()
    How to access the rowset initialised in the JSP???????????
    Thanks for your help

    This is correct. Think of the AM as having a hashtable of instances of view objects that you can lookup by instance name.
    The <jbo:DataSource> tag lets you lookup an instance by name in the AM and get a reference to it to use in the JSP page. Within your AMImpl class, you can either:
    [list]
    [*]Call findViewObject("YourViewInstanceName"), or
    [*]Just call the generated getYourViewInstanceName() method which is ok to call inside the Impl class to get hold of the same VO.
    [list]

  • How to resolve the datasource with Cloudspace database?

    Hi,
    I am running WebLogic 6.1 on Win2k and I have problem with
    Cloudscape database in Default Admin Server.
    === Start init method in myJDBCReadServlet.java ===
    Init Error: javax.naming.NameNotFoundException:
    Unable to resolve MyJDBCDataSource.
    Resolved: '' Unresolved:'MyJDBCDataSource' ; remaining name ''
    === Finish init method in myJDBCReadServlet.java ===
    1. I created simple table in the Cloudscape database using IJ utility and inserted
    some values:
    prompt>java -classpath %CLASSPATH%;..\lib\tools.jar COM.cloudscape.tools.ij
    ij version 3.5 (c) 1997-2000 Informix Software, Inc.
    ij> CONNECT 'jdbc:cloudscape:demo;create=true';
    WARNING 01J01: Database 'demo' not created, connection made to existing database
    instead.
    ij> SHOW CONNECTIONS;
    CONNECTION0* - jdbc:cloudscape:demo;create=true
    * = current connection
    ij> CREATE TABLE employee(name CHAR(25), location CHAR(20), id INTEGER);
    0 rows inserted/updated/deleted
    2. I created Connection Pool and Data Source using Default Console
    The Connection Pool configuration is the following:
    Name : MyJDBC Connection Pool
    URL : jdbc:cloudscape:demo
    Driver Classname: COM.cloudscape.core.JDBCDriver
    Properties : user=none password=none server=none
    My Data Source configuration is the following:
    Name : MyJDBC Data Source
    JNDI Name: MyJDBCDataSource
    Pool Name: MyJDBC Connection Pool
    I added the following line to myserver startup script to point
    to the database location:
    -Dcloudscape.system.home=./samples/eval/cloudscape/data
    3. I wrote the servlet and here is the piece of the myJDBCReadServlet
    code which generated the exception:
    public void init()
    System.out.println("=== Start init method in myJDBCReadServlet.java ===");
    try {
    ctx = new InitialContext();
    ds = (javax.sql.DataSource) ctx.lookup ("MyJDBCDataSource");
    } catch (Exception E) {
    System.out.println("Init Error: " + E);
    System.out.println("=== Finish init method in myJDBCReadServlet.java ===");
    Why it cannot find the database using JNDI name?
    Any help will be greatly appreciated,
    Jacob Nikom

    Great.
    Here is a link where you can find more cloudscape details:
    http://www.cloudscape.com/docs/doc_36/doc/html/coredocs/docs2.htm
    S.
    "jacob nikom" <[email protected]> wrote in message
    news:[email protected]...
    >
    Problem solved!
    Slava - thank you for your help.
    Yes, cloudscape.jar file should be on the CLASSPATH.
    I also put tools.jar from the same directory (I am not sure
    is it necessary or not, but I did not test it).
    However,it is not enough to run WebLogic with Cloudscape
    successfuly. You have to tell WebLogic where the database
    files are. To do it you have to include start-up option
    in the startWebLogic.cmd file.
    It looks like:
    -Dcloudscape.system.home="C:~\samples\eval\cloudscape\data"
    After that it runs. Actually, the file cloudscape.html in the
    directory ~\samples\eval\cloudscape has quite a bit of information.
    Unfortunately, it is difficult to comprehend it until you understand whatthe
    problem is.
    Regards,
    Jacob
    "Slava Imeshev" <[email protected]> wrote:
    Hi Jacob,
    You need to specify the Cloudscape classes in your
    CLASSPATH, which exists in weblogic/samples/eval/cloudscape/lib.
    Regards,
    Slava Imeshev
    "jacob nikom" <[email protected]> wrote in message
    news:[email protected]...
    Hi Slava,
    This is the source of the error:
    <Error> <JDBC>
    <Cannot startup connection pool "MyJDBC_Connection_Pool"
    Cannot load driver class: COM.cloudscape.core.JDBCDriver>
    but I don't know how to fix it.
    I don't know the name of the Cloudscape JDBC driver.
    I looked at cloudscape.jar file and found the following class file:
    COM/cloudscape/core/JDBCDriver.class
    Is it the right driver?
    I tried to use COM.cloudscape.core.XADataSource driver
    classname, but got the same problem - WebLogic cannot find it.
    Which .jar file has correct Cloudscape JDBC driver?
    What else should I do to ensure that driver loads properly?
    Thank you,
    Jacob Nikom
    "Slava Imeshev" <[email protected]> wrote:
    Ok. I don't see that neither connection pool nor data source
    trying to start. You did not added targets to them or may be
    you provided wrong target.
    S.
    "jacob nikom" <[email protected]> wrote in message
    news:[email protected]...
    Hi Slava,
    Thank you for your response. I am sending you the full
    log as .txt file attachment. It is not very large in order
    to zip it.
    I added some Cloudscape parameters to the startup script,
    so you can see them there. They show to the WebLogic where
    the database is located.
    Also, I think the database was running because I could see
    my tables using IJ utility (Cloudscape tool), however I am
    not sure how Cloudscape exactly starts and runs.
    Regards,
    Jacob Nikom
    "Slava Imeshev" <[email protected]> wrote:
    Could you zip the whole log and send it to me?
    I just want to see what the console says about
    creation of your datasources and pools.
    Regards,
    Slava Imeshev
    "jacob nikom" <[email protected]> wrote in message
    news:[email protected]...
    Hi Slava,
    This is the output with Stdout severity threshold = "info".
    I only split a couple of very long lines.
    <Oct 2, 2001 6:29:33 PM EDT> <Info> <HTTP>
    <[WebAppServletContext(5891807,myJDBCReadServlet,/myJDBCReadServlet)]
    myJDBCReadServlet:
    init>
    === Start init method in myJDBCReadServlet.java ===
    Init Error: javax.naming.NameNotFoundException: Unable to resolveMyJDBC_Data_Source.
    Resolved: '' Unresolved:'MyJDBC_Data_Source' ; remaining name
    === Finish init method in myJDBCReadServlet.java ===
    === Start service method in myJDBCReadServlet.java ===
    Service Error: java.lang.NullPointerException
    === Finish service method in myJDBCReadServlet.java ===
    "jacob nikom" <[email protected]> wrote:
    Hi Slava,
    Thank you very much for your response.
    I followed your advice and changed the names
    of my ConnectionPool and DataSource, removing
    all spaces. Now they are MyJDBC_Data_Source and
    MyJDBC_Connection_Pool (is underscore OK?).
    I think I turned on the message level on "info" few days ago.
    Could you remind me how to check it?
    I am sending you the full log of my session starting
    from the beginning up to the crush:
    prompt>"C:\WebLogic61\jdk131\bin\java" -hotspot -ms64m -mx64m
    -classpath
    .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\lib\cos.jar
    -Dweblogic.Domain=mydomain -Dweblogic.Name=myserver
    "-Dbea.home=C:\WebLogic61"
    -Dcloudscape.system.home="C:\WebLogic61\wlserver6.1\samples\eval\cloudsc
    a
    p
    e
    \data"
    >
    -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=false
    >
    "-Djava.security.policy==C:\WebLogic61\wlserver6.1/lib/weblogic.policy"
    weblogic.Server
    <Oct 2, 2001 5:21:57 PM EDT> <Info> <Security> <Getting bootpassword
    from user.>
    Enter password to boot WebLogic server:
    Starting WebLogic Server ....
    <Oct 2, 2001 5:22:02 PM EDT> <Notice> <Management> <Loadingconfiguration
    file
    .\config\mydomain\config.xml ...>
    <Oct 2, 2001 5:22:07 PM EDT> <Notice> <WebLogicServer> <StartingWebLogic
    Admin
    Server "myserver" for domain "mydomain">
    <Oct 2, 2001 5:22:10 PM EDT> <Notice> <Management> <Starting
    discovery
    of Managed
    Server...
    This feature is on by default, you may turn this off bypassing -Dweblogic.management.discover=false>
    <Oct 2, 2001 5:22:17 PM EDT> <Notice> <Management> <Application
    Poller
    started
    for development server.>
    <Oct 2, 2001 5:22:17 PM EDT> <Notice> <WebLogicServer><SSLListenThread
    listening
    on port 7002>
    <Oct 2, 2001 5:22:17 PM EDT> <Notice> <WebLogicServer>
    <ListenThread
    listening
    on port 7001>
    <Oct 2, 2001 5:22:18 PM EDT> <Notice> <WebLogicServer> <StartedWebLogic
    Admin
    Server "myserver" for
    domain "mydomain" running in Development Mode>
    === Start init method in myJDBCReadServlet.java ===
    Init Error: javax.naming.NameNotFoundException: Unable to
    resolve
    MyJDBC_Data_Source.
    Resolved: '' Unresolved:'MyJDBC_Data_Source' ; remaining name
    === Finish init method in myJDBCReadServlet.java ===
    === Start service method in myJDBCReadServlet.java ===
    Service Error: java.lang.NullPointerException
    "Slava Imeshev" <[email protected]> wrote:
    Jacob,
    Just FYI, DataSource or ConnectionPool name can not
    contain spaces. Change the names and let me know if it helps.
    Regards,
    Slava Imeshev
    "jacob nikom" <[email protected]> wrote in message
    news:[email protected]...
    Hi Slava,
    Thank you for your message. I did assign target to
    my Connection Pool and Data Source. It is "myserver".
    Also, there is not any error messages form WebLogic
    shell except the ones which I place in my message.
    So far the misery remains unresolved.
    Regards,
    Jacob Nikom
    "Slava Imeshev" <[email protected]> wrote:
    Hi Jacob,
    Make sure you assigned targets to the connection pool and
    data
    source.
    Also
    check Weblogic shell console for errors.
    Regards,
    Slava Imeshev
    "jacob nikom" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I am running WebLogic 6.1 on Win2k and I have problem
    with
    Cloudscape database in Default Admin Server.
    === Start init method in myJDBCReadServlet.java ===
    Init Error: javax.naming.NameNotFoundException:
    Unable to resolve MyJDBCDataSource.
    Resolved: '' Unresolved:'MyJDBCDataSource' ; remainingname
    === Finish init method in myJDBCReadServlet.java ===
    1. I created simple table in the Cloudscape database using
    IJ
    utility
    and
    inserted
    some values:
    prompt>java -classpath %CLASSPATH%;..\lib\tools.jarCOM.cloudscape.tools.ij
    ij version 3.5 (c) 1997-2000 Informix Software, Inc.
    ij> CONNECT 'jdbc:cloudscape:demo;create=true';
    WARNING 01J01: Database 'demo' not created, connection
    made
    to
    existing
    database
    instead.
    ij> SHOW CONNECTIONS;
    CONNECTION0* - jdbc:cloudscape:demo;create=true
    * = current connection
    ij> CREATE TABLE employee(name CHAR(25), location
    CHAR(20),
    id
    INTEGER);
    0 rows inserted/updated/deleted
    2. I created Connection Pool and Data Source using Default
    Console
    The Connection Pool configuration is the following:
    Name : MyJDBC Connection Pool
    URL : jdbc:cloudscape:demo
    Driver Classname: COM.cloudscape.core.JDBCDriver
    Properties : user=none password=none server=none
    My Data Source configuration is the following:
    Name : MyJDBC Data Source
    JNDI Name: MyJDBCDataSource
    Pool Name: MyJDBC Connection Pool
    I added the following line to myserver startup script
    to
    point
    to the database location:
    -Dcloudscape.system.home=./samples/eval/cloudscape/data
    3. I wrote the servlet and here is the piece of themyJDBCReadServlet
    code which generated the exception:
    public void init()
    System.out.println("=== Start init method inmyJDBCReadServlet.java
    ===");
    try {
    ctx = new InitialContext();
    ds = (javax.sql.DataSource) ctx.lookup
    ("MyJDBCDataSource");
    } catch (Exception E) {
    System.out.println("Init Error: " + E);
    System.out.println("=== Finish init method inmyJDBCReadServlet.java
    ===");
    Why it cannot find the database using JNDI name?
    Any help will be greatly appreciated,
    Jacob Nikom

  • How create a jndi / datasource for MySQL?

    Hi. This is CarloSilva, from Brazil, again. This time for help to datasource. My application uses MySQL database and ADF components. Please, would can anybody tell me step to step how to create a jndi conection datasource?
    I need setup project for uses datasource, no jdbc connection. How to?
    I need setup web.xml. How?
    I need setup a datasource in JDeveloper for my application. How?
    Please, sorry this questions but I new in JDeveloper and need use it for learn.
    Thanks.

    A JDBC connection may be used as a JNDI resource.
    If the Connections-Navigator connection is DBConnection1, the corresponding datasource is jdbc/DBConnection1DS.
    1. Create a JSP page.
    2. In the web.xml of the JSP add
    <resource-ref>
    <res-ref-name>jdbc/DBConnection1DS</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    3. In the JSP page obtain a connection with the datasource.
    InitialContext initialContext = new InitialContext();
    javax.sql.DataSource ds = (javax.sql.DataSource)initialContext.lookup("java:comp/env/jdbc/DBConnection1DS");
    java.sql.Connection conn = ds.getConnection();

  • How can i create datasource on apache server for ADF application?

    Hi All,
    i my use case i have created simple adf application using ADF BC and want to deploy on Apache server 6.x.
    So my question is that  how can i create Data Source i have goggling and find  two different way to do this.
    1. write following line of code on apache server conf/Context.xml file.
    <Resource name="jdbc/TestDB" auth="Container"
                  type="javax.sql.DataSource"
                   driverClassName="oracle.jdbc.OracleDriver"
                  url="jdbc:oracle:thin:@localhost:dst"
                  username="jagrandb" password="jagrantest" maxActive="20" maxIdle="10"
                  maxWait="-1"/>
    but when i have used this way i got following exception.
    org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper cannot be cast to oracle.jdbc.OracleConnection
    check link-
    https://forums.oracle.com/thread/2564233
    2. write following line of code apache conf/Server.xml file
    <GlobalNamingResources>
        <!-- Editable user database that can also be used by
             UserDatabaseRealm to authenticate users
        -->
        <Resource name="UserDatabase" auth="Container"
                  type="org.apache.catalina.UserDatabase"
                  description="User database that can be updated and saved"
                  factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
                  pathname="conf/tomcat-users.xml" />
    <Resource name="jdbc/TestDB" auth="Container"
                  type="oracle.jdbc.pool.OracleDataSource"
                  description="User database that can be updated and saved"
                  driverClassName="oracle.jdbc.driver.OracleDriver"
                  factory="oracle.jdbc.pool.OracleDataSourceFactory"
                  url="jdbc:oracle:thin:@//172.31.43.207:1521:dst"
                  username="jagrandb" password="jagrantest" maxActive="20" maxIdle="10"
                  maxWait="-1"   />
      </GlobalNamingResources>
    and add this line in context.xml file inside <context> tag
    <ResourceLink global="jdbc/TestDB" name="jdbc/TestDB" type="oracle.jdbc.pool.OracleDataSource"/>
    but when i have run application i have got following error
    log-
    javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: "java.sql.SQLException: invalid arguments in call"
      at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(QueryTagSupport.java:298)
      at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(QueryTagSupport.java:181)
      at org.apache.jsp.test_jsp._jspx_meth_sql_005fquery_005f0(test_jsp.java:110)
      at org.apache.jsp.test_jsp._jspService(test_jsp.java:63)
      at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
      at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
      at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
      at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:857)
      at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:565)
      at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1509)
      at java.lang.Thread.run(Thread.java:662)
    Aug 2, 2013 5:17:21 PM org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: "java.sql.SQLException: invalid arguments in call"
      at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(QueryTagSupport.java:298)
      at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(QueryTagSupport.java:181)
      at org.apache.jsp.test_jsp._jspx_meth_sql_005fquery_005f0(test_jsp.java:110)
      at org.apache.jsp.test_jsp._jspService(test_jsp.java:63)
      at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
      at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
      at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
      at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:857)
      at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:565)
      at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1509)
      at java.lang.Thread.run(Thread.java:662)
    so what is the solution how to create datasource on apche server which suitable for adf application?
    when i test data source using  following code used 1. way as i mentioned above  its running fine bt not for second.
    <%@ taglib uri="http://java.sun.com/jsp/jstl/sql" prefix="sql" %>
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <sql:query var="rs" dataSource="jdbc/TestDB">
    select empname from pay_emphdr where empcd='JK1306'
    </sql:query>
    <html>
      <head>
        <title>DB Test</title>
      </head>
      <body>
      <h2>Results</h2>
    <c:forEach var="row" items="${rs.rows}">
        Foo ${row.empname}<br/>
    </c:forEach>
      </body>
    </html>
    please help me. it is very urgent.
    thanks in Advance
    Manish

    Hi Lindalnci
    i have already tried  this tutorial and in my post i have defined first way to do using this procedure.
    in that case i have got following exception as i have mentioned above
    org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper cannot be cast to oracle.jdbc.OracleConnection

Maybe you are looking for