running jsp on tomcat

hi, can any one tell me how to run jsp on tomcat in solaris 2.6.jdk 1.1.3.tomcat3.1.i am able to run servlets but not jsp. regards and thanks subhomoy Feel the pulse of the stock market on the tip of your finger Online Investments at http://www.icicidirect.com.

BugRat Report #417 has been filed.

Bug report #417 has just been filed. You can view the report at the following URL: REPORT #417 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: high Severity: serious Co

[ANNOUNCEMENT] Tomcat 3.2 Beta 8

Thanks to everyone for the bug reports (and patches)! You can now download "beta 8" of the Tomcat 3.2 servlet container from: http://jakarta.apache.org/builds/tomcat/release/v3.2-beta-8 Relative to "beta 7", a number of critical bugs have been fixed, and several configuration options availa

Re: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/facade HttpServletResponseFacade.java

"Craig R. McClanahan" wrote: > > Hans Bergsten wrote: > > > [EMAIL PROTECTED] wrote: > > > > > > craigmcc00/11/20 15:59:43 > > > > > > Modified:src/share/org/apache/tomcat/facade Tag: tomcat_32 > > > HttpServletResponseFacade.java > > > Log: > > > Intra-docu

cvs commit: jakarta-tomcat/src/share/org/apache/jasper/runtime PageContextImpl.java

larryi 00/11/20 19:09:55 Modified:src/share/org/apache/jasper/runtime PageContextImpl.java Log: Port changes from tomcat_32 branch. Fix for bug report #412: public void removeAttribute(String name) does not work properly - removeAttribute now removes the attribute fro

Re: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/facade HttpServletResponseFacade.java

