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=22527>. 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=22527 [excalibur-datasource] Lookup of jndi datasource in Weblogic 7.0 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2003-10-01 12:48 ------- In the version of the DataSourceComponent you have, we addressed this issue by providing better access to JNDI through different configuration paramters. The old <dbname> parameter uses the fully J2EE compliant lookup name. We realized that this component would not always be used in J2EE environments, and it seems that WebLogic allows you to violate the J2EE spec in this regard as well. So change your configuration like this: <j2ee name="foo"> <initial-context-factory>fully.qualified.class.Name</initial-context-factory> <provider-url>http://weblogicserver.company.com:123/</provider-url> <lookup-name>java:abnormal-lookup</lookup-name> </j2ee> Please note, the first two configuration elements (initial-context-factory and provider-url) are only necessary if you are not already running in a J2EE environment. If you need to set these, consult your vendor's documentation for the proper settings. The main difference above is that <dbname> prepends the java:comp/env/jdbc/ section, and <lookup-name> allows you to put in the full name. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
