Re: Problem displaying accents in Tomcat

[Sergio G. Reus]

> Yes, your asumptsion is right. I had apache before hooked to Tomcat.
> Now the application is running with Tomcat 4.1.24 on its own.
> The OS is linux, SUSE distro.
> The character encoding it should be the default one I haven't specified 
> any. So it should be (iso-8859-1) ?
> 
> Thanks
> 
> Manuel
> 

I've always used apache + tomcat and needed to add this
to CATALINA_OPTS variable when executing tomcat so that it
can display characters with tilde properly:

CATALINA_OPTS="-Dfile.encoding=ISO8859_15"

I use ISO8859_15 both in tomcat and in my database because it also 
supports euro character.

Sergio.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Symbolic link doesn't work

[Sergio G . Reus]

Hello,

I've been working so far with Solaris 8 and Tomcat 4.0.4. I use only ROOT context
to deploy several servlets. As the servlets need to be in in a precise
directory in the system, I created a symbolic link from 
"$CATALINA_HOME/webapps/ROOT/WEB_INF/classes" to
the directory where the servlets reside and it works perfectly.
Well, now I'm trying Tomcat 4.1.9 and the servlet classes are not found:

2002-08-28 12:43:20 StandardWrapper[/general:org.apache.catalina.INVOKER.Hello]:
Marking servlet org.apache.catalina.INVOKER.Hello as unavailable

javax.servlet.ServletException: Wrapper cannot find servlet class Hello or a class it 
depends on

- Root Cause -
java.lang.ClassNotFoundException: Hello


If I delete symbolic link "classes", create the directory phisically and
copy directly the servlets, it works perfectly. So, Is tomcat 4.1.x no longer 
supporting symbolic linking classes directory? Why?

Thanks in advance.
___

Sergio García Reus
Sistemas  de Información y Comunicaciones
Fundación Integra. http://www.f-integra.org

Teléfono: +34 968 355161
Fax:  +34 968 355131
Correo:   [EMAIL PROTECTED]
___

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Strange servlet behaviour with tomcat 4

[Sergio G . Reus]

Hi,

We have several web sites based on servlets working with 
apache 1.3.23 + mod_ssl + tomcat 3.3 + mod_jk. We use an authentication
servlet to validate our users into the private part of the sites. We only 
use SSL to encapsulate the authentication servlet transactions.
Now we are trying tomcat 4 (with the same apache, mod_ssl & mod_jk version),
but the first call to the authentication servlet does not receive any
parameters. The second call receives the parameters correctly though. After
closing the browser and opening it again, the anomaly repeats. When we disable 
SSL in the calls to the servlet the problem disappears.
Despite debugging the code and inspecting tomcat/apache logs we have not 
detected the cause. Since the only thing that has changed in the scenario is 
tomcat (we have tried tomcat 4.0.3 and tomcat 4.0.4-beta3), could it be a problem 
in apache/ssl/tomcat4 interaction? a problem with http sessions?

Thanks in advance,

Sergio

--
To unsubscribe, e-mail:   
For additional commands, e-mail: