JasperException with tomcat

Hi people,

I have already put the jdbc driver for oracle in the tomcat/common/lib,

I added jstl.jar and standard.jar as libraries to my project too.

I exported to war file...

So, Simple applications that don磘 uses data base are running ok, but the application that use DB is receive this message...

HTTP Status 500 -

- -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

com.sun.rave.web.ui.appbase.ApplicationException: org.apache.jasper.JasperException

com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.destroy(ViewHandlerImpl.java: 601)

com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.ja va:316)

com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87 )

com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)

com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)

javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)

com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)

note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.

- -

Apache Tomcat/5.5.17

And I configured my context as the example bellow...

So what磗 my problem?! What I have to do!?

H:\Tomcat 5.5\conf\contex.xml

<?xml version="1.0" encoding="UTF-8"?>

<!-- The contents of this file will be loaded for each web application -->

<Context>

<Resource

auth="Container"

description="DB Connection"

name="jdbc/Helpdesk"

type="javax.sql.DataSource"

password="password"

driverClassName="oracle.jdbc.driver.OracleDriver"

maxIdle="50"

maxWait="5000"

validationQuery=""

username="Helpdesk"

url="jdbc:oracle:thin:hcdes@10.10.0.4:1521:hcdes"

maxActive="250"/>

<WatchedResource>WEB-INF/web.xml</WatchedResource>

<!-- Uncomment this to disable session persistence across Tomcat restarts -->

<!--

<Manager pathname="" />

-->

</Context>

[2269 byte] By [Callou] at [2007-11-26 8:42:55]
# 1
Actually, that stack trace does not show the root cause. If you could go into your server log and repost the root exception, it would help.
mbohm at 2007-7-6 22:23:06 > top of Java-index,Development Tools,Java Tools...