Redirect to http fail

[tpchan]

Hi,

I'm using Tomcat version 4.0 under Red Hat Linux 7.0. The problem we facing right now, 
is we had a box (let's call it box A) with ssl accelarator to encrypt and decrypt the 
https connection and then redirect back to web server (box B) using normal http 
connection. I didn't enable the SSL on box B, which is the web server. 

Here is when the problem occour. When I handshaking the cert for https, it failed to 
redirect me to normal http connection to the box B (non-SSL). Can anyone help me to 
solve this problem. Is there any configuration I need to edit?

Thank you in advance.

Emanduel Chan Tain Por
System Engineer
DotCom Consulting Sdn Bhd
DID : 603-62763230 ext. 112

Add new account

[tuandang]

I have configured Tomcat using James as local SMTP Server. I added following lines 
into /webapps/jetspeed/WEB-INF/conf/JetspeedResources.properties  :
mail.server=localhost confirm.email.from=Postmaster@localhost 

confirm.email.name=Jetspeed Postmaster confirm.email.subject=Jetspeed registration 

confirm.email.enable=false 

Then I restarted James and Tomcat. I entered "create new account" page using James' 
email address but I could not leave the page to go further. What did I do something 
wrong? Please help. 
Thanks
DangTuan
[EMAIL PROTECTED]

DO NOT REPLY [Bug 4356] - The JNDI namming is not working under apache webapp-module

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4356

The JNDI namming is not working under apache webapp-module





--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 21:17 ---
Probably not, since the Webapp connector is in a different engine (and the 
declaration of the extra resources is in the Context of a different engine). Or 
did I miss something ?

DO NOT REPLY [Bug 4356] New: - The JNDI namming is not working under apache webapp-module

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4356

The JNDI namming is not working under apache webapp-module

   Summary: The JNDI namming is not working under apache webapp-
module
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: Sun
   URL: http://207.249.0.102:8080/examples/servlet/JndiServlet
OS/Version: Solaris
Status: NEW
  Severity: Major
  Priority: Other
 Component: Unknown
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Runing the example from tomcat it works:

http://207.249.0.102:8080/examples/servlet/JndiServlet
Simple lookup test : 
Max exemptions value : 15
list() on /comp/env Context : 
Binding : mail: org.apache.naming.NamingContext
Binding : maxExemptions: java.lang.Integer
Binding : minExemptions: java.lang.Integer
Binding : jdbc: org.apache.naming.NamingContext
Binding : ejb: org.apache.naming.NamingContext
Binding : name3: java.lang.Integer
Binding : foo: org.apache.naming.NamingContext
listBindings() on /comp/env Context : 
Binding : mail: 
org.apache.naming.NamingContext:org.apache.naming.NamingContext@45f743
Binding : maxExemptions: java.lang.Integer:15
Binding : minExemptions: java.lang.Integer:1
Binding : jdbc: 
org.apache.naming.NamingContext:org.apache.naming.NamingContext@18c56d
Binding : ejb: 
org.apache.naming.NamingContext:org.apache.naming.NamingContext@497934
Binding : name3: java.lang.Integer:1
Binding : foo: 
org.apache.naming.NamingContext:org.apache.naming.NamingContext@348197


But when I try it from the Appache webserver I get:

http://207.249.0.102/examples/servlet/JndiServlet

JNDI lookup failed : javax.naming.NameNotFoundException: Name maxExemptions is 
not bound in this Context
list() on /comp/env Context : 
Binding : mail: org.apache.naming.NamingContext
Binding : minExemptions: java.lang.Integer
Binding : jdbc: org.apache.naming.NamingContext
Binding : ejb: org.apache.naming.NamingContext
Binding : name3: java.lang.Integer
Binding : foo: org.apache.naming.NamingContext
listBindings() on /comp/env Context : 
Binding : mail: 
org.apache.naming.NamingContext:org.apache.naming.NamingContext@41b571
Binding : minExemptions: java.lang.Integer:1
Binding : jdbc: 
org.apache.naming.NamingContext:org.apache.naming.NamingContext@6f137d
Binding : ejb: 
org.apache.naming.NamingContext:org.apache.naming.NamingContext@687719
Binding : name3: java.lang.Integer:1
Binding : foo: 
org.apache.naming.NamingContext:org.apache.naming.NamingContext@632802

aren't they sharing the same context's
Y tried to find what's up
and what I've got is that from Apache I get only what is in the WEB-INF/web.xml 
but not what was stated in the server.xml

DO NOT REPLY [Bug 4277] - can't compile webapp-module-1.0-tc40

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4277

can't compile webapp-module-1.0-tc40

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 20:49 ---
> Hi, how shoud I configure my GCC???
> any ideas?

I downloaded both GCC and GNU binutils from http://www.sunfreeware.com,
installed them, made sure that /usr/local/bin is in my PATH BEFORE
/usr/ccs/bin and compiled both Apache and WebApp... And it works...

Pier

In fact that way it compiled, and it's ruuning
Thanks a lot!

DO NOT REPLY [Bug 4354] - fatal relocation error for __lshrdi3

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4354

fatal relocation error for __lshrdi3

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

DO NOT REPLY [Bug 4354] - fatal relocation error for __lshrdi3

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4354

fatal relocation error for __lshrdi3

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||tomcat-
   ||[EMAIL PROTECTED]
 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 17:18 ---
Did you use the same compiler to compile Apache and the WebApp 
module? What compiler and version did you use to compile them?

DO NOT REPLY [Bug 4353] - Unable to load applications outside of $CATALINA_HOME/webapps, with mod_webapp

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4353

Unable to load applications outside of $CATALINA_HOME/webapps, with mod_webapp

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 17:15 ---
This bug has been fixed in CVS. Download a nightly snapshot from
http://nagoya.apache.org/~pier/ and compile the Java portion of the code.

cvs commit: jakarta-tomcat-connectors/jk/native/jni Makefile.linux

[costin]

costin  01/10/22 15:45:09

  Added:   jk/native/jni Makefile.linux
  Log:
  Added a small makefile for linux.
  
  After we switch to APR we should have a single ( and simple ) Makefile.
  
  Revision  ChangesPath
  1.1  jakarta-tomcat-connectors/jk/native/jni/Makefile.linux
  
  Index: Makefile.linux
  ===
  # Defines for example NSAPI programs running under SOLARIS
  
  CC_CMD=gcc -D_REENTRANT
  LD_SHAREDCMD=ld -G
  
  all:
  
  prepare:
  
  OS_TYPE=linux
  INCLUDEDIR=../common
  JAVA_INCLUDE=$(JAVA_HOME)/include
  
  JK_OBJS =  ../common/jk_map.o ../common/jk_util.o ../common/jk_pool.o jk_jnicb.o
  
  INCLUDE_FLAGS=-I$(INCLUDEDIR) -I$(JAVA_INCLUDE) -I$(JAVA_INCLUDE)/$(OS_TYPE)
  COMMON_DEFS=-Wall
  
  
  all: jni_connect.so 
  
  
  jni_connect.so: $(JK_OBJS)
  # $(MAKE) prepare
$(LD_SHAREDCMD) $(JK_OBJS) -o jni_connect.so $(EXTRA_LDDEFINES)
  
  .c.o:
$(CC_CMD) $(COMMON_DEFS) $(INCLUDE_FLAGS) -c $< 
  
  clean:
rm $(JK_OBJS)
  
  
  

Re: [ANNOUNCEMENT] Tomcat 3.3 Final Released

[Mike Anderson]

NetWare connectors are now available.

Mike Anderson

>>> [EMAIL PROTECTED] 10/22/01 02:16PM >>>
At long last, Tomcat 3.3 has reached "Final Release" and is available for
download.  With its refactored set of core classes and modules, it offers a
number of new features, better performance, and more flexible configuration
over its predecessors.  Also, it can be updated with add-on modules. The
PasswordPrompter add-on module is a simple example and is available with
this release. You can download the release from:

http://www.apache.org/dist/jakarta/jakarta-tomcat/release/v3.3 

Note: As of this moment, RPMs and netware connectors have not been added to
the web site. They will appear in the near future.


As a Tomcat 3.x release, it remains a reference implementation of the
Servlet 2.2 and JSP 1.1 specifications.  Note however that altering Tomcat's
behavior with respect to the Servlet 2.2 and JSP 1.1 specifications
invalidates its status as a reference implementation.

Since the configuration improvements often involve differences from earlier
Tomcat 3.2.x releases, you are strongly encouraged to review the "readme"
file in Tomcat's doc directory.  Especially section 5. "NEW FEATURES AND
CHANGES IN THIS RELEASE" where some of the important differences are listed.

A lot of new content has been added to the tomcat-ug.html.  In addition,
serverxml.html has been added to the site to provide reference information
about the modules.  If you upgrade to Tomcat 3.3, these documents are the
first place to look for information about how to use Tomcat 3.3.

To log problems or bugs, as well as submit patches, please refer to: 

http://jakarta.apache.org/site/bugs.html 

When logging bugs to Bugzilla, please specify the Product as "Tomcat 3" 
and the Version as "3.3 Final". Also, supplying a test case will greatly
improve our ability to address the problem.  Please do so if at all possible. 

Thanks,
Larry Isaacs

P.S. I would like to thank the countless people who have contributed to the
Tomcat 3.3 development.  A special thanks goes to Costin Manolache who did
the majority of the refactoring and is responsible in large part for many
of the improvements you will find in Tomcat 3.3.

DO NOT REPLY [Bug 4354] New: - fatal relocation error for __lshrdi3

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4354

fatal relocation error for __lshrdi3

   Summary: fatal relocation error for __lshrdi3
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: Sun
OS/Version: Solaris
Status: NEW
  Severity: Blocker
  Priority: Other
 Component: Webapps
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Hello,

I am trying to compile the tomcat webapp module 1.0 on a Solaris 8 system and I
am am getting these messages when running the 'apachectl configtest' command.  I
tried using the binary version of the module earlier and got similar errors:

cougar:/web/apache#./bin/apachectl configtest
Syntax error on line 206 of /web/apache_1.3.22/conf/httpd.conf:
Cannot load /web/apache_1.3.22/libexec/mod_webapp.so into server: ld.so.1:
/web/apache_1.3.22/bin/httpd: fatal: relocation error: file
/web/apache_1.3.22/libexec/mod_webapp.so: symbol __lshrdi3: referenced
symbol not found

I did a clean configure of the webapp module and it looked like it compiled
okay. I am using Apache 1.3.22.

cvs commit: jakarta-tomcat-connectors/webapp/apache-1.3 mod_webapp.c

[jfclere]

jfclere 01/10/22 15:11:14

  Modified:webapp/apache-1.3 mod_webapp.c
  Log:
  Some more typos.
  
  Revision  ChangesPath
  1.26  +3 -3  jakarta-tomcat-connectors/webapp/apache-1.3/mod_webapp.c
  
  Index: mod_webapp.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/apache-1.3/mod_webapp.c,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- mod_webapp.c  2001/10/22 21:44:21 1.25
  +++ mod_webapp.c  2001/10/22 22:11:14 1.26
  @@ -57,7 +57,7 @@
   
   /**
* @author  Pier Fumagalli 
  - * @version $Id: mod_webapp.c,v 1.25 2001/10/22 21:44:21 jfclere Exp $
  + * @version $Id: mod_webapp.c,v 1.26 2001/10/22 22:11:14 jfclere Exp $
*/
   
   #include 
  @@ -462,8 +462,8 @@
   req->clen=0;
   req->ctyp="\0";
   req->rlen=0;
  -req->ssld=(wa_ssldata *) apr_palloc(r->pool,sizeof(wa_ssldata));
  -req->ssld->ssl = (char *)ap_table_get(
  +req->ssld=(wa_ssldata *) apr_palloc(req->pool,sizeof(wa_ssldata));
  +req->ssld->cert = (char *)ap_table_get(
   r->subprocess_env,"SSL_CLIENT_CERT");
   
   /* Copy headers into webapp request structure */
  
  
  

DO NOT REPLY [Bug 4353] New: - Unable to load applications outside of $CATALINA_HOME/webapps, with mod_webapp

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4353

Unable to load applications outside of $CATALINA_HOME/webapps, with mod_webapp

   Summary: Unable to load applications outside of
$CATALINA_HOME/webapps, with mod_webapp
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: PC
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Connectors
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Applications that live outside of $CATALINA_HOME/webapps fail to load.

DO NOT REPLY [Bug 4352] New: - JDBCRealm does not work with CLIENT-CERT auth-method

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4352

JDBCRealm does not work with CLIENT-CERT auth-method

   Summary: JDBCRealm does not work with CLIENT-CERT auth-method
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: All
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When log in using CLIENT-CERT and MemoryRealm, the certificate's subject is 
used to match the user name to log the user in.  But when using the JDBCRealm , 
it fails, because the getPrincipal() method always return null!!!.

cvs commit: jakarta-tomcat-connectors/webapp/lib pr_warp.c

[jfclere]

jfclere 01/10/22 15:00:04

  Modified:webapp/lib pr_warp.c
  Log:
  Change ssl_cert to cert otherwise it even does not compile!
  
  Revision  ChangesPath
  1.18  +3 -3  jakarta-tomcat-connectors/webapp/lib/pr_warp.c
  
  Index: pr_warp.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/lib/pr_warp.c,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- pr_warp.c 2001/10/22 21:44:21 1.17
  +++ pr_warp.c 2001/10/22 22:00:04 1.18
  @@ -54,7 +54,7 @@
*   *
* = */
   
  -/* @version $Id: pr_warp.c,v 1.17 2001/10/22 21:44:21 jfclere Exp $ */
  +/* @version $Id: pr_warp.c,v 1.18 2001/10/22 22:00:04 jfclere Exp $ */
   #include "pr_warp.h"
   
   /* Initialize this provider. */
  @@ -431,12 +431,12 @@
   case TYPE_ASK_SSL_CLIENT: {
   wa_log(WA_MARK,"TYPE_ASK_SSL_CLIENT");
   /* Request for client certificate */
  -if (r->ssld->ssl_cert==NULL) {
  +if (r->ssld->cert==NULL) {
   pack->type=TYPE_REP_SSL_NO;
   pack->size=0;
   } else {
   pack->type=TYPE_REP_SSL_CERT;
  -p_write_string(pack,r->ssld->ssl_cert);
  +p_write_string(pack,r->ssld->cert);
   }
   wa_debug(WA_MARK,"CC bytes: (Sent=%d)",pack->size);
   if (n_send(conf->sock,pack)!=wa_true) {
  
  
  

Re: [PROPOSAL] Tomcat 3.2.4 release

[Bojan Smojver]

Marc Saegesser wrote:

> --
> Vote:  Tomcat 3.2.4 Release Plan
> [ ] +1  I am in favor of the release, and will help support it
> [X] +0  I am in favor of the release, but am unable to help support it
> [ ] -0  I am not in favor of the release
> [ ] -1  I am against this proposal (must include a reason).
> --

Bojan

DO NOT REPLY [Bug 4350] New: - SSLAuthenticator did not associate SSO session

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4350

SSLAuthenticator did not associate SSO session

   Summary: SSLAuthenticator did not associate SSO session
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: All
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When 'log in' using CLIENT-CERT, the SSLAuthenticator did not associate the SSO 
session with the user's session and cause the 'log out' to fail.  The following 
patch seem to fix it.


public boolean authenticate(HttpRequest request,
HttpResponse response,
LoginConfig config)
throws IOException {

// Have we already authenticated someone?
Principal principal =
((HttpServletRequest) request.getRequest()).getUserPrincipal();
if (principal != null) {
if (debug >= 1)
log("Already authenticated '" + principal.getName() + "'");
String ssoId = (String) request.getNote(Constants.REQ_SSOID_NOTE);
if (ssoId != null)
associate(ssoId, getSession(request, true));
return (true);
}

// Retrieve the certificate chain for this client
HttpServletResponse hres =
(HttpServletResponse) response.getResponse();
if (debug >= 1)
log(" Looking up certificates");
X509Certificate certs[] = (X509Certificate[])
request.getRequest().getAttribute(Globals.CERTIFICATES_ATTR);
if ((certs == null) || (certs.length < 1)) {
if (debug >= 1)
log("  No certificates included with this request");
hres.sendError(HttpServletResponse.SC_BAD_REQUEST,
   sm.getString("authenticator.certificates"));
return (false);
}

// Authenticate the specified certificate chain
principal = context.getRealm().authenticate(certs);
if (principal == null) {
if (debug >= 1)
log("  Realm.authenticate() returned false");
hres.sendError(HttpServletResponse.SC_UNAUTHORIZED,
   sm.getString("authenticator.unauthorized"));
return (false);
}

Session session = getSession(request, true);
// Cache the principal (if requested) and record this authentication
register(request, response, principal, Constants.CERT_METHOD,
 null, null);
if (principal != null) {
String ssoId = (String) request.getNote(Constants.REQ_SSOID_NOTE);
if (ssoId != null)
associate(ssoId, session);
}
return (true);

}

RE: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi SsiMediator.java

[Bip Thelin]

> -Original Message-
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]] 
> 
> Could you also commit these fixes to the 4.0 branch if you can ?

done, I have a bunch of enhancements on my table that I'm gonna
take care of as soon as possible, I'm in the process if relocating
back to sweden so I haven't been that active commiting code lately.

Regards, Bip

cvs commit: jakarta-tomcat-connectors/webapp/lib pr_warp.c

[jfclere]

jfclere 01/10/22 14:44:21

  Modified:webapp/apache-1.3 mod_webapp.c
   webapp/java Constants.java.in Makefile.in WarpConnector.java
WarpRequest.java
   webapp/lib pr_warp.c
  Added:   webapp/java WarpCertificates.java
  Log:
  Add logic for Client Certificate (Add Constantes for the rest of SSL support).
  Also fix the ServerSocketFactory (due to changes in TC4.0).
  
  Revision  ChangesPath
  1.25  +4 -1  jakarta-tomcat-connectors/webapp/apache-1.3/mod_webapp.c
  
  Index: mod_webapp.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/apache-1.3/mod_webapp.c,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- mod_webapp.c  2001/10/09 10:41:25 1.24
  +++ mod_webapp.c  2001/10/22 21:44:21 1.25
  @@ -57,7 +57,7 @@
   
   /**
* @author  Pier Fumagalli 
  - * @version $Id: mod_webapp.c,v 1.24 2001/10/09 10:41:25 jfclere Exp $
  + * @version $Id: mod_webapp.c,v 1.25 2001/10/22 21:44:21 jfclere Exp $
*/
   
   #include 
  @@ -462,6 +462,9 @@
   req->clen=0;
   req->ctyp="\0";
   req->rlen=0;
  +req->ssld=(wa_ssldata *) apr_palloc(r->pool,sizeof(wa_ssldata));
  +req->ssld->ssl = (char *)ap_table_get(
  +r->subprocess_env,"SSL_CLIENT_CERT");
   
   /* Copy headers into webapp request structure */
   if (r->headers_in!=NULL) {
  
  
  
  1.12  +44 -0 jakarta-tomcat-connectors/webapp/java/Constants.java.in
  
  Index: Constants.java.in
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/java/Constants.java.in,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- Constants.java.in 2001/08/09 20:02:15 1.11
  +++ Constants.java.in 2001/10/22 21:44:21 1.12
  @@ -363,4 +363,48 @@
* No payload.
*/
   public static final int TYPE_CBK_DONE=0x42;
  +
  +/**
  + * ASK_SSL: The WARP server (Tomcat) asks the WARP client to
  + * transfer the basic SSL information (cypher, keysize and session).
  + * 
  + * No payload.
  + */
  +public static final int TYPE_ASK_SSL=0x43;
  +
  +/**
  + * ASK_SSL_CLIENT: The WARP server (Tomcat) asks the WARP server to
  + * transfer the client certificate.
  + * (just the first element of the chain and the webserver should request
  + * for it to the browser if possible).
  + * 
  + * No payload.
  + */
  +public static final int TYPE_ASK_SSL_CLIENT=0x44;
  +
  +/**
  + * REP_SSL_CERT: The client certificate (remote peer).
  + * 
  + * Payload description:
  + * [string] The client certificate. (PEM format).
  + */
  +public static final int TYPE_REP_SSL_CERT=0x52;
  + 
  +/**
  + * REP_SSL: SSL information between 
  + * 
  + * Payload description:
  + * [string] The cipher_suite.
  + * [string] The ssl session. (That is not in the spec's).
  + * [ushort] size of the algorithm (56-128).
  + */
  +public static final int TYPE_REP_SSL=0x53;
  + 
  +/**
  + * REP_SSL_NO: Request SSL information is not available.
  + * 
  + * No payload.
  + */
  +public static final int TYPE_REP_SSL_NO=0x5F;
   }
  +
  
  
  
  1.4   +2 -1  jakarta-tomcat-connectors/webapp/java/Makefile.in
  
  Index: Makefile.in
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/java/Makefile.in,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- Makefile.in   2001/09/17 05:04:02 1.3
  +++ Makefile.in   2001/10/22 21:44:21 1.4
  @@ -56,7 +56,7 @@
   # = #
   
   # @author  Pier Fumagalli 
  -# @version $Id: Makefile.in,v 1.3 2001/09/17 05:04:02 pier Exp $
  +# @version $Id: Makefile.in,v 1.4 2001/10/22 21:44:21 jfclere Exp $
   
   include @TGTDIR@/Makedefs
   
  @@ -70,6 +70,7 @@
WarpRequest.java \
WarpRequestHandler.java \
WarpResponse.java \
  + WarpCertificates.java
   
   ARCHIVE = warp.jar
   
  
  
  
  1.24  +1 -1  jakarta-tomcat-connectors/webapp/java/WarpConnector.java
  
  Index: WarpConnector.java
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/java/WarpConnector.java,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- WarpConnector.java2001/10/19 19:16:43 1.23
  +++ WarpConnector.java2001/10/22 21:44:21 1.24
  @@ -74,7 +74,7 @@
   import org.apache.catalina.Response;
   import org.apache.catalina.Service;
   import org.apache.catalina.net.DefaultServerSocketFactory;
  -import 

DO NOT REPLY [Bug 4330] - ClassCastException with DocumentBuilderFactoryImpl

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4330

ClassCastException with DocumentBuilderFactoryImpl





--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 14:45 ---
This is hardly a jasper problem.  xerces.jar is part of Tomcat 4.0.1 Final
distriubution; but make sure you don't have any incompatible XML parser that got
loaded instead.  Does JDK 1.4 come with one?  Try using JDK 1.3 to see if it
change anything.

In any case, please give me a test case that I can run with JDK1.4.  Thanks.

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi SsiMediator.java

[bip]

bip 01/10/22 14:38:22

  Modified:catalina/src/share/org/apache/catalina/util/ssi Tag:
tomcat_40_branch SsiMediator.java
  Log:
  Bugfixes
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.7.2.1   +9 -10 
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi/SsiMediator.java
  
  Index: SsiMediator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi/SsiMediator.java,v
  retrieving revision 1.7
  retrieving revision 1.7.2.1
  diff -u -r1.7 -r1.7.2.1
  --- SsiMediator.java  2001/07/22 20:25:15 1.7
  +++ SsiMediator.java  2001/10/22 21:38:22 1.7.2.1
  @@ -1,8 +1,8 @@
   /*
* SsiMediator.java
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi/SsiMediator.java,v
 1.7 2001/07/22 20:25:15 pier Exp $
  - * $Revision: 1.7 $
  - * $Date: 2001/07/22 20:25:15 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi/SsiMediator.java,v
 1.7.2.1 2001/10/22 21:38:22 bip Exp $
  + * $Revision: 1.7.2.1 $
  + * $Date: 2001/10/22 21:38:22 $
*
* 
*
  @@ -86,7 +86,7 @@
   /**
* @author Bip Thelin
* @author Amy Roh
  - * @version $Revision: 1.7 $, $Date: 2001/07/22 20:25:15 $
  + * @version $Revision: 1.7.2.1 $, $Date: 2001/10/22 21:38:22 $
*
*/
   public class SsiMediator {
  @@ -404,13 +404,12 @@
   }else if (path.indexOf('/', 1)==-1) {
   //root context
   servletContext = servletContext.getContext("/");
  -} else if (!contextPath.equals("")) {
  +} else if (!contextPath.equals("") &&
  +   (normalized !=null) && (normalized.startsWith(contextPath))) 
{
   //starts with the context path of this webapp
  -if ((normalized !=null) && (normalized.startsWith(contextPath))) {
  -// strip off the context path
  -servletContext = servletContext.getContext(contextPath);
  -normalized = normalized.substring(contextPath.length());
  -}
  +// strip off the context path
  +servletContext = servletContext.getContext(contextPath);
  +normalized = normalized.substring(contextPath.length());
   } else if (normalized != null){
   // find which context is the right one to handle
   String context = normalized.substring(0, path.indexOf('/', 1));
  
  
  

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets SsiInvokerServlet.java

[bip]

bip 01/10/22 14:35:48

  Modified:catalina/src/share/org/apache/catalina/servlets Tag:
tomcat_40_branch SsiInvokerServlet.java
  Log:
  Bugfixes
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.8.2.1   +23 -6 
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/SsiInvokerServlet.java
  
  Index: SsiInvokerServlet.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/SsiInvokerServlet.java,v
  retrieving revision 1.8
  retrieving revision 1.8.2.1
  diff -u -r1.8 -r1.8.2.1
  --- SsiInvokerServlet.java2001/07/22 20:25:11 1.8
  +++ SsiInvokerServlet.java2001/10/22 21:35:48 1.8.2.1
  @@ -1,8 +1,8 @@
   /*
* SsiInvokerServlet.java
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/SsiInvokerServlet.java,v
 1.8 2001/07/22 20:25:11 pier Exp $
  - * $Revision: 1.8 $
  - * $Date: 2001/07/22 20:25:11 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/SsiInvokerServlet.java,v
 1.8.2.1 2001/10/22 21:35:48 bip Exp $
  + * $Revision: 1.8.2.1 $
  + * $Date: 2001/10/22 21:35:48 $
*
* 
*
  @@ -99,7 +99,7 @@
*
* @author Bip Thelin
* @author Amy Roh
  - * @version $Revision: 1.8 $, $Date: 2001/07/22 20:25:11 $
  + * @version $Revision: 1.8.2.1 $, $Date: 2001/10/22 21:35:48 $
*/
   public final class SsiInvokerServlet extends HttpServlet {
   /** Debug level for this servlet. */
  @@ -111,6 +111,8 @@
   /** Expiration time in seconds for the doc. */
   private Long expires = null;
   
  +/** Should we ignore unsupported/misspelled SSI Directives */
  +private boolean ignoreUnsupportedDirective = false;
   
   /** virtual path can be webapp-relative */
   private boolean isVirtualWebappRelative = false;
  @@ -143,8 +145,19 @@
   ;
   }
   
  -value = getServletConfig().getInitParameter("isVirtualWebappRelative");
  -isVirtualWebappRelative = Integer.parseInt(value) > 0 ? true : false;
  +try {
  +value = getServletConfig().getInitParameter("isVirtualWebappRelative");
  +isVirtualWebappRelative = Integer.parseInt(value) > 0 ? true : false;
  +} catch (Throwable t) {
  +;
  +}
  +
  +try {
  +value = 
getServletConfig().getInitParameter("ignoreUnsupportedDirective");
  +ignoreUnsupportedDirective = Integer.parseInt(value) > 0 ? true : false;
  +} catch (Throwable t) {
  +;
  +}
   
   try {
   value = getServletConfig().getInitParameter("expires");
  @@ -235,6 +248,8 @@
   return;
   }
   
  +res.setContentType("text/html;charset=UTF-8");
  +
   if (expires != null) {
   res.setDateHeader("Expires", (
   new java.util.Date()).getTime() + expires.longValue() * 1000);
  @@ -306,6 +321,8 @@
   out.write((ssiCommand.getStream(strParamType, 
strParam)).getBytes());
   } else
   ssiCommand.process(strParamType, strParam);
  +} else if(ignoreUnsupportedDirective && ssiCommand==null) {
  +;
   } else {
   out.write(ssiMediator.getError());
   }
  
  
  

cvs commit: jakarta-tomcat-4.0/catalina/src/conf web.xml

[bip]

bip 01/10/22 14:28:55

  Modified:catalina/src/conf Tag: tomcat_40_branch web.xml
  Log:
  SSI Additions
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.22.2.6  +9 -1  jakarta-tomcat-4.0/catalina/src/conf/web.xml
  
  Index: web.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/conf/web.xml,v
  retrieving revision 1.22.2.5
  retrieving revision 1.22.2.6
  diff -u -r1.22.2.5 -r1.22.2.6
  --- web.xml   2001/10/12 19:55:26 1.22.2.5
  +++ web.xml   2001/10/22 21:28:54 1.22.2.6
  @@ -157,7 +157,11 @@
 
 
 
  -
  +  
  +  
  +  
  +  
  +  
 
 
 
  @@ -181,6 +185,10 @@
   
 isVirtualWebappRelative
 0
  +
  +
  +  ignoreUnsupportedDirective
  +  1
   
   4
 
  
  
  

Re: DO NOT REPLY [Bug 4339] - Cannot use "//" comments in JSP code

[Paul Speed]

Ah,

Sorry.  _That_ makes perfect sense.

It's what I get for not reading the original bug report in more 
detail.

Although, I would expect in the following case...

> When you do something like this:
> 
>   <% System.out.println(); // Hello %> Some template text
> 
> then this gets translated into
> 
>   System.out.println();  // Hello Some template text

To instead get:

System.out.println(); // Hello 
out.print( "Some template text" );

Since "Some template text" is clearly outside of the <% %>, wouldln't
it be turned into generated output instead of code?  Or am I being
pedantic and what you really meant was:

System.out.println(); // Hello out.print( "Some template text" );

or somesuch?

-Paul Speed

"Craig R. McClanahan" wrote:
> 
> On Mon, 22 Oct 2001, Paul Speed wrote:
> 
> > Date: Mon, 22 Oct 2001 13:48:08 -0400
> > From: Paul Speed <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > Subject: Re: DO NOT REPLY [Bug 4339]  - Cannot use "//" comments in JSP
> > code
> >
> > Only partially related to the bug, so I'm replying directly instead
> > of through bugzilla...
> >
> > Does this mean that JSP uses a different Java language specification?
> > If so, where can I find this separate specification?  Are there any
> > other big things like this that are incompatible with normal Java
> > syntax?
> >
> 
> The JSP specification does not mandate the use of Java as a scripting
> language -- you can use any language you want (as specified by the
> "language" attribute of the <%@ page %> directive).  However, many of the
> features related to scripting are defined *only* for Java.
> 
> Note also that Jasper (the JSP page compiler in Tomcat) only supports Java
> as a scripting language at the moment.
> 
> However, more germane to this bug report:
> 
> * Scriptlets are required to be well-formed according to the
>   rules of the scripting language in use (JSP 1.2, Section 2.11.2).
>   Thus, if you mistakenly leave off a semicolon at the end of a
>   Java statement in a scriptlet, the compilation error you get is
>   your fault.  It's also your fault if the scope of your language
>   element extends outside the closing "%>" delimiter in a manner
>   that causes invalid code to be created (such as mismatching "}"
>   brackets), or the case described in the following point.
> 
> * Scriptlets are translated into the generated code according
>   to the following rule (JSP 1.2, Section 6.4.2):
> 
> <% scriptlet %> -->scriptlet
> 
>   In other words, no newline is added after the "%>" by the page
>   compiler (though the developer could certainly put a newline there).
> 
> When you do something like this:
> 
>   <% System.out.println(); // Hello %> Some template text
> 
> then this gets translated into
> 
>   System.out.println();  // Hello Some template text
> 
> and you get what you pay for.  If you want to use // comments, do this
> instead:
> 
>   <% System.out.println(); // Hello
>   %> Some template text
> 
> and it will work fine.
> 
> > Thanks,
> > -Paul Speed
> >
> 
> Craig
> 
> > [EMAIL PROTECTED] wrote:
> > >
> > > 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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4339
> > >
> > > Cannot use "//" comments in JSP code
> > >
> > > [EMAIL PROTECTED] changed:
> > >
> > >What|Removed |Added
> > > 
> > >  Status|NEW |RESOLVED
> > >  Resolution||WONTFIX
> > >
> > > --- Additional Comments From [EMAIL PROTECTED]  2001-10-22 10:11 
>---
> > > You should not be using "//" comments.  You have absolutely no control over the
> > > Java code that is generated for your page, so it is your responsibility to use
> > > well-formed constructs.  In this particular case, that means to use /* */ style
> > > comment markers so that you can explicitly close them.  Even if we changed
> > > Tomcat to do what you suggest, depending on this would not be portable and you'd
> > > have massive problems as soon as you tried to switch to some other container
> > > that didn't do it.
> > >
> > > Using scriptlets at all can lead you into lots of other problems (such as
> > > intermixing business logic and presentation logic that makes it very hard to
> > > maintain and enhance your applications), but that is a whole separate
> > > discussion.
> >

Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi SsiMediator.java

[Remy Maucherat]

> bip 01/10/22 13:47:42
>
>   Modified:catalina/src/share/org/apache/catalina/util/ssi
> SsiMediator.java
>   Log:
>   Fix for relativepath issues across contexts.
>
>   PR: 4326 / 4307
>   Submitted by: [EMAIL PROTECTED] (Rami Hänninen) /
[EMAIL PROTECTED]

Could you also commit these fixes to the 4.0 branch if you can ?

Thanks,
Remy

cvs commit: jakarta-tomcat-4.0/catalina/src/conf web.xml

[bip]

bip 01/10/22 13:57:24

  Modified:catalina/src/conf web.xml
  Log:
  additional information about the Ssi 'ignoreUnsupportedDirective' parameter.
  
  Revision  ChangesPath
  1.28  +5 -0  jakarta-tomcat-4.0/catalina/src/conf/web.xml
  
  Index: web.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/conf/web.xml,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- web.xml   2001/10/19 18:40:37 1.27
  +++ web.xml   2001/10/22 20:57:24 1.28
  @@ -137,6 +137,11 @@
   
   
   
  +
  +
  +
  +
  +
   
   
   
  
  
  

DO NOT REPLY [Bug 4307] - SSI Server Side Include

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4307

SSI Server Side Include

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 13:59 ---
Issue resolved, latest nightly should work. 20011023

*** This bug has been marked as a duplicate of 4326 ***

DO NOT REPLY [Bug 4326] - SSI servlet isVirtualWebappRelative parameter does not work

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4326

SSI servlet isVirtualWebappRelative parameter does not work

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 13:59 ---
*** Bug 4307 has been marked as a duplicate of this bug. ***

DO NOT REPLY [Bug 4326] - SSI servlet isVirtualWebappRelative parameter does not work

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4326

SSI servlet isVirtualWebappRelative parameter does not work

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 13:57 ---
Ssi Include should work correctly in the latest nightly.
20011023

   -bip

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi SsiMediator.java

[bip]

bip 01/10/22 13:47:42

  Modified:catalina/src/share/org/apache/catalina/util/ssi
SsiMediator.java
  Log:
  Fix for relativepath issues across contexts.
  
  PR: 4326 / 4307
  Submitted by: [EMAIL PROTECTED] (Rami Hänninen) / 
[EMAIL PROTECTED]
  
  Revision  ChangesPath
  1.8   +9 -10 
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi/SsiMediator.java
  
  Index: SsiMediator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi/SsiMediator.java,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- SsiMediator.java  2001/07/22 20:25:15 1.7
  +++ SsiMediator.java  2001/10/22 20:47:42 1.8
  @@ -1,8 +1,8 @@
   /*
* SsiMediator.java
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi/SsiMediator.java,v
 1.7 2001/07/22 20:25:15 pier Exp $
  - * $Revision: 1.7 $
  - * $Date: 2001/07/22 20:25:15 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/ssi/SsiMediator.java,v
 1.8 2001/10/22 20:47:42 bip Exp $
  + * $Revision: 1.8 $
  + * $Date: 2001/10/22 20:47:42 $
*
* 
*
  @@ -86,7 +86,7 @@
   /**
* @author Bip Thelin
* @author Amy Roh
  - * @version $Revision: 1.7 $, $Date: 2001/07/22 20:25:15 $
  + * @version $Revision: 1.8 $, $Date: 2001/10/22 20:47:42 $
*
*/
   public class SsiMediator {
  @@ -404,13 +404,12 @@
   }else if (path.indexOf('/', 1)==-1) {
   //root context
   servletContext = servletContext.getContext("/");
  -} else if (!contextPath.equals("")) {
  +} else if (!contextPath.equals("") &&
  +   (normalized !=null) && (normalized.startsWith(contextPath))) 
{
   //starts with the context path of this webapp
  -if ((normalized !=null) && (normalized.startsWith(contextPath))) {
  -// strip off the context path
  -servletContext = servletContext.getContext(contextPath);
  -normalized = normalized.substring(contextPath.length());
  -}
  +// strip off the context path
  +servletContext = servletContext.getContext(contextPath);
  +normalized = normalized.substring(contextPath.length());
   } else if (normalized != null){
   // find which context is the right one to handle
   String context = normalized.substring(0, path.indexOf('/', 1));
  
  
  

DO NOT REPLY [Bug 4339] - Cannot use "//" comments in JSP code

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4339

Cannot use "//" comments in JSP code





--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 13:37 ---
Hi,

It funny you should mention <% // %> as they work properly (After all, "//" on 
empty lines is valid under Java Code). So that's not a problem.

Anyway, with Craig's help I managed to resolve this issue. I am no longer able 
to reproduce the problem so I'll leave it as RESOLVED WORKSFORME and reopen it 
in the future if I get it again.

Thanks for your help,

Gili

DO NOT REPLY [Bug 4275] - java.lang.NullPointerException

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4275

java.lang.NullPointerException

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 13:18 ---
This seems like a NPE in xalan, not in tomcat. What xalan version ? Can't guess. Does 
it also fail in 3.3 ? 
The only possible problem tomcat can cause to xalan is the class loader, which is 
quite broken in 3.2.x. You must set Jdk12Interceptor manually in your 
server.xml, and make sure you replace jaxp.jar, parser.jar in lib/ with  xalan,xerces, 
etc

[ANNOUNCEMENT] Tomcat 3.3 Final Released

[Larry Isaacs]

At long last, Tomcat 3.3 has reached "Final Release" and is available for
download.  With its refactored set of core classes and modules, it offers a
number of new features, better performance, and more flexible configuration
over its predecessors.  Also, it can be updated with add-on modules. The
PasswordPrompter add-on module is a simple example and is available with
this release. You can download the release from:

http://www.apache.org/dist/jakarta/jakarta-tomcat/release/v3.3

Note: As of this moment, RPMs and netware connectors have not been added to
the web site. They will appear in the near future.


As a Tomcat 3.x release, it remains a reference implementation of the
Servlet 2.2 and JSP 1.1 specifications.  Note however that altering Tomcat's
behavior with respect to the Servlet 2.2 and JSP 1.1 specifications
invalidates its status as a reference implementation.

Since the configuration improvements often involve differences from earlier
Tomcat 3.2.x releases, you are strongly encouraged to review the "readme"
file in Tomcat's doc directory.  Especially section 5. "NEW FEATURES AND
CHANGES IN THIS RELEASE" where some of the important differences are listed.

A lot of new content has been added to the tomcat-ug.html.  In addition,
serverxml.html has been added to the site to provide reference information
about the modules.  If you upgrade to Tomcat 3.3, these documents are the
first place to look for information about how to use Tomcat 3.3.

To log problems or bugs, as well as submit patches, please refer to: 

http://jakarta.apache.org/site/bugs.html 

When logging bugs to Bugzilla, please specify the Product as "Tomcat 3" 
and the Version as "3.3 Final". Also, supplying a test case will greatly
improve our ability to address the problem.  Please do so if at all possible. 

Thanks,
Larry Isaacs

P.S. I would like to thank the countless people who have contributed to the
Tomcat 3.3 development.  A special thanks goes to Costin Manolache who did
the majority of the refactoring and is responsible in large part for many
of the improvements you will find in Tomcat 3.3.

cvs commit: jakarta-tomcat-site/docs news.html

[larryi]

larryi  01/10/22 13:06:18

  Modified:docs news.html
  Log:
  Update for Tomcat 3.3 Final
  
  Revision  ChangesPath
  1.11  +14 -1 jakarta-tomcat-site/docs/news.html
  
  Index: news.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/docs/news.html,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- news.html 2001/10/21 04:20:22 1.10
  +++ news.html 2001/10/22 20:06:18 1.11
  @@ -107,7 +107,20 @@
 
 
   
  -14 October 2001 - Tomcat 4.0.1 Final 
Released
  +22 October 2001 - Apache Tomcat 3.3 Final 
Released
  +At long last, Tomcat 3.3 has 
reached "Final Release"!  With its
  +refactored set of core classes and modules, it offers a number of
  +new features, better performance, and more flexible configuration
  +over its predecessors.  Also, it can be updated with add-on modules.
  +The PasswordPrompter add-on module is a simple example and is
  +available with this release.  You can find everything
  +http://www.apache.org/dist/jakarta/jakarta-tomcat/release/v3.3/bin";>here.
  +Note: Additional documentation 
updates are planned (as well as
  +maintenance bug fixes).  You can get the latest documentation at the
  +http://jakarta.apache.org/tomcat/tomcat-3.3-doc/index.html";>
  +Tomcat 3.3 Documentation site.
  +
  +14 October 2001 - Tomcat 4.0.1 
Final Released
   This is the final release of 
Tomcat 4.0.1, which is a maintenance release
   of Tomcat 4.0. Download it 
   http://www.apache.org/dist/jakarta/jakarta-tomcat-4.0/release/v4.0.1/";>here.
  
  
  

cvs commit: jakarta-tomcat-site/xdocs news.xml

[larryi]

larryi  01/10/22 13:05:57

  Modified:xdocsnews.xml
  Log:
  Update for Tomcat 3.3 Final
  
  Revision  ChangesPath
  1.9   +17 -0 jakarta-tomcat-site/xdocs/news.xml
  
  Index: news.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/xdocs/news.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- news.xml  2001/10/21 04:19:40 1.8
  +++ news.xml  2001/10/22 20:05:57 1.9
  @@ -10,6 +10,23 @@
   
   
   
  +22 October 2001 - Apache Tomcat 3.3 Final Released
  +
  +At long last, Tomcat 3.3 has reached "Final Release"!  With its
  +refactored set of core classes and modules, it offers a number of
  +new features, better performance, and more flexible configuration
  +over its predecessors.  Also, it can be updated with add-on modules.
  +The PasswordPrompter add-on module is a simple example and is
  +available with this release.  You can find everything
  +http://www.apache.org/dist/jakarta/jakarta-tomcat/release/v3.3/bin";>here.
  +
  +Note: Additional documentation updates are planned (as well as
  +maintenance bug fixes).  You can get the latest documentation at the
  +http://jakarta.apache.org/tomcat/tomcat-3.3-doc/index.html";>
  +Tomcat 3.3 Documentation site.
  +
  +
  +
   14 October 2001 - Tomcat 4.0.1 Final Released
   This is the final release of Tomcat 4.0.1, which is a maintenance release
   of Tomcat 4.0. Download it 
  
  
  

DO NOT REPLY [Bug 4339] - Cannot use "//" comments in JSP code

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4339

Cannot use "//" comments in JSP code

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||WORKSFORME



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 13:12 ---
Can you include a JSP page that have this problem ? I use // in jsps and never had 
problems.

My only guess could be that you use <%= // %>, but // is not valid in a 
java expression ( which is what <%= expects ). This will fail ( same as if 
you include a ; or anything that is not valid in an expression ).

DO NOT REPLY [Bug 4315] - EJB Access with weblogic.jar included: Can't access new InitialContext()

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4315

EJB Access with weblogic.jar included: Can't access new InitialContext()





--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 13:11 ---
Ok good. Did you want to put some additional comments (the last sentence looks 
incomplete) ?

PATCH: jk for tomcat4: Ajp13Connector.java

[James E Jurach Jr.]

I hacked out the patch below without completely understanding all the
issues involved, or all the ramifications of this change.  I crafted it by
eyeying org.apache.catalina.connector.http.HttpConnector, and after
applying it, mod_jk -> TC4 AJP13 connector appears to work.  Maybe someone
in the know can validate this change.

james


Index: java/org/apache/ajp/tomcat4/Ajp13Connector.java
===
RCS file: 
/home/cvspublic/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/Ajp13Connector.java,v
retrieving revision 1.6
diff -u -3 -r1.6 Ajp13Connector.java
--- java/org/apache/ajp/tomcat4/Ajp13Connector.java 2001/10/08 20:18:12 1.6
+++ java/org/apache/ajp/tomcat4/Ajp13Connector.java 2001/10/22 18:21:33
@@ -69,6 +69,11 @@
 import java.net.ServerSocket;
 import java.net.Socket;
 import java.security.AccessControlException;
+import java.security.KeyStoreException;
+import java.security.NoSuchAlgorithmException;
+import java.security.cert.CertificateException;
+import java.security.UnrecoverableKeyException;
+import java.security.KeyManagementException;
 import java.util.Stack;
 import java.util.Vector;
 import java.util.Enumeration;
@@ -85,7 +90,7 @@
 import org.apache.catalina.Response;
 import org.apache.catalina.Service;
 import org.apache.catalina.net.DefaultServerSocketFactory;
-import org.apache.catalina.net.ServerSocketFactory;
+import org.apache.catalina.ServerSocketFactory;
 import org.apache.catalina.util.LifecycleSupport;
 import org.apache.catalina.util.StringManager;
 
@@ -731,7 +736,9 @@
  *
  * @exception IOException if an input/output error occurs
  */
-private ServerSocket open() throws IOException {
+private ServerSocket open() throws IOException, KeyStoreException,
+   NoSuchAlgorithmException, CertificateException, UnrecoverableKeyException,
+   KeyManagementException {
 
 // Acquire the server socket factory for this Connector
 ServerSocketFactory factory = getFactory();
@@ -792,6 +799,21 @@
 // If reopening fails, exit
 logger.log("socket reopen: ", ex);
 break;
+} catch (KeyStoreException kse) {
+logger.log("socket reopen, keystore problem: ", kse);
+break;
+} catch (NoSuchAlgorithmException nsae) {
+logger.log("socket reopen, keystore algorithm problem: ", nsae);
+break;
+} catch (CertificateException ce) {
+logger.log("socket reopen, certificate problem: ", ce);
+break;
+} catch (UnrecoverableKeyException uke) {
+logger.log("socket reopen, unrecoverable key: ", uke);
+break;
+} catch (KeyManagementException kme) {
+logger.log("socket reopen, key management problem: ", kme);
+break;
 }
 continue;
}
@@ -903,6 +925,8 @@
try {
serverSocket = open();
} catch (IOException e) {
+   throw new LifecycleException(threadName + ".open", e);
+} catch (Exception e) {
throw new LifecycleException(threadName + ".open", e);
}
 

DO NOT REPLY [Bug 4315] - EJB Access with weblogic.jar included: Can't access new InitialContext()

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4315

EJB Access with weblogic.jar included: Can't access new InitialContext()





--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 12:45 ---
Hey,

long way, but I have strip down the bea weblogic.jar.

  
 
 



























my manifest --resource/WEBLOGIC-MANIFEST.MF---
Manifest-version: 1.0
Implementation-Vendor: BEA Systems
Implementation-Title: WebLogic Server 6.1  07/23/2001 22:31:20 #129251 
Implementation-Version: 6.1.0.0


It working.

Access jdbc orcale database with tomcat server.xml config and bea ejb's.

Puuh.
Peter

yet both tomcat 4 jndi tree and the bea jndi

Re: DO NOT REPLY [Bug 4339] - Cannot use "//" comments in JSP code

[Craig R. McClanahan]

On Mon, 22 Oct 2001, Paul Speed wrote:

> Date: Mon, 22 Oct 2001 13:48:08 -0400
> From: Paul Speed <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: DO NOT REPLY [Bug 4339]  - Cannot use "//" comments in JSP
> code
>
> Only partially related to the bug, so I'm replying directly instead
> of through bugzilla...
>
> Does this mean that JSP uses a different Java language specification?
> If so, where can I find this separate specification?  Are there any
> other big things like this that are incompatible with normal Java
> syntax?
>

The JSP specification does not mandate the use of Java as a scripting
language -- you can use any language you want (as specified by the
"language" attribute of the <%@ page %> directive).  However, many of the
features related to scripting are defined *only* for Java.

Note also that Jasper (the JSP page compiler in Tomcat) only supports Java
as a scripting language at the moment.

However, more germane to this bug report:

* Scriptlets are required to be well-formed according to the
  rules of the scripting language in use (JSP 1.2, Section 2.11.2).
  Thus, if you mistakenly leave off a semicolon at the end of a
  Java statement in a scriptlet, the compilation error you get is
  your fault.  It's also your fault if the scope of your language
  element extends outside the closing "%>" delimiter in a manner
  that causes invalid code to be created (such as mismatching "}"
  brackets), or the case described in the following point.

* Scriptlets are translated into the generated code according
  to the following rule (JSP 1.2, Section 6.4.2):

<% scriptlet %> -->scriptlet

  In other words, no newline is added after the "%>" by the page
  compiler (though the developer could certainly put a newline there).

When you do something like this:

  <% System.out.println(); // Hello %> Some template text

then this gets translated into

  System.out.println();  // Hello Some template text

and you get what you pay for.  If you want to use // comments, do this
instead:

  <% System.out.println(); // Hello
  %> Some template text

and it will work fine.

> Thanks,
> -Paul Speed
>

Craig


> [EMAIL PROTECTED] wrote:
> >
> > 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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4339
> >
> > Cannot use "//" comments in JSP code
> >
> > [EMAIL PROTECTED] changed:
> >
> >What|Removed |Added
> > 
> >  Status|NEW |RESOLVED
> >  Resolution||WONTFIX
> >
> > --- Additional Comments From [EMAIL PROTECTED]  2001-10-22 10:11 ---
> > You should not be using "//" comments.  You have absolutely no control over the
> > Java code that is generated for your page, so it is your responsibility to use
> > well-formed constructs.  In this particular case, that means to use /* */ style
> > comment markers so that you can explicitly close them.  Even if we changed
> > Tomcat to do what you suggest, depending on this would not be portable and you'd
> > have massive problems as soon as you tried to switch to some other container
> > that didn't do it.
> >
> > Using scriptlets at all can lead you into lots of other problems (such as
> > intermixing business logic and presentation logic that makes it very hard to
> > maintain and enhance your applications), but that is a whole separate
> > discussion.
>

DO NOT REPLY [Bug 3863] - BufferedServletInputStream doesn't buffer

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=3863

BufferedServletInputStream doesn't buffer

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 12:11 ---
Since the scope of changes to Tomcat 3.2.3 is limited, and buffering is already
implemented in Tomcat 3.3, I'm resolving this as "FIXED".

If you have improvements to offer, feel free to submit patches to the
tomcat-dev mailing list.

DO NOT REPLY [Bug 3863] - BufferedServletInputStream doesn't buffer

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=3863

BufferedServletInputStream doesn't buffer

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|REMIND  |



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 12:07 ---
Reopen to change resolution.

DO NOT REPLY [Bug 4206] - missing config files do not cause an error

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4206

missing config files do not cause an error

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||LATER



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 12:05 ---
Since this won't be addressed in 3.3, I'm changing the resolution to "LATER".
We will try to address it in 3.3.1.

DO NOT REPLY [Bug 4247] - Please add user session ID logging in the access log

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4247

Please add user session ID logging in the access log

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |
 Status|ASSIGNED|NEW

DO NOT REPLY [Bug 4206] - missing config files do not cause an error

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4206

missing config files do not cause an error

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|REMIND  |



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 12:04 ---
Reopen to change resolution

DO NOT REPLY [Bug 4247] - Please add user session ID logging in the access log

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4247

Please add user session ID logging in the access log

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||tomcat-
   ||[EMAIL PROTECTED]
 Status|NEW |ASSIGNED

Re: Cannot use "//" comments in JSP code

[Jon Stevens]

on 10/22/01 10:48 AM, "Paul Speed" <[EMAIL PROTECTED]> wrote:

> Only partially related to the bug, so I'm replying directly instead
> of through bugzilla...
> 
> Does this mean that JSP uses a different Java language specification?
> If so, where can I find this separate specification?  Are there any
> other big things like this that are incompatible with normal Java
> syntax?
> 
> Thanks,
> -Paul Speed

This is yet another great reason why you shouldn't embed Java code within
your templates. JSP != Java

-jon

Re: DO NOT REPLY [Bug 4339] - Cannot use "//" comments in JSP code

[Paul Speed]

Only partially related to the bug, so I'm replying directly instead
of through bugzilla...

Does this mean that JSP uses a different Java language specification?
If so, where can I find this separate specification?  Are there any
other big things like this that are incompatible with normal Java 
syntax?

Thanks,
-Paul Speed

[EMAIL PROTECTED] wrote:
> 
> 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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4339
> 
> Cannot use "//" comments in JSP code
> 
> [EMAIL PROTECTED] changed:
> 
>What|Removed |Added
> 
>  Status|NEW |RESOLVED
>  Resolution||WONTFIX
> 
> --- Additional Comments From [EMAIL PROTECTED]  2001-10-22 10:11 ---
> You should not be using "//" comments.  You have absolutely no control over the
> Java code that is generated for your page, so it is your responsibility to use
> well-formed constructs.  In this particular case, that means to use /* */ style
> comment markers so that you can explicitly close them.  Even if we changed
> Tomcat to do what you suggest, depending on this would not be portable and you'd
> have massive problems as soon as you tried to switch to some other container
> that didn't do it.
> 
> Using scriptlets at all can lead you into lots of other problems (such as
> intermixing business logic and presentation logic that makes it very hard to
> maintain and enhance your applications), but that is a whole separate
> discussion.

Cannot use "//" comments in JSP code - clarifications ?

[Denis Balazuc]

Hi all

I've read that bug report about comments in JSP files and don't really
understand - can someone clarify the issue for me ? thanks

I'm wondering what's wrong with "//", and what I might be doing wrong as I
myself use such comments within JSP files...
(those comments use to work well...it's even better than using HTML comments
in a JSP file as they won't appear in the generated HTML)

Actually, I don't understand the argument "You should not be using "//"
comments"

--"//" are part of the java language spec
-- the JSP API is made for implementing server-side pages using the java
language

Therefore, JSP pages should accept everything that it's in the Java specs,
including "//".
If such comments are misplaced and the compilation fails, Tomcat is not
supposed to do anything..

So what's the real issue then ?

> --- Additional Comments From [EMAIL PROTECTED]  2001-10-22
10:11 ---
> You should not be using "//" comments.  You have absolutely no control
over the
> Java code that is generated for your page, so it is your responsibility to
use
> well-formed constructs.  In this particular case, that means to use /* */
style
> comment markers so that you can explicitly close them.  Even if we changed
> Tomcat to do what you suggest, depending on this would not be portable and
you'd
> have massive problems as soon as you tried to switch to some other
container
> that didn't do it.
>
> Using scriptlets at all can lead you into lots of other problems (such as
> intermixing business logic and presentation logic that makes it very hard
to
> maintain and enhance your applications), but that is a whole separate
> discussion.

DO NOT REPLY [Bug 4332] - Compilation from .jsp to .java fail if newline in useBean tag

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4332

Compilation from .jsp to .java fail if newline in useBean tag

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 10:40 ---
When I tried your test with the 4.0 nightly build, it worked (i.e. it got an
InstantiationException, since there no such bean).  Can you try either 4.0.1
final or 4.0 nightly to see if either fix your problem?

DO NOT REPLY [Bug 4339] - Cannot use "//" comments in JSP code

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4339

Cannot use "//" comments in JSP code

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 10:21 ---
Sorry but your resolution makes no sense.

You seem to imply that:

- "//" comments are invalid within JSP code, which is incorrect.
- Just because other container implementations don't fix this issue, Tomcat 
shouldn't either. Which is also incorrect.

I never said Tomcat should convert "//" style comments to /* */ style comments 
for me. 

The way I look at it, you have two possible solutions:

- Tomcat scans for "//" style comments and removes the commented code before it 
compiles the JSP file into a Servlet. This is a quick-fix, but not ideal.

- Tomcat scans for "//" comments, compiles the line of code without the 
commented component, and appends the comment thereafter. For example:

JSP Code:

  System.out.println("This is a test"); //This should work quite well

Tomcat steps:

- Convert 'System.out.println("This is a test");' into Servlet
- Add "//This should work quite well" after resulting line of code

DO NOT REPLY [Bug 4339] - Cannot use "//" comments in JSP code

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4339

Cannot use "//" comments in JSP code

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 10:11 ---
You should not be using "//" comments.  You have absolutely no control over the
Java code that is generated for your page, so it is your responsibility to use
well-formed constructs.  In this particular case, that means to use /* */ style
comment markers so that you can explicitly close them.  Even if we changed
Tomcat to do what you suggest, depending on this would not be portable and you'd
have massive problems as soon as you tried to switch to some other container
that didn't do it.

Using scriptlets at all can lead you into lots of other problems (such as
intermixing business logic and presentation logic that makes it very hard to
maintain and enhance your applications), but that is a whole separate
discussion.

DO NOT REPLY [Bug 4339] New: - Cannot use "//" comments in JSP code

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4339

Cannot use "//" comments in JSP code

   Summary: Cannot use "//" comments in JSP code
   Product: Tomcat 3
   Version: 3.2.3 Final
  Platform: All
OS/Version: Windows NT/2K
Status: NEW
  Severity: Major
  Priority: Other
 Component: Servlet
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When I use "//" style comments inside JSP code, they end up commenting out the 
Servlet code Tomcat generates when converting my page from a JSP to a Servlet. 
You should make sure "//" comments do not comment out your code. This is pretty 
critical as many people use "//" style comments.

DO NOT REPLY [Bug 4334] - ServerName in httpd.conf vs. defaultHost in server.xml Error: addChild: Child name 'hostname.myserver.com' is not unique

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4334

ServerName in httpd.conf vs. defaultHost in server.xml Error: addChild:  Child name 
'hostname.myserver.com' is not unique

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||tomcat-
   ||[EMAIL PROTECTED]
 Status|NEW |ASSIGNED

DO NOT REPLY [Bug 4334] - ServerName in httpd.conf vs. defaultHost in server.xml Error: addChild: Child name 'hostname.myserver.com' is not unique

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4334

ServerName in httpd.conf vs. defaultHost in server.xml Error: addChild:  Child name 
'hostname.myserver.com' is not unique

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |

DO NOT REPLY [Bug 4296] - Allow to disable the shutdown listener

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4296

Allow to disable the shutdown listener

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:26 ---
The functionality is provided with the Service code bundled with Windows.

DO NOT REPLY [Bug 3509] - Apache 1.3.20 & mod_webapp & Tomcat 4b7 HANGS

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=3509

Apache 1.3.20 & mod_webapp & Tomcat 4b7 HANGS

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:25 ---
*** Bug 4294 has been marked as a duplicate of this bug. ***

DO NOT REPLY [Bug 4294] - apache tomcat connection is halted

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4294

apache tomcat connection is halted

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:25 ---


*** This bug has been marked as a duplicate of 3509 ***

DO NOT REPLY [Bug 4232] - Tomcat home page has a typo

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4232

Tomcat home page has a typo

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:24 ---
Fixed.

DO NOT REPLY [Bug 4277] - can't compile webapp-module-1.0-tc40

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4277

can't compile webapp-module-1.0-tc40

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |

cvs commit: jakarta-tomcat-site/xdocs index.xml

[craigmcc]

craigmcc01/10/22 09:14:42

  Modified:docs index.html
   xdocsindex.xml
  Log:
  Fix a typo on the Tomcat home page.
  
  PR: Bugzilla #4232
  Submitted by: Richard Gaushell
  
  Revision  ChangesPath
  1.12  +1 -1  jakarta-tomcat-site/docs/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/docs/index.html,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- index.html2001/10/21 04:20:22 1.11
  +++ index.html2001/10/22 16:14:42 1.12
  @@ -171,7 +171,7 @@
   performance improvements.  Version 3.3 is currently under development and 
   has begun beta testing.
   Tomcat 4.0.x.  
Tomcat 4.0.1 is the current production
  -quality release.  Tomcat 4.0 is the next generatation of 
  +quality release.  Tomcat 4.0 is the next generation of 
   Tomcat.  The 4.0 servlet container (Catalina) has been developed from the 
   ground up for flexibility and performance.  Version 4.0 implements the 
   final released versions of the Servlet 2.3 and JSP 1.2 specifications.
  
  
  
  1.11  +1 -1  jakarta-tomcat-site/xdocs/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/xdocs/index.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- index.xml 2001/10/21 04:19:40 1.10
  +++ index.xml 2001/10/22 16:14:42 1.11
  @@ -73,7 +73,7 @@
   has begun beta testing. 
   
   Tomcat 4.0.x.  Tomcat 4.0.1 is the current production
  -quality release.  Tomcat 4.0 is the next generatation of 
  +quality release.  Tomcat 4.0 is the next generation of 
   Tomcat.  The 4.0 servlet container (Catalina) has been developed from the 
   ground up for flexibility and performance.  Version 4.0 implements the 
   final released versions of the Servlet 2.3 and JSP 1.2 specifications.
  
  
  

DO NOT REPLY [Bug 4225] - minor bug in configure script for mod_webapp

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4225

minor bug in configure script for mod_webapp

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:21 ---
This is available in the nightly CVS snapshots at http://nagoya.apache.org/
~pier/

cvs commit: jakarta-tomcat-connectors/webapp/java WarpConfigurationHandler.java

[pier]

pier01/10/22 09:12:52

  Modified:webapp/java WarpConfigurationHandler.java
  Log:
  Fix for absolute paths to web-applications used in the first parameter
  to WebAppDeploy
  
  Revision  ChangesPath
  1.16  +6 -3  
jakarta-tomcat-connectors/webapp/java/WarpConfigurationHandler.java
  
  Index: WarpConfigurationHandler.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/webapp/java/WarpConfigurationHandler.java,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- WarpConfigurationHandler.java 2001/09/17 05:03:24 1.15
  +++ WarpConfigurationHandler.java 2001/10/22 16:12:52 1.16
  @@ -286,10 +286,13 @@
   logger.debug("No application for \""+applPath+"\"");
   
   Deployer deployer=(Deployer)host;
  -File file=new File(host.getAppBase()+File.separator+applName);
  +File file=new File(applName);
   if (!file.isAbsolute()) {
  -file=new File(System.getProperty("catalina.base"),
  -  host.getAppBase()+File.separator+applName);
  +file=new File(host.getAppBase()+File.separator+applName);
  +if (!file.isAbsolute()) {
  + file=new File(System.getProperty("catalina.base"),
  +  host.getAppBase()+File.separator+applName);
  +}
   }
   
   if (!file.exists()) {
  
  
  

DO NOT REPLY [Bug 4227] - Invalid CGI path

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4227

Invalid CGI path





--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:19 ---
Currently, the CGI servlet refuses to run a request that has "/./" or "/../" in
the CGI command path (as yours does), in order to avoid spoofing attacks that
try to access binaries outside of the appropriate webapp directory.  In this
case, it appears that the "/../" is occurring because you are letting the
standard startup script figure out what CATALINA_HOME is.

Could you try explicitly setting the CATALINA_HOME environment variable (to
"/opt/catalina") and see if that solves the problem for you?

DO NOT REPLY [Bug 4212] - How to configure Apache to serve static contents?

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4212

How to configure Apache to serve static contents?

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |
   Severity|Normal  |Enhancement



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:18 ---
This will be available shortly in the nightly snapshots.

DO NOT REPLY [Bug 4211] - Apache 1.3.14 hangs constantly with image requests

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4211

Apache 1.3.14 hangs constantly with image requests

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:17 ---


*** This bug has been marked as a duplicate of 3509 ***

DO NOT REPLY [Bug 3509] - Apache 1.3.20 & mod_webapp & Tomcat 4b7 HANGS

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=3509

Apache 1.3.20 & mod_webapp & Tomcat 4b7 HANGS

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:17 ---
*** Bug 4211 has been marked as a duplicate of this bug. ***

DO NOT REPLY [Bug 4200] - Adapters for Microsoft IIS absent in Tomcat 4

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4200

Adapters for Microsoft IIS absent in Tomcat 4

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:17 ---
You can use AJPv13 and MOD_JK. AJPv13 has been added into Tomcat 
4.0 from version 4.0.1.

DO NOT REPLY [Bug 4198] - __lshrdi3: referenced symbol not found

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4198

__lshrdi3: referenced symbol not found

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:16 ---
This is indeed a clash in the compilers used to build Apache and the 
Module...

DO NOT REPLY [Bug 4187] - mod_webapp hangs

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4187

mod_webapp hangs

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:14 ---


*** This bug has been marked as a duplicate of 3509 ***

DO NOT REPLY [Bug 3509] - Apache 1.3.20 & mod_webapp & Tomcat 4b7 HANGS

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=3509

Apache 1.3.20 & mod_webapp & Tomcat 4b7 HANGS

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 09:14 ---
*** Bug 4187 has been marked as a duplicate of this bug. ***

DO NOT REPLY [Bug 4200] - Adapters for Microsoft IIS absent in Tomcat 4

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4200

Adapters for Microsoft IIS absent in Tomcat 4

[EMAIL PROTECTED] changed:

   What|Removed |Added

  Component|Unknown |Connectors

DO NOT REPLY [Bug 4198] - __lshrdi3: referenced symbol not found

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4198

__lshrdi3: referenced symbol not found

[EMAIL PROTECTED] changed:

   What|Removed |Added

  Component|Webapps |Connectors

Problem while compiling mod_jserv.so in Solaris 2.6

[Pal, Anshu]

Hi,
I am trying to compile the mod_jserv module. I went to the
src/native/apache/jserv directory( Tomcat 3.2.3) .
I typed the command 
apxs -c -o mod_jserv.so *.c
I got the error message 
Command failed ld:fatal Symbol referencing errors. No output written to
mod_jserv.so
along with the list of symbols it failed to resolve.

The object files are created successfully . It fails while it tries to link
them.


Thanks  

Anshu Pal
 

Proprietary/Confidential Information belonging to CGI may be contained in
this message. If you are not a recipient indicated or intended in
this message (or responsible for delivery of this message to such person),
or you think for any reason that this message may have been
addressed to you in error, you may not use or copy or deliver this message
to anyone else. In such case, you should destroy this message
and kindly notify the sender by reply e-mail.

DO NOT REPLY [Bug 4334] New: - ServerName in httpd.conf vs. defaultHost in server.xml Error: addChild: Child name 'hostname.myserver.com' is not unique

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4334

ServerName in httpd.conf vs. defaultHost in server.xml Error: addChild:  Child name 
'hostname.myserver.com' is not unique

   Summary: ServerName in httpd.conf vs. defaultHost in server.xml
Error: addChild:  Child name 'hostname.myserver.com' is
not unique
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: All
OS/Version: Solaris
Status: NEW
  Severity: Blocker
  Priority: Other
 Component: Connectors
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When ServerName and defaultHost are the same (As requested by documentation)

This error is not consitent, and does not always happen, but when is does, the 
temporary fix to this problem, is making the ServerName (httpd.conf) an IP 
address instead of a hostname.

This is what's thrown in the WrapEngine log files:

[org.apache.catalina.connector.warp.WarpConfigurationHandler]
java.lang.IllegalArgumentException: addChild:  Child name 'xxx.home.com' is
not unique at org.apache.catalina.core.ContainerBase.addChil 
(ContainerBase.java)
at org.apache.catalina.core.StandardEngine.addChild(StandardEngine.java)
 at org.apache.catalina.connector.warp.WarpConfigurationHandler.deploy
(WarpConfigurationHandler.java)
at org.apache.catalina.connector.warp.WarpConfigurationHandler.handle
(WarpConfigurationHandler.java)
at org.apache.catalina.connector.warp.WarpConnection.run(WarpConnection.java)
at java.lang.Thread.run(Thread.java:484)
...

Re: [PROPOSAL] Tomcat 3.2.4 release

[Pier Fumagalli]

> --
> Vote:  Tomcat 3.2.4 Release Plan
> [ ] +1  I am in favor of the release, and will help support it
> [X] +0  I am in favor of the release, but am unable to help support it
> [ ] -0  I am not in favor of the release
> [ ] -1  I am against this proposal (must include a reason).
> --

RE: [PROPOSAL] Tomcat 3.2.4 release

[Ignacio J. Ortega]

+1

Saludos ,
Ignacio J. Ortega

Re: [PROPOSAL] Tomcat 3.2.4 release

[Mike Anderson]

--
Vote:  Tomcat 3.2.4 Release Plan
[X] +1  I am in favor of the release, and will help support it
[ ] +0  I am in favor of the release, but am unable to help support it
[ ] -0  I am not in favor of the release
[ ] -1  I am against this proposal (must include a reason).
--

Mike Anderson

DO NOT REPLY [Bug 4266] - Jasper is unable to handle a jar containing multiple tlds.

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4266

Jasper is unable to handle a jar containing multiple tlds.

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 06:34 ---
Had a subtle build issue that caused the issue.
Sorry for confusion on this issue.

DO NOT REPLY [Bug 4332] - Compilation from .jsp to .java fail if newline in useBean tag

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4332

Compilation from .jsp to .java fail if newline in useBean tag





--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 06:16 ---
Here is the error message output (not very explicit):

org.apache.jasper.JasperException: Unable to compile class for JSP
at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:558)
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:176)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:188)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:1264)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
(...)


Compiling by hand with jspc gives the next output:

C:\TEMP\xx>D:\PROGRA~1\APACHE~1.0\bin\jspc x.jsp
Using CLASSPATH: D:\PROGRA~1\APACHE~1.0\classes;D:\PROGRA~1\APACHE~1.0\lib\jaspe
r-runtime.jar;D:\PROGRA~1\APACHE~1.0\lib\naming-factory.jar;D:\PROGRA~1\APACHE~1
.0\jasper\crimson.jar;D:\PROGRA~1\APACHE~1.0\jasper\jasper-compiler.jar;D:\PROGR
A~1\APACHE~1.0\jasper\jaxp.jar;D:\PROGRA~1\APACHE~1.0\common\lib\servlet.jar
2001-10-22 02:57:39 - ERROR-the file '\x.jsp' generated the following general ex
ception: java.lang.NullPointerException
java.lang.NullPointerException
at org.apache.jasper.compiler.JakartaCommentGenerator.generateEndComment
(JakartaCommentGenerator.java:146)
at org.apache.jasper.compiler.JspParseEventListener$GeneratorWrapper.gen
erate(JspParseEventListener.java:834)
at org.apache.jasper.compiler.JspParseEventListener.generateAll(JspParse
EventListener.java:241)
at org.apache.jasper.compiler.JspParseEventListener.endPageProcessing(Js
pParseEventListener.java:197)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:215)
at org.apache.jasper.JspC.parseFile(JspC.java:402)
at org.apache.jasper.JspC.parseFiles(JspC.java:722)
at org.apache.jasper.JspC.main(JspC.java:737)

