DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27479>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27479 Deployed webapp contexts don't get properties ( child elements ) from DefaultContext Summary: Deployed webapp contexts don't get properties ( child elements ) from DefaultContext Product: Tomcat 5 Version: 5.0.19 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Given a a DefaultContext declaration in server.xml as follows : <DefaultContext debug="1000" crossContext="true"> <Resource name="jdbc/clubmom" auth="Container" type="oracle.jdbc.pool.OracleConnectionCacheImpl"/> <ResourceParams name="jdbc/clubmom"> <parameter><name>factory</name><value>oracle.jdbc.pool.OracleDataSourceFactory</value></parameter> <parameter><name>driverClassName</name><value>oracle.jdbc.OracleDriver</value></parameter> <parameter><name>url</name><value>jdbc:oracle:thin:@oracle-dev:1521:CM_DEV</value></parameter> <parameter><name>user</name><value>clubmom</value></parameter> <parameter><name>password</name><value>clubmom</value></parameter> <parameter><name>maxLimit</name><value>10</value></parameter> <parameter><name>stmtCacheSize</name><value>50</value></parameter> <parameter><name>implicitCachingEnabled</name><value>true</value></parameter> </ResourceParams> </DefaultContext> any deployed application ( via the manager app, dropped into webapps, or using ant tasks ) has no access to the given resource name. It seems none of the relevant properties from the DefaultContext are copied over. The problem seems to be that in StandardHostDeployer.install() the only properties that are set are the path and the docBase. I figure more properties, such as naming resources should be copied over also.. i.e. context.setNamingResources( host.getDefaultContext().getNamingResources() ) or some variation of ... A locally patched version adding that one line definitely gets rid of the common issu of the DBCP data source cannot load driver null for resource null that everyone gets.. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
