Re: PATCH - jk_workerEnv.c - Use jk_global.h defines

2004-05-25 Thread jean-frederic clere 
NormW wrote:
Greetings All.
The following link is to a patch which changes two string constants in
jk_workerEnv.c to use an existing #define in jk_global.h. A copy of the
patch is added at the end. The patch has been successfuly applied and
compiled on a NetWare platform.
Committed thanks.
Jean-Frederic
http://normw.gknw.com/patches/jk_workerEnv.c.diff
Norm
-
 jk_workerEnv.c.orig 2004-03-22 07:46:03.0 +1100
+++ jk_workerEnv.c 2004-04-19 11:09:46.0 +1000
@@ -293,7 +293,7 @@
 if (configFile == NULL) {
 wEnv->config->setPropertyString(env, wEnv->config,
 "config.file",
-
"${serverRoot}/conf/workers2.properties");
+JK_WORKER_FILE_DEF);
 configFile = wEnv->config->file;
 }
@@ -334,7 +334,7 @@
 if (configFile == NULL) {
 wEnv->config->setPropertyString(env, wEnv->config,
 "config.file",
-
"${serverRoot}/conf/workers2.properties");
+JK_WORKER_FILE_DEF);
 configFile = wEnv->config->file;
 }
 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


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

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_workerEnv.c

2004-05-25 Thread jfclere 
jfclere 2004/05/25 23:50:19

  Modified:jk/native2/common jk_workerEnv.c
  Log:
  Use existing DEFINE (in jk_global.h).
  Submitted by Norm (normw at bocnet.com.au) (http://normw.gknw.com)
  
  Revision  ChangesPath
  1.68  +3 -3  jakarta-tomcat-connectors/jk/native2/common/jk_workerEnv.c
  
  Index: jk_workerEnv.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_workerEnv.c,v
  retrieving revision 1.67
  retrieving revision 1.68
  diff -u -r1.67 -r1.68
  --- jk_workerEnv.c21 Mar 2004 09:43:09 -  1.67
  +++ jk_workerEnv.c26 May 2004 06:50:19 -  1.68
  @@ -293,7 +293,7 @@
   if (configFile == NULL) {
   wEnv->config->setPropertyString(env, wEnv->config,
   "config.file",
  -"${serverRoot}/conf/workers2.properties");
  +JK_WORKER_FILE_DEF);
   configFile = wEnv->config->file;
   }
   
  @@ -334,7 +334,7 @@
   if (configFile == NULL) {
   wEnv->config->setPropertyString(env, wEnv->config,
   "config.file",
  -"${serverRoot}/conf/workers2.properties");
  +JK_WORKER_FILE_DEF);
   configFile = wEnv->config->file;
   }
   
  
  
  

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

DO NOT REPLY [Bug 29220] New: - Connection pool exhausted

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29220

Connection pool exhausted

   Summary: Connection pool exhausted
   Product: Tomcat 4
   Version: 4.1.24
  Platform: Other
OS/Version: Windows NT/2K
Status: NEW
  Severity: Major
  Priority: Other
 Component: Connector:Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


My server.xml is given below

 

  factory
  org.apache.commons.dbcp.BasicDataSourceFactory


  driverClassName
  oracle.jdbc.driver.OracleDriver


  url
  jdbc:oracle:thin:@192.9.200.4:1521:orcl


  username
  notisappuser


  password
  nihmcbiegllgnafk


  maxActive
  30


   maxIdle
   3


  maxWait
  1



There is a appropriate entry in web.xml too


 Oracle Datasource example
 jdbc/bbksms
 javax.sql.DataSource
 Container


i am using oracle 9i as my database.
during login, i used to get 
org.apache.commons.dbcp.SQLNestedException: Cannot create 
PoolableConnectionFactory, cause: Io exception:
connection pool exhausted.

what may be the reason

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

DO NOT REPLY [Bug 27958] - WAR files not autodeployed when changed

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27958

WAR files not autodeployed when changed





--- Additional Comments From [EMAIL PROTECTED]  2004-05-26 04:26 ---
Hello,

a reload from a war works fine for me at 5.0.24/25 release.

Your must deploy your web application at appBase from your host.
The Deployer (HostConfig class) detect than the changed war file, delete the
extracted directory and context.xml. Than the newer war Archiv was loaded
and extract your META-INF/context.xml and the directory.

It also work when you context.xml docPath point to the extacted directory, but
this is not clever. Thing about Tomcat server that configured with
Host.unpackWARS=false! 
The complete deployment work also for ROOT.war.

I tested this and it works stable.

Regards
Peter

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

respuestas sobre el Chat

2004-05-25 Thread ayudachat 


Algunas preguntas frecuentes sobre inconvenientes al ingresar al chat son:



Si puede ingresar su Nick en el recuadro de texto pero no inicia la sesión de chat 
pueder ser por que dicho Nick se encuentre registrado por otra persona en tal caso 
pruebe cambiarlo o agregarle algún numero.

También puede ser que su ip se encuentre prohibida por el moderador en este caso hay 
que esperar algunas horas hasta que se libere, observe el recuadro blanco de reportes 
cada vez que intenta ingresar para saber cual es el caso. Si sólo lee un mensaje de 
"error" puede ser necesario reiniciar su computadora.



FALTA DE MAQUINA VIRTUAL DE JAVA

Para Windows XP, WinNT, WinME, Win98

Si por alguna razón su navegador le avisa que NO tiene instalada la compatibilidad con 
JAVA, la mejor alternativa es bajar la Maquina virtual de Java desde el sitio oficial 
de Sun

http://www.java.com/en/index.jsp  En esta página clickeando en "Download Java 
Software", automaticamentte le va a detectar e instalar la version necesaria para su 
PC.

 

Luego de un par de minutos que se complete el proceso ya lo puede probar

www.paysandu.com/chat



OTRAS RAZONES POSIBLES

Cuando aparece un recuadro gris en la pantalla y luego de varios segundos no aparece 
el acceso al Chat. Las razones pueden ser las siguientes, que en ese momento la 
conexión esté muy lenta y demora más de lo habitual; si es este el caso y esperando no 
se soluciona puede desconectarse/conectarse de Internet para volver a intentarlo. 

Si no se soluciona o nota que esto es frecuente, entonces puede ser que tenga muchos 
archivos temporales en el cache de su maquina.



Como Limpiar la memoria caché?

Si el caché está lleno, las páginas nuevas se abrirán muy lentamente o no se abrirán. 
Es posible que la memoria caché esté llena de páginas desfasadas o inútiles; por ello 
es buena idea limpiarla de vez en cuando. A continuación explicamos cómo limpiar la 
memoria caché dependiendo del navegador que tenga:



*

LIMPIAR CACHE EN INTERNET EXPLORER, instrucciones:



Haga clic en "Herramientas" (Tools) en la parte superior de la ventana de su navegador 
y luego seleccione "Opciones de Internet" (Internet Options).



Cuando emerja la ventana, haga clic en el cuadro "eliminar archivos" (delete files).



Marque la opción "eliminar contenido fuera de línea" (delete offline content) y haga 
clic en "Aceptar" (OK).



Haga también clic en el botón "limpiar historial" (clear history).



Haga clic en "Aceptar" (OK) hasta salir del cuadro de preferencias. 

Después de haber vaciado el caché, y estando conectado a Internet vaya a 
www.paysandu.com/chat.html oprima las teclas Ctrl y Shift y pulse el botón 
"Actualizar" (refresh) o (Reload) en su navegador a la misma vez luego de algunos 
segundos deberá aparecer el recuadro del nombre y boton login de acceso al Chat