DO NOT REPLY [Bug 4332] New: - Compilation from .jsp to .java fail if newline in useBean tag

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4332

Compilation from .jsp to .java fail if newline in useBean tag

   Summary: Compilation from .jsp to .java fail if newline in
useBean tag
   Product: Tomcat 4
   Version: 4.0 Final
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Major
  Priority: Other
 Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


This code doesn't compile:




when there is a newline between the  and  tags.

It does however compile when the newline is not present.

I'm not sure if the standard (dis)allows this, but for sure it is not nice.

I hope this helps.

Apache and Tomcat problem

[The Duke]

I'm using tomcat 4.0 with apache.

I have developped an application with tomcat and it works fine. When I use apache to 
go to my application I get the index file.

This file has a form to login. It calls a servlet that calls a bean. In the bean I use 
a xml file to find my password file. To find the xml file I use an URL to find it. And 
I use JDom to build the xml file.

When I use Tomcat everything works. When I use apache I can load the page, but I can't 
login. The servers just stop and I have to restart both.

I have located the place where the servers stop where JDom builds the document with 
the URL. (Document doc = builder.build(URL);)

The URL to locate the xml file is correct. When I type the URL in the address bar of 
the browser I get the file on screen. Also the xml file is correct otherwise the 
application wouldn't work at all.