Hans Bergsten wrote: > [EMAIL PROTECTED] wrote: > > > > craigmcc00/11/20 15:59:43 > > > > Modified:src/share/org/apache/tomcat/facade Tag: tomcat_32 > > HttpServletResponseFacade.java > > Log: > > Intra-document references (i.e. relative urls starting with "#

Re: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/facade HttpServletResponseFacade.java

[EMAIL PROTECTED] wrote: > > craigmcc00/11/20 15:59:43 > > Modified:src/share/org/apache/tomcat/facade Tag: tomcat_32 > HttpServletResponseFacade.java > Log: > Intra-document references (i.e. relative urls starting with "#") never > need to be encoded. I'

cvs commit: jakarta-tomcat/src/webpages index.html

craigmcc00/11/20 18:43:17 Modified:src/share/org/apache/tomcat/core Tag: tomcat_32 Constants.java src/webpages Tag: tomcat_32 index.html Log: Set version numbers for 3.2-b8 release. Revision ChangesPath No revision

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/core RequestImpl.java

craigmcc00/11/20 18:39:07 Modified:src/share/org/apache/tomcat/core Tag: tomcat_32 RequestImpl.java Log: Lightly refactor the initialization and recycling code to make it easier to subclass this class in an embedded environment. Should have zero impact on

Re: 3.2 status -- no taglibs in jars

Pierre Delisle wrote: > > I'll commit the patch right now and I'd appreciate if you > > could run some exhaustive tests. > > Well, it may take a little while, as my commit is currently blocked > because of a lock held by Larry (I've notified him). > > Since the lock has been on for more than 10 m

Re: Problem with context initialization ?

Hi Arieh, I know about this problem, and 3.3 is going to fix this ( and other similar problems ) by defining a startup order and changing the code to implement it. I don't know any simple fix for 3.2, there is a lot of code that has to be changed. Costin On Mon, 20 Nov 2000, Arieh Markel wro

Re: Problem with context initialization ?

A better Exception trace follows (note the message) (the following is the tomcat console output) 2000-11-20 06:05:17 - Ctx( ): Exception in: R( + /login + null) - java.lang.ExceptionInInitializerError: java.lang.NullPointerException at at com.sun.esm.web.servlet.CMCServlet.s

Problem with context initialization ?

We are running into the following problem: . we start Tomcat in an embedded manner: use a server.xml that only includes interceptors and connectors create contexts programmatically initialize the context manager I am observing the following beh

cvs commit: jakarta-tomcat/src/share/org/apache/jasper/runtime JspRuntimeLibrary.java

larryi 00/11/20 16:47:16 Modified:src/share/org/apache/jasper/runtime JspRuntimeLibrary.java Log: Make setProperty with param="..." not set the property if the parameter is empty. Modify introspect() to allow introspecthelper() to decide whether to set or not set the prope

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/session ServerSession.java ServerSessionManager.java StandardSessionInterceptor.java

costin 00/11/20 16:31:15 Modified:src/etc server.xml src/share/org/apache/tomcat/helper SecurityTools.java src/share/org/apache/tomcat/request SessionInterceptor.java src/share/org/apache/tomcat/session ServerSession.java

BugRat Report #412 was closed (apparently by: Pierre Delisle)

Report #412 was closed by Person #0 Synopsis: public void removeAttribute(String name) does not work properly (logged in as: Pierre Delisle)

cvs commit: jakarta-tomcat/src/share/org/apache/jasper/runtime PageContextImpl.java

pierred 00/11/20 16:18:27 Modified:src/share/org/apache/jasper/runtime Tag: tomcat_32 PageContextImpl.java Log: Fix for bug report #412: public void removeAttribute(String name) does not work properly - removeAttribute now removes the attribute from

cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/runtime PageContextImpl.java

pierred 00/11/20 16:02:24 Modified:jasper/src/share/org/apache/jasper/runtime PageContextImpl.java Log: Fix for bug report #412: public void removeAttribute(String name) does not work properly - removeAttribute now removes the attribute from the 4 sc

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector HttpResponseBase.java

craigmcc00/11/20 16:00:40 Modified:catalina/src/share/org/apache/catalina/connector HttpResponseBase.java Log: Intra-document references (those that start with "#") never need to be encoded. Revision ChangesPath 1.17 +8 -4 jakarta-tom

BugRat Report #416 has been filed.

Bug report #416 has just been filed. You can view the report at the following URL: REPORT #416 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: high Severity: critical C

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/facade HttpServletResponseFacade.java

craigmcc00/11/20 15:59:43 Modified:src/share/org/apache/tomcat/facade Tag: tomcat_32 HttpServletResponseFacade.java Log: Intra-document references (i.e. relative urls starting with "#") never need to be encoded. Revision ChangesPath No

cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/runtime JspRuntimeLibrary.java

pierred 00/11/20 15:49:08 Modified:jasper/src/share/org/apache/jasper/runtime JspRuntimeLibrary.java Log: port larryi's bug fix in 3.2 to 4.0. - Apply Gareth Morgan's patch for value="", but don't allow setProperty with param="..." to set the prop

Re: PageContext.include(..) flushing buffer

Gary Albelli wrote: > I was reading this bug report and could not find where the jsp spec > indicates that the buffer should be flushed prior to processing the include. > You're right ... the servlet spec does not require this behavior (although JSP 1.1 pages that use are already used to causin

Tomcat Startup Problem

Hi, Can somebody please help me solve the error I am getting I try to start Tomcat on my machine. "Java.lang.ClassNot FoundException: org/apache/tomcat/service/http/HttpConnectionHandler" . In short I get Class not found exception for HttpConnectionHandler. I have set the TOMCAT_HOME and JAVA_HO

PageContext.include(..) flushing buffer

I was reading this bug report and could not find where the jsp spec indicates that the buffer should be flushed prior to processing the include. Thanks Gary winmail.dat

cvs commit: jakarta-tomcat/src/share/org/apache/jasper/runtime JspRuntimeLibrary.java

larryi 00/11/20 14:01:47 Modified:src/share/org/apache/jasper/runtime Tag: tomcat_32 JspRuntimeLibrary.java Log: Apply Gareth Morgan's patch for value="", but don't allow setProperty with param="..." to set the property if parameter is empty. Modify i

Re: Proper jsp:setProperty behavior for Tomcat 3.2

Larry Isaacs wrote: > ... > I'll try to commit a patch that fixes just the following: > > 1) Fix value="" without allowing param="..." to set. > 2) For a String array property, make "?prop=&prop=text" set the >property for property="*". Currently property="*" handling >assumes only simpl

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/config - New directory

costin 00/11/20 13:38:27 jakarta-tomcat/src/share/org/apache/tomcat/modules/config - New directory

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/session - New directory

costin 00/11/20 13:38:12 jakarta-tomcat/src/share/org/apache/tomcat/modules/session - New directory

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util/cookies - New directory

costin 00/11/20 13:38:00 jakarta-tomcat/src/share/org/apache/tomcat/util/cookies - New directory

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util MimeHeaders.java

costin 00/11/20 13:37:47 Modified:src/share/org/apache/tomcat/util MimeHeaders.java Log: Added a new method to MimeHeaders to do fast ( indexed ) searches for multi-value headers. The whole MimeHeaders will be re-written soon ( I have a first draft, but I want to make sure

RE: Proper jsp:setProperty behavior for Tomcat 3.2

> I would argue that in such a case, the developer should not > use an "indexed" property, but rather a simple property that > takes a String array as argument. > (i.e. the only difference with an "indexed property" is that > the index setter method would not be defined). I had not noticed the di

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

remm00/11/20 13:23:08 Modified:catalina/src/conf server.xml Log: - The AccessLogValve is now removed from the default configuration until further work is done to improve its performance. The XML is just commented out, so you can still easily use it if you want to. R

Re: PageContext.removeAttribute

Pierre Delisle wrote: > > > Bug report #412 has just been filed. > > > Synopsis: > > public void removeAttribute(String name) does not work properly > > > > Description: > > lt. spec from sun this method is required to remove > > the attribute from every scope. in class PageContextImpl > > howe

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/core Container.java Context.java ContextManager.java Request.java

costin 00/11/20 13:00:55 Modified:src/share/org/apache/tomcat/core Container.java Context.java ContextManager.java Request.java Log: Removed unused imports, commented code. Revision ChangesPath 1.40 +0 -2 jakarta-tomcat/src/share/org/ap

cvs commit: jakarta-tomcat/src/facade22/org/apache/tomcat/modules/facade22 JspInterceptor.java

costin 00/11/20 13:00:00 Modified:src/facade22/org/apache/tomcat/modules/facade22 JspInterceptor.java Log: Less "verbose" messages - the debug messages will be displayed only when debug is enabled. Revision ChangesPath 1.10 +31 -28 ja

PageContext.removeAttribute

> Bug report #412 has just been filed. > Synopsis: > public void removeAttribute(String name) does not work properly > > Description: > lt. spec from sun this method is required to remove > the attribute from every scope. in class PageContextImpl > however this only removes attributes from the

BugRat Report #415 has been filed.

Bug report #415 has just been filed. You can view the report at the following URL: REPORT #415 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: low Severity: non-critica

BugRat Report #414 has been filed.

Bug report #414 has just been filed. You can view the report at the following URL: REPORT #414 Details. Project: Catalina Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: medium Severity: seriou

Re: Proper jsp:setProperty behavior for Tomcat 3.2

Larry, As you pointed out, whether or not the sequence of parameters in the query string is reliable seems the key issue here. Let's consider the following two use cases: A) truly indexed fields HTML form with 5 text fields labeled "Period 1" to "Period 5". The data entered by the user in ea

Re: TC 3.3: RE: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/service/connector Ajp13ConnectorRequest.java

> Hola a Todos: > > > Asunto: cvs commit: > > jakarta-tomcat/src/share/org/apache/tomcat/service/connector > > Ajp13ConnectorRequest.java > > > > How about definitely deprecate org.apache.tomcat.service packages?? The package has been refactored and moved to org.apache.tomcat.modules.server.

Jsp file throws ArrayIndexOutOfBoundsException in MsgBuffer.appendBytes

Title: Jsp file throws ArrayIndexOutOfBoundsException in MsgBuffer.appendBytes I saw the same problem has been reported. See thread "Large JSP Files (8k+) Yield Buffer Overflow & Lots of Errors". Has this been fixed? I ran into the same problem using 3.2b6. Thanks -Sam

[Fwd: [REPOST] Windows SMB paths in server.xml please?]

Hello, guys, I've posted this twice to tomcat-user, and had no answer. Since I woud love to have it, I'm volunteering to make it work. The problem is that I have no idea as where to start looking the source: where is a URL translated to a real path by tomcat? Regards, Rogério Orig

BugRat Report #412 has been filed.

Bug report #412 has just been filed. You can view the report at the following URL: REPORT #412 Details. Project: Jasper Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: medium Severity: non-crit

RE: Proper jsp:setProperty behavior for Tomcat 3.2

Hi Pierre, Thanks, I was aware of: incorrectly allowing the set to get through. I just sent a separate e-mail concerning this. I looked at implementing a form of 3C. I asked someone here at SAS who has done a lot of HTML and JSP. He seemed to indicate to me that the sequence of parameters

RE: Proper jsp:setProperty behavior for Tomcat 3.2

I have a patch that assumes for indexed properties, empty parameter values should be ignored as is done for simple properties. Thus, for the following test cases: 1) 2) 3) the following results would occur for the specified query string: Query String Result1 Result2 Result3 ?

BugRat Report #411 was closed (apparently by: Pierre Delisle)

Report #411 was closed by Person #0 Synopsis: jsp:setProperty doesn't call set methods in beans if params have no value (logged in as: Pierre Delisle)

Re: Proper jsp:setProperty behavior for Tomcat 3.2

Larry Isaacs wrote: > > When applying Gareth Morgan's bug fix for JspRuntimeLibrary in the Tomcat MAIN > branch, a difference between the tomcat_32 and MAIN versions revealed that > Tomcat 3.2 still has the bug discovered by Glenn Nielsen. This is where: > > > > leaves the property un