LIMPIAR CACHE EN NETSCAPE, instrucciones:



Haga clic en "edición" (edit) en la parte superior de la ventana de su navegador y a 
continuación en "preferencias" (preferences).



Cuando emerja la ventana, haga clic en las opciones "limpiar historial" (clear 
history) y en "limpiar barra de localización" (clear location bar).



A continuación haga clic en el signo + que se encuentra junto a la opción "avanzado" 
(advanced).



Seleccione la opción "caché".



Haga clic en las opciones "limpiar memoria caché" (clear memory cache) y en "limpiar 
disco caché" (clear disk cache).



Haga clic en "Aceptar" (OK) hasta salir de la ventana.





LIMPIAR CACHE EN AOL, siga los siguientes pasos:



Busque "preferencias" (preferences) en el menú "mi aol" (my aol).



Luego haga clic en "www".



Haga clic en el botón "eliminar archivos" (delete files). Aparecerá una ventana 
preguntándole si desea borrar los archivos temporales de Internet.



Marque el cuadro de la opción "eliminar contenido fuera de línea" (delete offline 
content) y haga clic en el botón Aceptar (OK).



A continuación haga clic en el botón "eliminar historial" (delete history).



Haga clic en "Aceptar" (OK) hasta que salga del menú de preferencias.

Después de haber vaciado el caché, vaya a www.paysandu.com/chat.html y pulse el botón 
"Actualizar" (refresh) o "Volver a cargar" (Reload) en su navegador



**

Si usted es usuario de WebTv no podrá acceder al Chat, esta es una limitacion del 
proveedor de este tipo de servicio que no admite Java. Tampoco se pueden conectar en 
una red interna a través de un Fire Wall sin que el administrador del mismo lo 
autorice previamente.



En este chat al igual que en el foro de encuentros, los enlaces entre usuarios y o 
canales se producen 100% en la web de www.paysandu.com es decir no exiten accesos a 
través de servidores IRC u de otro tipo.



  





COMANDOS DE USO EN EL CHAT DE ENCUENTROS SANDUCEROS



Los siguientes comandos se pueden ejecutar en la línea de diálogo seguidos del 
caractér / 



algunos de ellos se han simpli

[GUMP@brutus]: jakarta-tomcat-4.0/tomcat-catalina success

2004-05-25 Thread Stefan Bodewig 
To whom it may satisfy...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project tomcat-catalina *no longer* has an issue.
Project State : 'Success'

Full details are available at:

http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Sole jar [catalina.jar] identifier set to project name
 -INFO- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet.jar.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging-api.jar.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.jar.
 -INFO- Enable "verbose" output, due to 2 previous error(s).
 -INFO- No license on redistributable project with outputs.


The following work was performed:
http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/gump_work/build_jakarta-tomcat-4.0_tomcat-catalina.html
Work Name: build_jakarta-tomcat-4.0_tomcat-catalina (Type: Build)
State: Success
Elapsed: 0 hours, 0 minutes, 9 seconds
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
 org.apache.tools.ant.Main -verbose 
-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-beanutils.jar=/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar
 -Djtc.home=/usr/local/gump/public/workspace/jakarta-tomcat-connectors 
-Dversion=4.1.25-dev 
-Dregexp.jar=/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040525.jar
 
-Dcommons-logging-api.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar
 -Dservlet.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar 
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar
 
-Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040525.jar
 
-Dcommons-digester.jar=/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar
 deploy-catalina 
[Working Directory: /usr/local/gump/public/workspace/jakarta-tomcat-4.0/catalina]
CLASSPATH : 
/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040525.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/fileupload/target/commons-fileupload-20040525.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040525.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar-
  [jar] adding directory org/apache/catalina/ssi/
  [jar] adding entry org/apache/catalina/ssi/ByteArrayServletOutputStream.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$1.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$AndNode.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$CompareNode.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$EqualNode.class
  [jar] adding entry 
org/apache/catalina/ssi/ExpressionParseTree$GreaterThanNode.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$LessThanNode.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$Node.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$NotNode.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$OppNode.class
  [jar] adding entry org/apache/catalina/ssi/ExpressionParseTree$OrNode.class
  [jar] adding entry org/apache/catalina/ssi

[GUMP@brutus]: jakarta-tomcat-catalina/jakarta-tomcat-catalina failed

2004-05-25 Thread bobh 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project jakarta-tomcat-catalina has an issue affecting its community integration.
This issue affects 2 projects.
Project State : 'Failed', Reason 'Build Failed'
The following are affected:
- jakarta-tomcat-5 :  Servlet 2.4 and JSP 2.0 Reference Implementation
- jakarta-tomcat-jk :  Connectors to various web servers


Full details are available at:


http://brutus.apache.org:8080/gump/jakarta-tomcat-catalina/jakarta-tomcat-catalina/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Jar [naming-resources.jar] identifier set to jar basename: [naming-resources]
 -INFO- Jar [servlets-default.jar] identifier set to jar basename: [servlets-default]
 -INFO- Jar [naming-common.jar] identifier set to jar basename: [naming-common]
 -INFO- Jar [catalina.jar] identifier set to jar basename: [catalina]
 -INFO- Jar [bootstrap.jar] identifier set to jar basename: [bootstrap]
 -INFO- Jar [servlets-common.jar] identifier set to jar basename: [servlets-common]
 -INFO- Jar [servlets-invoker.jar] identifier set to jar basename: [servlets-invoker]
 -ERROR- No such project [commons-beanutils] for property
 -ERROR- Cannot resolve jar/jarpath of *unknown* [commons-beanutils]
 -INFO- Dependency on javamail exists, no need to add for property mail.jar.
 -INFO- Dependency on jaf exists, no need to add for property activation.jar.
 -INFO- Dependency on jmx exists, no need to add for property jmx.jar.
 -INFO- Dependency on jakarta-servletapi-5-servlet exists, no need to add for property 
servlet-api.jar.
 -INFO- Dependency on jakarta-servletapi-5-jsp exists, no need to add for property 
jsp-api.jar.
 -INFO- Dependency on xml-xerces exists, no need to add for property xercesImpl.jar.
 -INFO- Dependency on xml-xerces exists, no need to add for property xmlParserAPIs.jar.
 -INFO- Dependency on jakarta-tomcat-util exists, no need to add for property 
tomcat-util.jar.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging-api.jar.
 -INFO- Dependency on ant exists, no need to add for property ant.home.
 -INFO- Dependency on jsse exists, no need to add for property jsse.home.
 -INFO- Dependency on jmx exists, no need to add for property jmx.home.
 -INFO- Dependency on jmx exists, no need to add for property jmxtools.jar.
 -INFO- Dependency on jndi exists, no need to add for property jndi.home.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.home.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.jar.
 -INFO- Dependency on javamail exists, no need to add for property mail.home.
 -INFO- Dependency on jaf exists, no need to add for property activation.home.
 -INFO- Dependency on jakarta-tomcat-coyote exists, no need to add for property 
tomcat-coyote.home.
 -INFO- Enable "verbose" output, due to 4 previous error(s).
 -INFO- Failed with reason build failed
 -INFO- Enable "debug" output, due to build failure.