The URL is constructed with getServerName, getServerPort and getContextPath.

I think that somehow the xml isn't found. But the URL is correct. I have tried to use 
different url's, like without a port. That didn't work either. I could login when I 
replaced the URL with File. But that is not an option, because then I would have to 
change the code whenever is use the application somewhere else.

I have run out of ideas, can anyone help?

Dennis Knol


Make a difference, help support the relief efforts in the U.S.
http://clubs.lycos.com/live/events/september11.asp

DO NOT REPLY [Bug 4330] New: - ClassCastException with DocumentBuilderFactoryImpl

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4330

ClassCastException with DocumentBuilderFactoryImpl

   Summary: ClassCastException with DocumentBuilderFactoryImpl
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Blocker
  Priority: Other
 Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I was starting up the Tomcat 4.0 servlet engine, running against JDK 1.4 and 
received the following error when attempting to start the engine.  I'm willing 
to believe this is just a library issue on my part, but I'm not an idiot and 
have been hunting it down for 2 days now.  I even rebuilt the XErces2 jar under 
my running 1.4 environment (by downloading the source and running Ant against 
my JAVA_HOME.  

I have posted several questions to the tomcat users list with no reponses, and 
searched through the archives for similar issues with no success.  This leads 
me to believe it may in fact be a bug.  Please contact for more info if 
necessary.

The Stacktrace follows

javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception
at org.apache.catalina.core.StandardWrapper.load
(StandardWrapper.java:871)
at org.apache.catalina.core.StandardContext.loadOnStartup
(StandardContext.java:3267)
at org.apache.catalina.core.StandardContext.start
(StandardContext.java:3384)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:612)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at org.apache.catalina.core.StandardEngine.start
(StandardEngine.java:307)
at org.apache.catalina.core.StandardService.start
(StandardService.java:388)
at org.apache.catalina.core.StandardServer.start
(StandardServer.java:505)
at org.apache.catalina.startup.Catalina.start(Catalina.java:776)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:42)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:28)
at java.lang.reflect.Method.invoke(Method.java:313)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
- Root Cause -
java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
at javax.xml.parsers.DocumentBuilderFactory.newInstance
(DocumentBuilderFactory.java:103)
at org.apache.jasper.parser.ParserUtils.parseXMLDocument
(ParserUtils.java:183)
at org.apache.jasper.compiler.TldLocationsCache.processWebDotXml
(TldLocationsCache.java:165)
at org.apache.jasper.compiler.TldLocationsCache.
(TldLocationsCache.java:138)
at org.apache.jasper.EmbededServletOptions.
(EmbededServletOptions.java:324)
at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:266)
at org.apache.catalina.core.StandardWrapper.load
(StandardWrapper.java:852)
at org.apache.catalina.core.StandardContext.loadOnStartup
(StandardContext.java:3267)
at org.apache.catalina.core.StandardContext.start
(StandardContext.java:3384)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:612)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at org.apache.catalina.core.StandardEngine.start
(StandardEngine.java:307)
at org.apache.catalina.core.StandardService.start
(StandardService.java:388)
at org.apache.catalina.core.StandardServer.start
(StandardServer.java:505)
at org.apache.catalina.startup.Catalina.start(Catalina.java:776)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:42)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:28)
at java.lang.reflect.Method.invoke(Method.java:313)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)

