Is it possible to put a servlet in a .jar file and be able to access it
via AJAX?
I have some support servlets that I want to share via a common library.
To this point Ive only been putting session beans in there. Its easy to
point to those using 'do something similar to a servlet such that I
So I built a sample request filter using TC 5.x under NetBeans. I didn't
realize that it was going to be so pervasive! It is part of a test
project and just outputs some debug info to show that its awake.
The original app was just a test to see if I could trap login
information from the JNDIRe
(tomcat 5.x)
Why are 'context.xml' and 'web.xml' bits stored in different files? What
is the difference in their scope?
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
Im working with a JNDI realm to control access to a site. I need to be
able to 'trap' a successful login to any one of the pages in the site so
that I can create a session bean with login information. Is it possible
to tie a filter or valve to the login process and get the information
*before*
Im running my app using a 'DataSourceRealm' (MySQL) wherein I have
encrypted the stored passwords using SHA. I added the 'digest="SHA"' to
the realm definition.
The logins were working when I didn't encrypt the passwords. Now that
they are encrypted I can't login anymore.
Does the MySQL 'SHA
I have a site that uses Tomcat's form based authentication. It reads
from a MySQL db using a 'DataSourceRealm' defined in the context.xml
file. All well and good.
What Im hoping to achieve is creation of a session bean with info about
the logged in account when a valid login is sent. Is there
Issue: Im running into problems with a tomcat based application that
uses the JNDI connection pooling mechanism that ships with tomcat. It
appears that my session bits are being kept 'alive' by any running
instances of firefox even after the browser running my app is closed.
Situation: I have
Hi. I have a series of tomcat based apps that all use a single .jar to
do some common admin tasks like sending mail and connecting to a DB. The
.jar file uses the Tomcat/JNDI connection pooling to save overhead
(supposedly).
In the other apps (that use the above .jar) I have both servlets and