The following work was performed:
http://brutus.apache.org:8080/gump/jakarta-tomcat-catalina/jakarta-tomcat-catalina/gump_work/build_jakarta-tomcat-catalina_jakarta-tomcat-catalina.html
Work Name: build_jakarta-tomcat-catalina_jakarta-tomcat-catalina (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 2 seconds
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -verbose 
-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dtomcat33.home=*Unset* 
-Djsp-api.jar=/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar
 -Djmx.jar=/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar 
-Djmx.home=/usr/local/gump/packages/jmx-1_2-ri 
-Djdbc20ext.jar=/usr/local/gump/packages/jdbc2_0/jdbc2_0-stdext.jar 
-Djtc.home=/usr/local/gump/public/workspace/jakarta-tomcat-connectors 
-Dmail.home=/usr/local/gump/packages/javamail-1.3 
-Dant.home=/usr/local/gump/public/workspace/ant/dist 
-Dsite2.home=/usr/local/gump/public/workspace/jakarta-site2 
-Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040525.jar
 -Dcatalina.deploy=/usr/local/gump/public/workspace/jakarta-tomcat-catalina/build 
-Dldap.jar=/usr/local/gump/packages/ldap-1_2_4/lib/ldap.jar 
-DxercesImpl.jar=/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar
 -Djsse.home=/usr/local/gump/packages/jsse1.0.3 
-Djaas.jar=/usr/local/gump/packages/jaa

PATCH - \jk\native2\common\jk_worker_ajp13.c - get/set updates

2004-05-25 Thread NormW 
Greetings All,
The link below is an updated diff to the above referenced file, and which
does thefollowing:

- adds 'debug' into setAttribute() (it was already listed in
setAttributeInfo[]),
- adds 'max_connections' to 'setAttributeInfo[]' (it was already in
setAttribute()),
- adds 'max_connections' to 'getAttributeInfo[]',
- adds 'max_connections' to 'getAttribute()',
- re-orders getAttributeInfo[] to a more logical sequence for status worker
display:
  : balance related items are grouped,
  : route items are grouped,
  : connections items are grouped,
  : 'debug' and 'disabled' at the end of the list (to be in a standard
location).

http://normw.gknw.com/patches/jk_worker_ajp13.c.diff2

The code presentation changes have generally be removed from this to ease
analysis of changes...(the original diff remains available).

The resulting jk_worker_ajp13.c has been successfully compiled and tested to
display correctly in status worker pages on a NetWare platform.
Norm.
-
--- jk_worker_ajp13.c.orig 2004-03-22 07:46:09.0 +1100
+++ jk_worker_ajp13.c 2004-05-26 09:43:59.0 +1000
@@ -35,23 +35,26 @@
 #include "jk_registry.h"

 /*  Impl  */
-static char *jk2_worker_ajp13_getAttributeInfo[] =
-{ "lb_factor", "lb_value", "debug", "channel", "level",
-"route", "routeRedirect", "errorState", "graceful", "groups",
"disabled",
-"epCount", "errorTime", "connectTimeout", "replyTimeout",
-"prepostTimeout", NULL
+/*
+ * Properties available to Get.
+ */
+static char *jk2_worker_ajp13_getAttributeInfo[] = {
+"channel", "groups", "max_connections", "epCount", "level",
"lb_factor",
+"lb_value", "route", "routeRedirect","graceful", "errorState",
"errorTime",
+"connectTimeout", "replyTimeout", "prepostTimeout", "debug",
"disabled", NULL
 };

 static char *jk2_worker_ajp13_multiValueInfo[] = { "group", NULL };

-static char *jk2_worker_ajp13_setAttributeInfo[] =
-{ "debug", "channel", "route", "routeRedirect", "secretkey", "group",
-"graceful",
-"disabled", "lb_factor", "level", "connectTimeout", "replyTimeout",
-"prepostTimeout", NULL
+/*
+ * Properties available to Set.
+ */
+static char *jk2_worker_ajp13_setAttributeInfo[] = {
+"channel", "group", "secretkey", "max_connections", "level",
"lb_factor",
+"route", "routeRedirect", "graceful", "connectTimeout", "replyTimeout",
+"prepostTimeout", "debug", "disabled", NULL
 };

-
 static void *JK_METHOD jk2_worker_ajp13_getAttribute(jk_env_t *env,
  jk_bean_t *bean,
  char *name)
@@ -76,6 +79,9 @@
 else if (strcmp(name, "groups") == 0) {
 return jk2_map_concatKeys(env, worker->groups, ":");
 }
+else if (strcmp(name, "max_connections") == 0) {
+return jk2_env_itoa(env, worker->maxEndpoints);
+}
 else if (strcmp(name, "level") == 0) {
 return jk2_env_itoa(env, worker->level);
 }
@@ -116,9 +122,8 @@
 }
 }

-
 /*
- * Initialize the worker
+ * Set worker properties.
  */
 static int JK_METHOD
 jk2_worker_ajp13_setAttribute(jk_env_t *env, jk_bean_t *mbean,
@@ -169,6 +174,9 @@
 else if (strcmp(name, "max_connections") == 0) {
 ajp13->maxEndpoints = atoi(value);
 }
+ else if (strcmp(name, "debug") == 0) {
+mbean->debug = atoi(value);
+}
 else {
 return JK_ERR;
 }
-


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

DO NOT REPLY [Bug 27958] - WAR files not autodeployed when changed

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27958

WAR files not autodeployed when changed





--- Additional Comments From [EMAIL PROTECTED]  2004-05-26 00:23 ---
Remy, is this a bug or a feature because the docs say this about deployment:

"Redeployment of a web application which has been deployed from a WAR when the
WAR is updated: the expanded web application is removed, and the WAR is expanded
again. This will not happen if the host is configured so that WARs are not
expanded, in which case the webapp will be simply redeployed."

(From http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html)

If I read above statement correctly it means changing a WAR file should result
in its expanded directory being removed from webapps and recreated in webapps.

Am I missing something?

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

DO NOT REPLY [Bug 29214] New: - response containsHeader("Content-Type") not working

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29214

response containsHeader("Content-Type") not working

   Summary: response containsHeader("Content-Type") not working
   Product: Tomcat 4
   Version: 4.1.24
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Servlet & JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


response.containsHeader("Content-Type") always returns false even if the header
is explicitly added via response.setHeader("Content-Type", "text/html").

To reproduce, simply add the following to a filter or servlet:

response.setHeader("Content-Type", "text/html");
System.out.println(response.containsHeader("Content-Type"));

The difficult question (for which the Servlet spec is silent) will be what to
return for response.containsHeader("Content-Type") if the header was set using
the response.setContentType() method.  I think the spec is pretty clear that if
setHeader is used, containsHeader should work for any header.

Thanks... Sean

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

HSBC BANK A.S.

2004-05-25 Thread Information 


Degerli Musterimiz,

Bu E-Posta adresine gonderilen mesajlar Bankamiz ilgili birimlerine
ulasmamaktadir. Bu nedenle, tum memnuniyet, oneri ve sikayetlerinizi en
kisa surede cevaplayabilmemiz icin asagıdaki kanallardan birini tercih
ederek iletmenizi rica ederiz.

Saygilarimizla
HSBC Bank A.S.

E-Posta:
www.hsbc.com.tr HSBC Bank Web Sitesi "Bize Ulasın" sayfasi veya HSBC
Internet Bankaciligi hizmeti "E-Posta" sayfasi

Telefon:
HSBC Bank Musteri Memnuniyeti Hatti 444 0 114

Mektup&Faks:
HSBC Bireysel Direkt Bankacilik-Müsteri İletisim Birimi
Adres: HSBC Bank A.S, Ayazaga Mah. Ahi Evran Cad. Dereboyu Sok.
Maslak 34398 - İSTANBUL
Faks: +90 (212) 336 26 37






Dear Sir/Madam,

Messages that are sent to this e-mail address do not reach the relevant
department. Therefore, we kindly ask you to forward your satisfactions,
suggestions and complaints from one of the following channels in order
for us to respond promptly.

Best Regards
HSBC Bank A.S.


E-Mail:
The "Contact Us" page at www.hsbc.com.tr HSBC Bank Web site or "E-Mail"
page at HSBC Retail Internet Banking

Telephone:
HSBC Bank Customer Satisfaction Line +90 (212) 444 0 114

Letter & Fax:
HSBC Retail Direct Banking-Customer Communication Unit
Address: HSBC Bank A.S, Ayazaga Mah. Ahi Evran Cad. Dereboyu Sok.
Maslak 34398 - ISTANBUL
Fax: +90 (212) 336 26 37



Bu E-posta mesajı gizlidir. Ayrıca hukuken de gizli olabilir.
Mesajın gönderilmek istendiği kişi siz değilseniz hiçbir kısmını
kopyalayamaz, başkasına gönderemez, başkasına açıklayamaz veya
kullanamazsınız. Eğer bu mesaj size yanlışlıkla ulaşmışsa, lütfen
mesajı ve tüm kopyalarını sisteminizden silin ve gönderen kişiyi
E-posta yolu ile bilgilendirin.

İnternet iletişiminde zamanında, güvenli, hatasız ya da virüssüz
gönderim garanti edilemez.
Gönderen taraf hata veya unutmalardan sorumluluk kabul etmez.

This E-mail is confidential. It may also be legally privileged. If
you are not the addressee you may not copy, forward, disclose or use
any part of it. If you have received this message in error, please
delete it and all copies from your system and notify the sender
immediately by return E-mail.

Internet communications cannot be guaranteed to be timely, secure,
error or virus-free.
The sender does not accept liability for any errors or omissions.




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

cvs commit: jakarta-tomcat-connectors/jk/native/common jk_connect.h

2004-05-25 Thread mmanders 
mmanders2004/05/25 15:32:55

  Modified:jk/native/common jk_connect.h
  Log:
  Fixed define if building for NetWare and using LIBC (i.e. Apache2).
  
  Revision  ChangesPath
  1.8   +2 -2  jakarta-tomcat-connectors/jk/native/common/jk_connect.h
  
  Index: jk_connect.h
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_connect.h,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- jk_connect.h  1 Mar 2004 13:37:38 -   1.7
  +++ jk_connect.h  25 May 2004 22:32:55 -  1.8
  @@ -26,7 +26,7 @@
   #include "jk_logger.h"
   #include "jk_global.h"
   
  -#ifndef WIN32
  +#if !defined(WIN32) && !(defined(NETWARE) && defined(__NOVELL_LIBC__))
   #define closesocket close
   #endif
   
  
  
  

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

DO NOT REPLY [Bug 29160] - precompile problem: _jspx_meth_* (javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) cannot be applied to (org.apache.struts.taglib.*.*Tag,javax.servlet.jsp.PageContext)

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29160

precompile problem: _jspx_meth_* 
(javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) cannot be applied to 
(org.apache.struts.taglib.*.*Tag,javax.servlet.jsp.PageContext)





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 22:16 ---
Can you attach your original webapp WAR file that contains the JSP pages and
bundles the struts taglib?

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

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources messages.properties messages_es.properties messages_fr.properties messages_ja.properties

2004-05-25 Thread luehe 
luehe   2004/05/25 14:28:40

  Modified:jasper2/src/share/org/apache/jasper/resources
messages.properties messages_es.properties
messages_fr.properties messages_ja.properties
  Log:
  Include javac errors whose line numbers cannot be mapped to JSP page in error 
message that is returned to client.
  
  For instance, a missing closing brace in a scriptlet causes havoc with the 
try-catch-finally block that that JSP compiler puts around all generated code, and the 
resulting javac error line numbers fall outside the scope of the begin and end java 
line numbers of the scriptlet (and therefore cannot be mapped back to the JSP line 
number of the scriptlet).
  
  (This used to return the misleading error message about failure to find javac 
compiler.)
  
  Revision  ChangesPath
  1.146 +2 -2  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties
  
  Index: messages.properties
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties,v
  retrieving revision 1.145
  retrieving revision 1.146
  diff -u -r1.145 -r1.146
  --- messages.properties   21 May 2004 00:22:06 -  1.145
  +++ messages.properties   25 May 2004 21:28:40 -  1.146
  @@ -291,7 +291,7 @@
   jsp.error.invalid.javaEncoding=Invalid java encodings. Tried {0} and then {1}. Both 
failed.
   jsp.error.needAlternateJavaEncoding=Default java encoding {0} is invalid on your 
java platform. An alternate can be specified via the 'javaEncoding' parameter of 
JspServlet.
   #Error when compiling, used for jsp line number error messages
  -jsp.error.single.line.number=\n\nAn error occurred at line: {0} in the jsp file: 
{1}\n\n
  +jsp.error.single.line.number=An error occurred at line: {0} in the jsp file: {1}
   jsp.error.multiple.line.number=\n\nAn error occurred between lines: {0} and {1} in 
the jsp file: {2}\n\n
   jsp.error.corresponding.servlet=Generated servlet error:\n
   jsp.error.empty.body.not.allowed=Empty body not allowed for {0}
  
  
  
  1.50  +2 -2  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_es.properties
  
  Index: messages_es.properties
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_es.properties,v
  retrieving revision 1.49
  retrieving revision 1.50
  diff -u -r1.49 -r1.50
  --- messages_es.properties21 May 2004 00:22:06 -  1.49
  +++ messages_es.properties25 May 2004 21:28:40 -  1.50
  @@ -292,7 +292,7 @@
   jsp.error.invalid.javaEncoding=Codificaciones java incorrectas. Intenté {0} y luego 
{1}. Ambas fallaron.
   jsp.error.needAlternateJavaEncoding=La codificación java por defecto {0} es 
incorrecta en tu plataforma java. Se puede especificar una alternativa vía parámetro 
'javaEncoding' de JspServlet.
   #Error when compiling, used for jsp line number error messages
  -jsp.error.single.line.number=\n\nHa tenido lugar un error en la línea: {0} en el 
archivo jsp: {1}\n\n
  +jsp.error.single.line.number=Ha tenido lugar un error en la línea: {0} en el 
archivo jsp: {1}
   jsp.error.multiple.line.number=\n\nHa tenido lugar un error entre las líneas: {0} y 
{1} en el archivo jsp: {2}\n\n
   jsp.error.corresponding.servlet=Error de servlet generado:\n
   jsp.error.empty.body.not.allowed=Cuerpo vacío no permitido para {0}
  
  
  
  1.33  +2 -2  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_fr.properties
  
  Index: messages_fr.properties
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_fr.properties,v
  retrieving revision 1.32
  retrieving revision 1.33
  diff -u -r1.32 -r1.33
  --- messages_fr.properties10 Mar 2004 21:16:31 -  1.32
  +++ messages_fr.properties25 May 2004 21:28:40 -  1.33
  @@ -243,7 +243,7 @@
   jsp.error.invalid.javaEncoding=Encodage java incorrect. Essai de {0} puis de {1}. 
Les deux ont échoué.
   jsp.error.needAlternateJavaEncoding=L''encodage java par défaut {0} est incorrect 
sur votre environnement java. Une alternative peut être indiquée via le paramêtre 
'javaEncoding' de la JspServlet.
   #Erreur lors de la compilation, utilisé pour la ligne jsp des messages d''erreur
  -jsp.error.single.line.number=\n\nUne erreur s''est produite à la ligne: {0} dans le 
fichier jsp: {1}\n\n
  +jsp.error.single.line.number=Une erreur s''est produite à la ligne: {0} dans le 
fichier jsp: {1}
   jsp.error.multiple.line.number=\n\nUne erreur s''est produite entre les lignes: {0} 
et {1} dans le fichier jsp: {2}\n\n
   jsp.error.corresponding.servlet=Erreur de servlet générée:\n
   jsp.error.empty.body.not.allowed=Un co

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler DefaultErrorHandler.java ErrorDispatcher.java JavacErrorDetail.java

2004-05-25 Thread luehe 
luehe   2004/05/25 14:27:55

  Modified:jasper2/src/share/org/apache/jasper/compiler
DefaultErrorHandler.java ErrorDispatcher.java
JavacErrorDetail.java
  Log:
  Include javac errors whose line numbers cannot be mapped to JSP page in error 
message that is returned to client.
  
  For instance, a missing closing brace in a scriptlet causes havoc with the 
try-catch-finally block that that JSP compiler puts around all generated code, and the 
resulting javac error line numbers fall outside the scope of the begin and end java 
line numbers of the scriptlet (and therefore cannot be mapped back to the JSP line 
number of the scriptlet).
  
  (This used to return the misleading error message about failure to find javac 
compiler.)
  
  Revision  ChangesPath
  1.12  +12 -7 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/DefaultErrorHandler.java
  
  Index: DefaultErrorHandler.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/DefaultErrorHandler.java,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- DefaultErrorHandler.java  21 May 2004 17:52:59 -  1.11
  +++ DefaultErrorHandler.java  25 May 2004 21:27:55 -  1.12
  @@ -66,18 +66,23 @@
   StringBuffer buf = new StringBuffer();
   
   for (int i=0; i < details.length; i++) {
  -args = new Object[] {
  +if (details[i].getJspBeginLineNumber() >= 0) {
  +args = new Object[] {
   new Integer(details[i].getJspBeginLineNumber()), 
   details[i].getJspFileName() };
  -buf.append(Localizer.getMessage("jsp.error.single.line.number",
  -args));
  -buf.append(Localizer.getMessage("jsp.error.corresponding.servlet"));
  +buf.append(Localizer.getMessage("jsp.error.single.line.number",
  +args));
  +buf.append("\n"); 
  +}
  +
  +buf.append(
  +Localizer.getMessage("jsp.error.corresponding.servlet"));
   buf.append(details[i].getErrorMessage());
  -buf.append('\n');
  +buf.append("\n\n");
   }
   
  - throw new JasperException(Localizer.getMessage("jsp.error.unable.compile")
  -   + buf);
  + throw new JasperException(
  +Localizer.getMessage("jsp.error.unable.compile") + "\n\n" + buf);
   }
   
   /**
  
  
  
  1.20  +44 -25
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ErrorDispatcher.java
  
  Index: ErrorDispatcher.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ErrorDispatcher.java,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- ErrorDispatcher.java  21 May 2004 17:52:59 -  1.19
  +++ ErrorDispatcher.java  25 May 2004 21:27:55 -  1.20
  @@ -431,9 +431,9 @@
throws IOException, JasperException {
   
Vector errVec = new Vector();
  - StringBuffer partialErrMsg = new StringBuffer();
  + StringBuffer errMsgBuf = null;
int lineNum = -1;
  - Node errNode = null;
  +JavacErrorDetail javacError = null;
   
   BufferedReader reader = new BufferedReader(new StringReader(errMsg));
   
  @@ -453,16 +453,11 @@
   int beginColon = line.indexOf(':', 2); 
   int endColon = line.indexOf(':', beginColon + 1);
   if ((beginColon >= 0) && (endColon >= 0)) {
  - if (errNode != null) {
  - // add previous error to error vector
  - errVec.add(new JavacErrorDetail(
  - fname,
  - lineNum,
  - errNode.getStart().getFile(),
  - errNode.getStart().getLineNumber(),
  - partialErrMsg.toString()));
  - partialErrMsg = new StringBuffer();
  +if (javacError != null) {
  +// add previous error to error vector
  +errVec.add(javacError);
}
  +
String lineNumStr = line.substring(beginColon + 1, endColon);
   try {
   lineNum = Integer.parseInt(lineNumStr);
  @@ -470,29 +465,53 @@
   // XXX
   }
   
  - // Map servlet line number to corresponding node in JSP page
  +errMsgBuf = new StringBuffer();
  +
  +// Attempt to map javac error line number to line in JSP page
ErrorVisitor errVisitor = new ErrorVisito

[GUMP@brutus]: jakarta-tomcat-4.0/tomcat-catalina failed

2004-05-25 Thread Stefan Bodewig 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project tomcat-catalina has an issue affecting its community integration.
This issue affects 14 projects, and has been outstanding for 2 runs.
Project State : 'Failed', Reason 'Build Failed'
The following are affected:
- cocoon-block-slide :  Java XML Framework
- cocoon-block-webdav :  Java XML Framework
- jakarta-cactus-documentation :  Cactus Documentation
- jakarta-cactus-release-12 :  Unit test framework for server-side java code
- jakarta-cactus-release-13 :  Unit test framework for server-side java code
- jakarta-cactus-sample-jetty-13 :  Cactus Jetty Sample (J2EE 1.3)
- jakarta-cactus-sample-servlet-13 :  Cactus Servlet Sample (J2EE 1.3)
- jakarta-slide :  Content Management System based on WebDAV technology
- jakarta-tomcat-4.0 :  Servlet 2.3 and JSP 1.2 Reference Implementation
- jakarta-tomcat-5 :  Servlet 2.4 and JSP 2.0 Reference Implementation
- jakarta-tomcat-catalina :  Servlet 2.4 Reference Implementation
- jakarta-tomcat-coyote :  Connectors to various web servers
- jakarta-tomcat-coyote_10 :  Connectors to various web servers
- jakarta-tomcat-jk :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Sole jar [catalina.jar] identifier set to project name
 -INFO- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet.jar.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging-api.jar.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.jar.
 -INFO- Enable "verbose" output, due to 1 previous error(s).
 -INFO- Failed with reason build failed
 -INFO- Enable "debug" output, due to build failure.


The following work was performed:
http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/gump_work/build_jakarta-tomcat-4.0_tomcat-catalina.html
Work Name: build_jakarta-tomcat-4.0_tomcat-catalina (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 2 seconds
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
 org.apache.tools.ant.Main -verbose 
-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Djtc.home=/usr/local/gump/public/workspace/jakarta-tomcat-connectors 
-Dversion=4.1.25-dev 
-Dcommons-beanutils-core.jar=/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar
 
-Dregexp.jar=/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040525.jar
 
-Dcommons-logging-api.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar
 -Dservlet.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar 
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar
 
-Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040525.jar
 
-Dcommons-digester.jar=/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar
 deploy-catalina 
[Working Directory: /usr/local/gump/public/workspace/jakarta-tomcat-4.0/catalina]
CLASSPATH : 
/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040525.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/fileupload/target/commons-fileupload-20040525.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040525.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-diges

DO NOT REPLY [Bug 29208] - start listening on port after everything has been initialized.

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29208

start listening on port after everything has been initialized.





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 20:29 ---
What is the problem? Is the patch bad, or do you think tomcat should really
start listening before it can process any requests? 

Thanks
Moh

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

DO NOT REPLY [Bug 29208] - start listening on port after everything has been initialized.

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29208

start listening on port after everything has been initialized.

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 20:26 ---
Sorry, I disagree with your proposed change.

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

DO NOT REPLY [Bug 29208] - start listening on port after everything has been initialized.

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29208

start listening on port after everything has been initialized.





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 19:44 ---
I re-read the reinitialization part and I think I understand it now (it's more
complicated that just stop/start because we don't want to restart the thread
pool). The patch above creates a new method "createSocket()" which is called
appropriately. 

Thanks
Moh

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

DO NOT REPLY [Bug 29208] - start listening on port after everything has been initialized.

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29208

start listening on port after everything has been initialized.





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 19:40 ---
Created an attachment (id=11663)
patch file for PoolTcpEndpoint.java

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

DO NOT REPLY [Bug 29208] New: - start listening on port after everything has been initialized.

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29208

start listening on port after everything has been initialized.

   Summary: start listening on port after everything has been
initialized.
   Product: Tomcat 5
   Version: 5.0.18
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Connector:HTTP
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


We have several startup servlets that take a very long time to start (15
minutes).  Tomcat binds the server socket before it's ready to process requests.
This causes all sorts of headaches for us. Ideally, the socket should be bound
only when tomcat is really ready to process requests. This can be achieved
relatively simply by changing org.apache.tomcat.util.net.PoolTcpEndpoint and
moving the server socket binding code from initEndpoint to startEndpoint:

public void initEndpoint() throws IOException, InstantiationException {
if(factory==null)
factory=ServerSocketFactory.getDefault();
}

public void startEndpoint() throws IOException, InstantiationException {
if (!initialized) {
initEndpoint();
if(serverSocket==null) {
try {
if (inet == null) {
serverSocket = factory.createSocket(port, backlog);
} else {
serverSocket = factory.createSocket(port, backlog,
inet);
}
} catch ( BindException be ) {
throw new BindException(be.getMessage() + ":" + port);
}
}
if( serverTimeout >= 0 )
serverSocket.setSoTimeout( serverTimeout );
initialized = true;
}
if(isPool) {
tp.start();
}
...

A corresponding change should be made to the reinitialization code in
acceptSocket. I'm not sure I understand the subtleties of the reinitialization
code, so I'll leave that for the experts. (To my uninitiated eyes,
reinitializtion should be as simple as stopEndpoint(); startEndpoint();).

Thanks
Moh

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

DO NOT REPLY [Bug 29198] - pageEncoding and translation time including

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29198

pageEncoding and translation time including

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 16:46 ---
According to JSP 2.0 spec:

JSP.4.1 Page Character Encoding

The page character encoding is the character encoding in which the JSP page or
tag file itself is encoded. The character encoding is determined for each file
separately, even if one file includes another using the include directive
(Section JSP.1.10.3).

Note that this is not backward comapitble with JSP 1.2, which allows the
behavior you expect; but there are lots of problems with that in the past, and
the expert group felt that this needed to be clarified.

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

respuestas sobre el Chat

2004-05-25 Thread ayudachat 


Algunas preguntas frecuentes sobre inconvenientes al ingresar al chat son:



Si puede ingresar su Nick en el recuadro de texto pero no inicia la sesión de chat 
pueder ser por que dicho Nick se encuentre registrado por otra persona en tal caso 
pruebe cambiarlo o agregarle algún numero.

También puede ser que su ip se encuentre prohibida por el moderador en este caso hay 
que esperar algunas horas hasta que se libere, observe el recuadro blanco de reportes 
cada vez que intenta ingresar para saber cual es el caso. Si sólo lee un mensaje de 
"error" puede ser necesario reiniciar su computadora.



FALTA DE MAQUINA VIRTUAL DE JAVA

Para Windows XP, WinNT, WinME, Win98

Si por alguna razón su navegador le avisa que NO tiene instalada la compatibilidad con 
JAVA, la mejor alternativa es bajar la Maquina virtual de Java desde el sitio oficial 
de Sun

http://www.java.com/en/index.jsp  En esta página clickeando en "Download Java 
Software", automaticamentte le va a detectar e instalar la version necesaria para su 
PC.

 

Luego de un par de minutos que se complete el proceso ya lo puede probar

www.paysandu.com/chat



OTRAS RAZONES POSIBLES

Cuando aparece un recuadro gris en la pantalla y luego de varios segundos no aparece 
el acceso al Chat. Las razones pueden ser las siguientes, que en ese momento la 
conexión esté muy lenta y demora más de lo habitual; si es este el caso y esperando no 
se soluciona puede desconectarse/conectarse de Internet para volver a intentarlo. 

Si no se soluciona o nota que esto es frecuente, entonces puede ser que tenga muchos 
archivos temporales en el cache de su maquina.



Como Limpiar la memoria caché?

Si el caché está lleno, las páginas nuevas se abrirán muy lentamente o no se abrirán. 
Es posible que la memoria caché esté llena de páginas desfasadas o inútiles; por ello 
es buena idea limpiarla de vez en cuando. A continuación explicamos cómo limpiar la 
memoria caché dependiendo del navegador que tenga:



*

LIMPIAR CACHE EN INTERNET EXPLORER, instrucciones:



Haga clic en "Herramientas" (Tools) en la parte superior de la ventana de su navegador 
y luego seleccione "Opciones de Internet" (Internet Options).



Cuando emerja la ventana, haga clic en el cuadro "eliminar archivos" (delete files).



Marque la opción "eliminar contenido fuera de línea" (delete offline content) y haga 
clic en "Aceptar" (OK).



Haga también clic en el botón "limpiar historial" (clear history).



Haga clic en "Aceptar" (OK) hasta salir del cuadro de preferencias. 

Después de haber vaciado el caché, y estando conectado a Internet vaya a 
www.paysandu.com/chat.html oprima las teclas Ctrl y Shift y pulse el botón 
"Actualizar" (refresh) o (Reload) en su navegador a la misma vez luego de algunos 
segundos deberá aparecer el recuadro del nombre y boton login de acceso al Chat





LIMPIAR CACHE EN NETSCAPE, instrucciones:



Haga clic en "edición" (edit) en la parte superior de la ventana de su navegador y a 
continuación en "preferencias" (preferences).



Cuando emerja la ventana, haga clic en las opciones "limpiar historial" (clear 
history) y en "limpiar barra de localización" (clear location bar).



A continuación haga clic en el signo + que se encuentra junto a la opción "avanzado" 
(advanced).



Seleccione la opción "caché".



Haga clic en las opciones "limpiar memoria caché" (clear memory cache) y en "limpiar 
disco caché" (clear disk cache).



Haga clic en "Aceptar" (OK) hasta salir de la ventana.





LIMPIAR CACHE EN AOL, siga los siguientes pasos:



Busque "preferencias" (preferences) en el menú "mi aol" (my aol).



Luego haga clic en "www".



Haga clic en el botón "eliminar archivos" (delete files). Aparecerá una ventana 
preguntándole si desea borrar los archivos temporales de Internet.



Marque el cuadro de la opción "eliminar contenido fuera de línea" (delete offline 
content) y haga clic en el botón Aceptar (OK).



A continuación haga clic en el botón "eliminar historial" (delete history).



Haga clic en "Aceptar" (OK) hasta que salga del menú de preferencias.

Después de haber vaciado el caché, vaya a www.paysandu.com/chat.html y pulse el botón 
"Actualizar" (refresh) o "Volver a cargar" (Reload) en su navegador



**

Si usted es usuario de WebTv no podrá acceder al Chat, esta es una limitacion del 
proveedor de este tipo de servicio que no admite Java. Tampoco se pueden conectar en 
una red interna a través de un Fire Wall sin que el administrador del mismo lo 
autorice previamente.



En este chat al igual que en el foro de encuentros, los enlaces entre usuarios y o 
canales se producen 100% en la web de www.paysandu.com es decir no exiten accesos a 
través de servidores IRC u de otro tipo.



  





COMANDOS DE USO EN EL CHAT DE ENCUENTROS SANDUCEROS



Los siguientes comandos se pueden ejecutar en la línea de diálogo seguidos del 
caractér / 



algunos de ellos se han simpli

AutoReply: Ihre Anfrage!

2004-05-25 Thread service 

Sehr geehrter freenet.de Interessent,
 
vielen Dank für Ihr Interesse an unseren Diensten und Produkten!
 
Bitte beachten Sie, dass Sie eine automatische Antwort erhalten haben 
und auf diese E-Mail nicht geantwortet werden kann.
Eine gesonderte weitere Antwort auf Ihre E-Mail Anfrage erhalten Sie nicht.
 
Haben Sie Fragen zu unseren Tarifen, so besuchen Sie uns unter: http://tarif.freenet.de
 
Möchten Sie in Einrichtungshilfestellungen stöbern, so öffnen Sie bitte: 
http://hilfe.freenet.de
 
Wenn Sie nicht die gewünschte Hilfe in den zur Verfügung gestellten Informationen 
auffinden konnten, nutzen Sie unseren für Kunden kosten- freien E-Mail Service über 
unser Kontakt-Formular.
 
Um eine hochwertige, qualifizierte und schnelle Bearbeitung Ihrer Anfrage 
sicherzustellen, haben wir unseren E-Mail Service für Sie optimiert. 
Nutzen Sie einfach unser Kundenkontakt-Formular unter: http://online-hilfe.freenet.de
 
Bitte beachten Sie, dass Sie über ein kostenfreien freenet.de Mitglieds- namen 
verfügen müssen, um unseren kostenlosen E-Mail Service in 
Anspruch nehmen zu können. 
 
Noch nicht kostenfrei registriert bei freenet.de? 
Einfach schnell und kostenfrei anmelden unter my.freenet.de
 
Viel Spaß bei freenet.de 
Ihr freenet.de Serviceteam
 
Kontakt unter:
http://service.freenet.de

[GUMP@brutus]: jakarta-tomcat-4.0/tomcat-catalina failed

2004-05-25 Thread Stefan Bodewig 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project tomcat-catalina has an issue affecting its community integration.
This issue affects 14 projects.
Project State : 'Failed', Reason 'Build Failed'
The following are affected:
- cocoon-block-slide :  Java XML Framework
- cocoon-block-webdav :  Java XML Framework
- jakarta-cactus-documentation :  Cactus Documentation
- jakarta-cactus-release-12 :  Unit test framework for server-side java code
- jakarta-cactus-release-13 :  Unit test framework for server-side java code
- jakarta-cactus-sample-jetty-13 :  Cactus Jetty Sample (J2EE 1.3)
- jakarta-cactus-sample-servlet-13 :  Cactus Servlet Sample (J2EE 1.3)
- jakarta-slide :  Content Management System based on WebDAV technology
- jakarta-tomcat-4.0 :  Servlet 2.3 and JSP 1.2 Reference Implementation
- jakarta-tomcat-5 :  Servlet 2.4 and JSP 2.0 Reference Implementation
- jakarta-tomcat-catalina :  Servlet 2.4 Reference Implementation
- jakarta-tomcat-coyote :  Connectors to various web servers
- jakarta-tomcat-coyote_10 :  Connectors to various web servers
- jakarta-tomcat-jk :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Sole jar [catalina.jar] identifier set to project name
 -INFO- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet.jar.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging-api.jar.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.jar.
 -INFO- Enable "verbose" output, due to 2 previous error(s).
 -INFO- Failed with reason build failed
 -INFO- Enable "debug" output, due to build failure.


The following work was performed:
http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/gump_work/build_jakarta-tomcat-4.0_tomcat-catalina.html
Work Name: build_jakarta-tomcat-4.0_tomcat-catalina (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 2 seconds
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
 org.apache.tools.ant.Main -verbose 
-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Djtc.home=/usr/local/gump/public/workspace/jakarta-tomcat-connectors 
-Dversion=4.1.25-dev 
-Dcommons-beanutils-core.jar=/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar
 
-Dregexp.jar=/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040525.jar
 
-Dcommons-logging-api.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar
 -Dservlet.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar 
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar
 
-Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040525.jar
 
-Dcommons-digester.jar=/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar
 deploy-catalina 
[Working Directory: /usr/local/gump/public/workspace/jakarta-tomcat-4.0/catalina]
CLASSPATH : 
/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040525.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/fileupload/target/commons-fileupload-20040525.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040525.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/worksp

DO NOT REPLY [Bug 29180] - Tag attributes with array type don't work

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29180

Tag attributes with array type don't work

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |
Version|4.0 Beta 1  |4.0.4 Final



--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 12:55 ---
Oops, I got the version wrong - this happens in Tomcat 4.0.4, and I suspect
(from looking at the source) in all other versions of Tomcat 4 as well.

In TagBeginGenerator.convertString(), the class object representing the
attribute's type is used to get the name of the class to put into the generated
source, which in the case of arrays ends up inserting something which isn't a
valid identifier. That code has been essentially unaltered since 2000, so if
I've diagnosed it correctly it should be present in all versions.

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

DO NOT REPLY [Bug 29180] - Tag attributes with array type don't work

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29180

Tag attributes with array type don't work

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 12:38 ---
Tomcat 4.0 beta1 is not supported

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

DO NOT REPLY [Bug 29182] - Jasper locks jar files when compiling JSPs through Ant

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29182

Jasper locks jar files when compiling JSPs through Ant





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 08:54 ---
I don't think this is a Javac or Ant issue - in fact, my testcase does not use
Javac at all. As I wrote privately to Kin-Man, I believe the problem is that
JspC uses URLClassLoader, which is known to lock jar files. When Jasper runs
inside the Catalina container, Catalina's WebappClassLoader is used, so the code
that locks jars is avoided.

But thanks for the hint with fork=true, this actually helped. I replaced the
 style of calling
Jasper by the  task, which allows to fork JspC:







 
 
 
 
 
 
 
 
 
 
 
 


When using the above code, jar files are not locked and my testcase succeeds.
However, I don't much like this solution, because:

- Code that uses  is uglier than when you use 
- Tomcat documentation recommends the use of , see:
  http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jasper-howto.html

So I would still appreciate if this is fixed.

There is an additional aspect: many current IDEs have some kind of Ant
integrations, and most IDEs run Ant internally, without launching a separate
process. So when JspC locks jar files, these jar files will be locked until the
IDE exits. That's another compelling reason to fix this issue. Thanks.

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

DO NOT REPLY [Bug 29198] New: - pageEncoding and translation time including

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29198

pageEncoding and translation time including

   Summary: pageEncoding and translation time including
   Product: Tomcat 5
   Version: 5.0.24
  Platform: All
OS/Version: All
Status: NEW
  Severity: Major
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I’m facing the following problem after installing tomcat5 and after some 
searching i'm convinced that that's a bug (a small e.g)

<%@ page contentType="text/html;charset=windows-1253"%>


HERE I've to define the contentType inside the file.jsp cause the inclusion 
occurs at request time (which is corect)

<%@ include file = "file2.jsp" %>
BUT HERE THE INCLUSION OCCURS AT TRANSLATION TIME SO (NORMALLY) I DON'T HAVE 
TO DEFINE THE contentType INSIDE FILE2.JSP (WRONG)

SO HERE LAYS THE PROBLEM I HAVE TO DEFINE contentType ALSO IN THE SECOND CASE 
IF I WANT TO HAVE THE TEXT DISPLAYED PROPERLY, SOMETHING THAT I DON'T FIND 
RIGHT AND IT'S NOT TECHNICAL RIGHT(I THINK IS A MATTER OF HOW TOMCAT 
TRANSALTES AND COMPILES JSPs INTO SERVLETS). WHEN I WAS USING TOMCAT 4.x I 
DIDN'T HAVE THIS PROBLEM!

So i checked the generated srvlets at "work" directory! so for the same 
characters i get:
...
  out.write("ááááááááááá"); 
// LINE FROM:  <%@ include file = "file2.jsp" %> (not properly displayed but 
// included at translation time(???)
  out.write("Ξ±Ξ±Ξ±Ξ±Ξ±Ξ±Ξ±Ξ±Ξ±Ξ±Ξ±");
// text inside the index file...properly displayed
...

IT'S WRONG TO DEFINE THE CONTETNTYPE INSIDE ALL THE JSP FILES THAT ARE 
INCLUDED USING INCLUDING AT TRANSALATION TIME (<[EMAIL PROTECTED])

ps. all the other definitions, declarations, variables e.t.c are passed 
normally into files that are included at page translation time!

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

DO NOT REPLY [Bug 11656] - UTF-8 encoding not supported correctly in included text file or JSP Document

2004-05-25 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=11656

UTF-8 encoding not supported correctly in included text file or JSP Document





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 08:23 ---
Hi,

I have a similar problem with UTF-8.
I explain. I have a file (index.html) with a link to a servlet in it.
This file is the same on 2 servers with 1 with version 4.1.27 of Tomcat and 1
with 4.1.29. On the version 27 it work properly (URL is well encoded in UTF-8 as
I wanted and in version 29 the URL is not encoded in UTF-8. I'd like to add that
my servlet are the same...

Any ideas on this problem ?

thanks

Jean

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

respuestas sobre el Chat

2004-05-25 Thread ayudachat 


Algunas preguntas frecuentes sobre inconvenientes al ingresar al chat son:



Si puede ingresar su Nick en el recuadro de texto pero no inicia la sesión de chat 
pueder ser por que dicho Nick se encuentre registrado por otra persona en tal caso 
pruebe cambiarlo o agregarle algún numero.

También puede ser que su ip se encuentre prohibida por el moderador en este caso hay 
que esperar algunas horas hasta que se libere, observe el recuadro blanco de reportes 
cada vez que intenta ingresar para saber cual es el caso. Si sólo lee un mensaje de 
"error" puede ser necesario reiniciar su computadora.



FALTA DE MAQUINA VIRTUAL DE JAVA

Para Windows XP, WinNT, WinME, Win98

Si por alguna razón su navegador le avisa que NO tiene instalada la compatibilidad con 
JAVA, la mejor alternativa es bajar la Maquina virtual de Java desde el sitio oficial 
de Sun

http://www.java.com/en/index.jsp  En esta página clickeando en "Download Java 
Software", automaticamentte le va a detectar e instalar la version necesaria para su 
PC.

 

Luego de un par de minutos que se complete el proceso ya lo puede probar

www.paysandu.com/chat



OTRAS RAZONES POSIBLES

Cuando aparece un recuadro gris en la pantalla y luego de varios segundos no aparece 
el acceso al Chat. Las razones pueden ser las siguientes, que en ese momento la 
conexión esté muy lenta y demora más de lo habitual; si es este el caso y esperando no 
se soluciona puede desconectarse/conectarse de Internet para volver a intentarlo. 

Si no se soluciona o nota que esto es frecuente, entonces puede ser que tenga muchos 
archivos temporales en el cache de su maquina.



Como Limpiar la memoria caché?

Si el caché está lleno, las páginas nuevas se abrirán muy lentamente o no se abrirán. 
Es posible que la memoria caché esté llena de páginas desfasadas o inútiles; por ello 
es buena idea limpiarla de vez en cuando. A continuación explicamos cómo limpiar la 
memoria caché dependiendo del navegador que tenga:



*

LIMPIAR CACHE EN INTERNET EXPLORER, instrucciones:



Haga clic en "Herramientas" (Tools) en la parte superior de la ventana de su navegador 
y luego seleccione "Opciones de Internet" (Internet Options).



Cuando emerja la ventana, haga clic en el cuadro "eliminar archivos" (delete files).



Marque la opción "eliminar contenido fuera de línea" (delete offline content) y haga 
clic en "Aceptar" (OK).



Haga también clic en el botón "limpiar historial" (clear history).



Haga clic en "Aceptar" (OK) hasta salir del cuadro de preferencias. 

Después de haber vaciado el caché, y estando conectado a Internet vaya a 
www.paysandu.com/chat.html oprima las teclas Ctrl y Shift y pulse el botón 
"Actualizar" (refresh) o (Reload) en su navegador a la misma vez luego de algunos 
segundos deberá aparecer el recuadro del nombre y boton login de acceso al Chat





LIMPIAR CACHE EN NETSCAPE, instrucciones:



Haga clic en "edición" (edit) en la parte superior de la ventana de su navegador y a 
continuación en "preferencias" (preferences).



Cuando emerja la ventana, haga clic en las opciones "limpiar historial" (clear 
history) y en "limpiar barra de localización" (clear location bar).



A continuación haga clic en el signo + que se encuentra junto a la opción "avanzado" 
(advanced).



Seleccione la opción "caché".



Haga clic en las opciones "limpiar memoria caché" (clear memory cache) y en "limpiar 
disco caché" (clear disk cache).



Haga clic en "Aceptar" (OK) hasta salir de la ventana.





LIMPIAR CACHE EN AOL, siga los siguientes pasos:



Busque "preferencias" (preferences) en el menú "mi aol" (my aol).



Luego haga clic en "www".



Haga clic en el botón "eliminar archivos" (delete files). Aparecerá una ventana 
preguntándole si desea borrar los archivos temporales de Internet.



Marque el cuadro de la opción "eliminar contenido fuera de línea" (delete offline 
content) y haga clic en el botón Aceptar (OK).



A continuación haga clic en el botón "eliminar historial" (delete history).



Haga clic en "Aceptar" (OK) hasta que salga del menú de preferencias.

Después de haber vaciado el caché, vaya a www.paysandu.com/chat.html y pulse el botón 
"Actualizar" (refresh) o "Volver a cargar" (Reload) en su navegador



**

Si usted es usuario de WebTv no podrá acceder al Chat, esta es una limitacion del 
proveedor de este tipo de servicio que no admite Java. Tampoco se pueden conectar en 
una red interna a través de un Fire Wall sin que el administrador del mismo lo 
autorice previamente.



En este chat al igual que en el foro de encuentros, los enlaces entre usuarios y o 
canales se producen 100% en la web de www.paysandu.com es decir no exiten accesos a 
través de servidores IRC u de otro tipo.



  





COMANDOS DE USO EN EL CHAT DE ENCUENTROS SANDUCEROS



Los siguientes comandos se pueden ejecutar en la línea de diálogo seguidos del 
caractér / 



algunos de ellos se han simpli