tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16316] - DataSourceRealm can not find JNDI name in context
Date Mon, 03 Feb 2003 15:27:46 GMT
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=16316>.
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=16316

DataSourceRealm can not find JNDI name in context

3ca28f66@mail.ru changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From 3ca28f66@mail.ru  2003-02-03 15:27 -------
Sad but true, I've forced to reopen this bug. I tried all the possible variants
in configuration files (config.xml , web.xml) with no luck.
I have a servlet that looks up JNDI for DataSource object, and a DataSourceRealm
relied on JNDI resource defined in config.xml . With one configuration,
DataSource obtains successfully, but Realm doesn't work, throwing an exception;
with another, DataSource throwing an exception, but database access works fine.
How can I have it work both siumltaneuosly? Seems like nobody uses this
technique for now because I asked similar questions several time in tomcat-dev
list, and nobody helped to make it work both, but separately only.
Exception is the same:

javax.naming.NameNotFoundException: Name java:comp is not bound in this Context

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message