RE: [PROPOSAL] Tomcat 3.2.4 release

[Larry Isaacs]

[X] +1  I am in favor of the release, and will help support it

Larry

DO NOT REPLY [Bug 4327] New: - access log not rotated

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4327

access log not rotated

   Summary: access log not rotated
   Product: Tomcat 4
   Version: 4.0 Final
  Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
  Severity: Minor
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Acess log produced by org.apache.catalina.valves.AccessLogValve
doesn't switch it's file name when going to next date, so we have different
days in one file.

DO NOT REPLY [Bug 4326] New: - SSI servlet isVirtualWebappRelative parameter does not work

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4326

SSI servlet isVirtualWebappRelative parameter does not work

   Summary: SSI servlet isVirtualWebappRelative parameter does not
work
   Product: Tomcat 4
   Version: 4.0 Final
  Platform: Sun
OS/Version: Linux
Status: NEW
  Severity: Major
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Server side include servlet accepts an isVirtualWebappRelative parameter,
defined in tomcat4/conf/web.xml. The parameter value '0' (false, the default!)
should make server side virtual paths relative to server root. This does not
however seem work :-/

In particular, if in server.xml we first define two contexts:




where the files in the /archive context contain SSI references:



and the files in /tk context contain the corresponding SSI files:

/home/ibs/tk/tyyli_yleinen_ibs.ssi

