I think that all the others problems I had were related to this
configuration.
Anyway, I had an issue with data saved in the application scope which
after the user switched from http to https was not anymore available,
and now I understand why.
If you don't mind I'd like to ask a couple of que
--- Alessandro Ilardo
<[EMAIL PROTECTED]> wrote:
> back to my problem: I discovered that the kindly
> network administrator
> had configured two tomcat instances, one working
> with apache connector
> for the normal http request and the other on a
> different port for the
> ssl. Both instances g
Your suggestion is appreciated, all my webapp implement the driver
you've suggested, but regarding the Realm configuration I preferred
follow the tomcat docs which says: "The fully qualified Java class name
of this Realm implementation. You *MUST* specify the value
"|org.apache.catalina.realm.J
On the outset, looks good to me. Can you confirm the location of your
new class files are where they belong inside of WEB-INF/classes of the
webapp? Are there any logging messages that might suggest tomcat isn't
reading classes from the expected location?
This comment has nothing to do with
Hi there,
on a remote tomcat 5.5 webserver we uploaded new .class files, we
reloaded at least three times trough the manager but anytime we test it,
looks like the old files are still running.
The META-INF folder contain the following context.xml configuration file:
debug="0" reloadable="true">