In web.xml, we then (try to) make virtual references relative to root:


  isVirtualWebappRelative
  0


If we now try to access files that contain SSI directives:

http://localhost/archive/testfile.shtml

The result is a SSI error [an error occurred while processing this directive],
even if:

http://localhost/tk/tyyli_yleinen_ibs.ssi

is available and works fine.

If we then ignore the /tk context, set 'isVirtualWebappRelative=1' and rename
the /home/ibs/tk directory as /home/ibs/archive/tk, and therefore make the SSI
files to appear as:

http://localhost/archive/tk/tyyli_yleinen_ibs.ssi

the SSI include mechanism produces the expected result.

It would therefore seem that the 'isVirtualWebappRelative=0' fails to resolve
virtual paths, or download file content. If it is the downloading that fails,
one possible reason for this could be that loading files from some other context
is not permitted for some reason. Without any error messages anywhere, it is
however hard to tell.

It is a very typical scenario that SSI virtual paths should be interpreted
relative to server root (that's why it is (or should be) the default behaviour,
too). Such files should also to be able to reside in different contexts.

RE: [PROPOSAL] Tomcat 3.2.4 release

[GOMEZ Henri]

+0, I'll do the RPM and linux mod_jk/mod_jserv stuff :)

-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .) 
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-Original Message-
>From: Pier Fumagalli [mailto:[EMAIL PROTECTED]]
>Sent: Saturday, October 20, 2001 4:03 AM
>To: [EMAIL PROTECTED]
>Subject: Re: [PROPOSAL] Tomcat 3.2.4 release
>
>
>Marc Saegesser at [EMAIL PROTECTED] wrote:
>
>> 
>---
>---
>> Vote:  Tomcat 3.2.4 Release Plan
>> [ ] +1  I am in favor of the release, and will help support it
>> [X] +0  I am in favor of the release, but am unable to help 
>support it
>> [ ] -0  I am not in favor of the release
>> [ ] -1  I am against this proposal (must include a reason).
>> 
>---
>---
>
>

DO NOT REPLY [Bug 4315] - EJB Access with weblogic.jar included: Can't access new InitialContext()

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=4315

EJB Access with weblogic.jar included: Can't access new InitialContext()





--- Additional Comments From [EMAIL PROTECTED]  2001-10-22 04:31 ---
I have no success with setup tomcat with weblogic jndi.

I copy my weblogic.jar to WEB-INF/lib and setup a resource
/WEB-INF/weblogic-jndi.properties to configure my remote
ejb access.

Here my jsp access :

>>>
Properties props = new Properties() ;
 props.load(
   application.getResourceAsStream("/WEB-INF/weblogic-jndi.properties") 
) ;
 
 Context   ctx = new InitialContext(props);
 EchoHome home =
(EchoHome) 
javax.rmi.PortableRemoteObject.narrow(ctx.lookup("echo.EchoHome"),
 EchoHome.class);
 Echo echo = home.create();
<<<

But with weblogic.jar I have no chance to accces Tomcat JNDI tree!
That is very bad. I want access some remote EJB and access JDBC datasources
directly via tomcat.

>>>
javax.naming.NoInitialContextException: Cannot instantiate class: 
org.apache.naming.java.javaURLContextFactory.  Root exception is 
java.lang.ClassCastException: org.apache.naming.java.javaURLContextFactory
at 
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:658)
at 
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.(InitialContext.java:174)
at 
org.apache.jsp.jdbc_0002daccess$jsp._jspService(jdbc_0002daccess$jsp.java:67)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:2
02)
<<<
Hups!

I thing the big weblogic.jar with all j2ee classes load some other
classes at the tomcat 4 distribution have at common/lib.

...


When have next week time, I working on spezial JNDI Resource factory
or at night I made a spezial weblogic.jar without j2ee classes that included at 
tomcat.

Help are very welcome ??

Thanx,
Peter