XML parser

[Paul_Wallace]

Hi,
How can I parse XML using the Apache Tomcat server? Do I have to 
install a third party parser or is there one built in? I seem to remember 
reading somewhere there was? (AT 4.1.12). I am also looking at Xerces Java 
Parser however. Can someone throw some light on the subject please?

Thnaks

Paul. 

persistent storage / library?

[Paul_Wallace]

Hello,
Can anyone tell me of a library equivalent in JSP please? I would 
like to define variables that have eternal persistence, and that are 
loaded into memory when the service starts. The nature of such persistence 
means that session will not fit the bill.

Thanks for all input

Paul.

DO NOT REPLY [Bug 14660] - Unable to use custom tag when running applicaiton in war

[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=14660

Unable to use custom tag when running applicaiton in war

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED

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

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

[kinman]

kinman  2002/11/18 19:27:44

  Modified:jasper2/src/share/org/apache/jasper/compiler SmapUtil.java
  Log:
  - "Fix" 14660: Accessing smap files in a jar produces a NPE.
  
Comment out the offending codes, as this functionality is not currently
useful.
  
  Revision  ChangesPath
  1.7   +6 -0  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/SmapUtil.java
  
  Index: SmapUtil.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/SmapUtil.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- SmapUtil.java 22 Oct 2002 03:00:20 -  1.6
  +++ SmapUtil.java 19 Nov 2002 03:27:44 -  1.7
  @@ -100,6 +100,11 @@
// set up our SMAP generator
SmapGenerator g = new SmapGenerator();
   
  + /** Disable reading of input SMAP because:
  + 1. There is a bug here: getRealPath() is null if .jsp is in a jar
  + Bugzilla 14660.
  + 2. Mappings from other sources into .jsp files are not supported.
  + TODO: fix 1. if 2. is not true.
// determine if we have an input SMAP
String smapPath = inputSmapPath(ctxt.getRealPath(ctxt.getJspFile()));
   File inputSmap = new File(smapPath);
  @@ -109,6 +114,7 @@
String subSmapString = new String(subSmap, SMAP_ENCODING);
g.addSmap(subSmapString, "JSP");
}
  + **/
   
   // now, assemble info about our own stratum (JSP) using JspLineMap
   SmapStratum s = new SmapStratum("JSP");
  
  
  

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

DO NOT REPLY [Bug 14622] - Jasper fails when security manager is set by a jsp

[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=14622

Jasper fails when security manager is set by a jsp

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 01:54 ---
Again, trying to set the security manager from a JSP or a Servlet is illegal
(and Tomcat will throws and exception) if you run Tomcat using -security.

If you don't start Tomcat using -security, all the security mechanism is broken
and will not be initialized properly. IF you are seeing that problem using
-security, then add more information...but if not, then please do not re-open
the bug.

-- Jeanfrancois

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

DO NOT REPLY [Bug 14660] - Unable to use custom tag when running applicaiton in war

[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=14660

Unable to use custom tag when running applicaiton in war





--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 01:47 ---
Here is the simple way to reproduce the bug:

In the server.xml add the following  entry inside the  element

like:
 

..





the context points to a jsp-examples2.war (just a copy of the jsp-examples.war)
as docBase. When the containter starts, there will be no jsp-examples2 directory
created. The webapplication can be access in http://localhost:8080/jsp-examples2/

but when click the links of the samples, there will be exception:

Such as:

java.lang.NullPointerException
at org.apache.jasper.compiler.SmapUtil.inputSmapPath(SmapUtil.java:163)
at org.apache.jasper.compiler.SmapUtil.generateSmap(SmapUtil.java:104)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:303)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:413)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext
.java:552)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:297)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2
95)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:194)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:276)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:996)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
torBase.java:474)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:996)

at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:
2523)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:996)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:996)

at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:22
3)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:413)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:380)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:537)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:533)
at java.lang.Thread.run(Thread.java:536)


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

Re: readable bugzilla? tomcat-dev

[Amy Roh]

> Is there some readable list on tasks needed to be performed and bugs
needed
> to be fixed on Tomcat?  I would love to work on some stuff but I don't
have
> time to open all the bugzilla urls to see what the problems are for hours
> before beginning on a task.

One place to look is RELEASE-PLAN-4.1.txt.  It's been a while since its last
update and many bugs have already been addressed.

Amy

>
> Micael
>
> ---
>
> This electronic mail  transmission and any accompanying documents contain
> information belonging to the sender which may be confidential and legally
> privileged.  This information is intended only for the use of the
> individual or entity to whom this electronic mail transmission was sent as
> indicated above. If you are not the intended recipient, any disclosure,
> copying, distribution, or action taken in reliance on the contents of the
> information contained in this transmission is strictly prohibited.  If you
> have received this transmission in error, please delete the message.
Thank you
>
>
>
> --
> To unsubscribe, e-mail:

> For additional commands, e-mail:

>
>


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

DO NOT REPLY [Bug 14438] - Can't configure referrals in JNDI Realm

[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=14438

Can't configure referrals in JNDI Realm

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 01:36 ---
Enhancement added.  Thanks for the patch.

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

cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm JNDIRealm.java

[amyroh]

amyroh  2002/11/18 17:27:59

  Modified:catalina/src/share/org/apache/catalina/realm JNDIRealm.java
  Log:
  Port change to configure how JNDI should handle referrals returned by the server.
  
  Revision  ChangesPath
  1.3   +31 -4 
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java
  
  Index: JNDIRealm.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- JNDIRealm.java12 Nov 2002 20:09:29 -  1.2
  +++ JNDIRealm.java19 Nov 2002 01:27:59 -  1.3
  @@ -247,6 +247,14 @@
   
   
   /**
  + * How should we handle referrals?  Microsoft Active Directory can't handle 
  + * the default case, so an application authenticating against AD must 
  + * set referrals to "follow".
  + */
  +protected String referrals = null;
  +
  +
  +/**
* The base element for user searches.
*/
   protected String userBase = "";
  @@ -469,6 +477,23 @@
   
   
   /**
  + * Returns the current settings for handling JNDI referrals.
  + */
  +public String getReferrals () {
  +return referrals;
  +}
  +
  +
  +/**
  + * How do we handle JNDI referrals? ignore, follow, or throw 
  + * (see javax.naming.Context.REFERRAL for more information).
  + */
  +public void setReferrals (String referrals) {
  +this.referrals = referrals;
  +}
  +
  +
  +/**
* Return the base element for user searches.
*/
   public String getUserBase() {
  @@ -1355,6 +1380,8 @@
   env.put(Context.SECURITY_AUTHENTICATION, authentication);
   if (protocol != null)
   env.put(Context.SECURITY_PROTOCOL, protocol);
  +if (referrals != null)
  +env.put(Context.REFERRAL, referrals);   
   
   context = new InitialDirContext(env);
   return (context);
  
  
  

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

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/realm JNDIRealm.java

[amyroh]

amyroh  2002/11/18 17:26:38

  Modified:catalina/src/share/org/apache/catalina/realm JNDIRealm.java
  Log:
  Add to configure how JNDI should handle referrals returned by the server.
  
  Submitted by Christopher Taylor <[EMAIL PROTECTED]>.
  
  Revision  ChangesPath
  1.10  +34 -5 
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java
  
  Index: JNDIRealm.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- JNDIRealm.java12 Nov 2002 01:13:37 -  1.9
  +++ JNDIRealm.java19 Nov 2002 01:26:38 -  1.10
  @@ -237,11 +237,21 @@
*/
   protected static final String name = "JNDIRealm";
   
  +
   /**
* The protocol that will be used in the communication with the directory 
server.
*/
   protected String protocol = null;
   
  +
  +/**
  + * How should we handle referrals?  Microsoft Active Directory can't handle 
  + * the default case, so an application authenticating against AD must 
  + * set referrals to "follow".
  + */
  +protected String referrals = null;
  +
  +
   /**
* The base element for user searches.
*/
  @@ -460,6 +470,23 @@
   
   
   /**
  + * Returns the current settings for handling JNDI referrals.
  + */
  +public String getReferrals () {
  +return referrals;
  +}
  +
  +
  +/**
  + * How do we handle JNDI referrals? ignore, follow, or throw 
  + * (see javax.naming.Context.REFERRAL for more information).
  + */
  +public void setReferrals (String referrals) {
  +this.referrals = referrals;
  +}
  +
  +
  +/**
* Return the base element for user searches.
*/
   public String getUserBase() {
  @@ -1345,7 +1372,9 @@
   if (authentication != null)
   env.put(Context.SECURITY_AUTHENTICATION, authentication);
   if (protocol != null)
  -env.put(Context.SECURITY_PROTOCOL, protocol);
  +env.put(Context.SECURITY_PROTOCOL, protocol);   
  +if (referrals != null)
  +env.put(Context.REFERRAL, referrals);   
   
   context = new InitialDirContext(env);
   return (context);
  
  
  

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

mod_jk2-2.0.43.dll does not support strings longer than aprox 4K - in a HTML text area for example

[brenron]

My first posting. I hope this is the proper place to report it.

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

DO NOT REPLY [Bug 14577] - comment mangles declaration

[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=14577

comment mangles declaration

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 00:53 ---
Fixed.

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

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

[kinman]

kinman  2002/11/18 16:51:05

  Modified:jasper2/src/share/org/apache/jasper/compiler Tag:
tomcat_4_branch Generator.java
  Log:
  - Fix 14577: Declarations should geneate a '\n' at end.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.35.2.12 +4 -3  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java
  
  Index: Generator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
  retrieving revision 1.35.2.11
  retrieving revision 1.35.2.12
  diff -u -r1.35.2.11 -r1.35.2.12
  --- Generator.java4 Nov 2002 21:24:42 -   1.35.2.11
  +++ Generator.java19 Nov 2002 00:51:05 -  1.35.2.12
  @@ -161,6 +161,7 @@
   
public void visit(Node.Declaration n) throws JasperException {
out.printMultiLn(new String(n.getText()));
  + out.println();
}
}
   
  
  
  

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

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

[kinman]

kinman  2002/11/18 16:49:42

  Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
  Log:
  - Fix 14577: Declarations should geneate a '\n' at end.
  
  Revision  ChangesPath
  1.128 +4 -3  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java
  
  Index: Generator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
  retrieving revision 1.127
  retrieving revision 1.128
  diff -u -r1.127 -r1.128
  --- Generator.java16 Nov 2002 04:20:10 -  1.127
  +++ Generator.java19 Nov 2002 00:49:42 -  1.128
  @@ -165,6 +165,7 @@
   
public void visit(Node.Declaration n) throws JasperException {
out.printMultiLn(new String(n.getText()));
  + out.println();
}
}
   
  
  
  

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

DO NOT REPLY [Bug 14583] - How to specify Classpath for the Tomcat NT Service ?

[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=14583

How to specify Classpath for the Tomcat NT Service ?

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 00:41 ---
You can ask tomcat user questions to [EMAIL PROTECTED]  Email
[EMAIL PROTECTED] to subscribe to the list.  Make sure
you read the guidelines at http://jakarta.apache.org/site/mail.html first.

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

DO NOT REPLY [Bug 14654] - Tags like doesn't 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=14654

Tags like  doesn't work !

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 00:40 ---
Unless an example is provided - this is invalid. Tomcat does provide XML syntax
support for JSP pages.

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

DO NOT REPLY [Bug 14660] New: - Unable to use custom tag when running applicaiton in war

[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=14660

Unable to use custom tag when running applicaiton in war

   Summary: Unable to use custom tag when running applicaiton in war
   Product: Tomcat 5
   Version: 5.0.0
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Jasper2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When the web application was running as a war file (unpacked), the JSPer 
through a exception of compiling the JSP. And the custom tags got error.  But 
the same applicaiton can be run when the webapplication unpacked.

the exception is :

java.lang.NullPointerException
at org.apache.jasper.compiler.SmapUtil.inputSmapPath(SmapUtil.java:163)
at org.apache.jasper.compiler.SmapUtil.generateSmap(SmapUtil.java:104)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:303)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:413)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext
.java:552)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:297)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2
95)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:194)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp
atcher.java:727)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD
ispatcher.java:616)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis
patcher.java:530)
at com.sun.j2ee.workflow.taglib.InsertTag.doEndTag(InsertTag.java:63)
at org.apache.jsp.template_jsp._jspx_meth_j2ee_insert_4(template_jsp.jav
a:198)
at org.apache.jsp.template_jsp._jspService(template_jsp.java:95)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:138)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:317)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2
95)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:194)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp
atcher.java:727)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationD
ispatcher.java:464)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDis
patcher.java:356)
at com.sun.j2ee.workflow.control.web.MainServlet.doGet(MainServlet.java:
127)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:194)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:276)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:996)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.RequestListenerValve.invoke(RequestListene
rValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
torBase.java:474)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.c

DO NOT REPLY [Bug 14658] - Bad exception handling in getWriter()

[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=14658

Bad exception handling in getWriter()





--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 00:03 ---
The legacy connector, org.apache.catalina.connector.http.HttpConnector, does not
exhibit this behavior. If I interrupt a stream from my browser, I see no
degratation in performance.

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

DO NOT REPLY [Bug 14658] - Bad exception handling in getWriter()

[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=14658

Bad exception handling in getWriter()





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 23:41 ---
Correction: I didn't actually need to cast it to a PrintWriter since getWriter()
already returns a PrintWriter. The issue of checkError() and bad performance
remain though.

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

DO NOT REPLY [Bug 14658] New: - Bad exception handling in getWriter()

[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=14658

Bad exception handling in getWriter()

   Summary: Bad exception handling in getWriter()
   Product: Tomcat 4
   Version: 4.1.12
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Connector:Coyote HTTP/1.1
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


getWriter() seems to be implemented as a PrintWriter. This means that all the
exceptions are eaten. This is due to the fact that PrintWriter does not forward
IOExceptions, but sets an internal variable called "trouble" to true. This
variable is supposed to be cheked with checkError() regularly, but here is is not.

This is bad in particular when writing a large document and the user closes his
browser connection. The servlet will keep writing unaware of the error, and
potentially thousands of exceptions will be caught silently. This can completely
kill a server if many connections are interrupted, because exception handling is
pretty slow.

I tried working around this by casting the Writer to a PrintWriter and calling
checkError() manually, but the PrintWriter is recycled which means that once an
error occurs, all subsequent requests fail.

To solve this, Tomcat should call checkError() and throw an exception or make it
so that the subsequent calls on the writer do not cause so many exceptions to be
thrown and eaten after the first exception is caught. I am fine if those
exceptions are eaten, but the performance hit is unacceptable (some of my
requests that usually complete in a few seconds take over 30 seconds to complete
in this exception-eating mode).

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

DO NOT REPLY [Bug 14654] New: - Tags like doesn't 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=14654

Tags like  doesn't work !

   Summary: Tags like  doesn't work !
   Product: Tomcat 4
   Version: 4.1.12
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Major
  Priority: Other
 Component: Unknown
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Hi,

If you try to use tags like   or  you will be 
get an error. Seams that Tomcat 4.1.12 doesn't recognize those tags, although 
required in JSP 1.2.

Daniel

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

setURLStreamHandlerFactory

[Joyson Gracer]

Hello,

I'm facing a problem while using a custom URL Handlers with Jakarta 
tomcat 4.0.4.

Can you please give some info about it.

Thanks

Joyson


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

Fwd: [PATCH] Fixes TagHandlerPool Size patch

[Torsten Fohrer]

false Maillinglist, ;-<

--  Forwarded Message  --

Subject: [PATCH] Fixes TagHandlerPool Size patch
Date: Monday 18 November 2002 20:43
From: [EMAIL PROTECTED] (Torsten Fohrer)
To: "Tomcat Users List" <[EMAIL PROTECTED]>

Adding Integer to String

Index: Generator.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/com
piler/Generator.java,v retrieving revision 1.127
diff -u -w -b -r1.127 Generator.java
--- Generator.java  16 Nov 2002 04:20:10 -  1.127
+++ Generator.java  18 Nov 2002 19:38:47 -
@@ -660,7 +660,7 @@
for (int i=0; imailto:[EMAIL PROTECTED]>
For additional commands, e-mail: 

---


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

cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/valves RequestListenerValve.java

[bobh]

bobh2002/11/18 10:38:12

  Modified:catalina/src/share/org/apache/catalina/valves
RequestListenerValve.java
  Log:
  - Servlet 2.4, section 10.6 talks about how to handle "Listener Exceptions."
It says a listener exception should cause the error page handling stuff
to be triggered.  This change does that.
  
  Revision  ChangesPath
  1.2   +13 -4 
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/valves/RequestListenerValve.java
  
  Index: RequestListenerValve.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/valves/RequestListenerValve.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- RequestListenerValve.java 9 Aug 2002 02:07:12 -   1.1
  +++ RequestListenerValve.java 18 Nov 2002 18:38:12 -  1.2
  @@ -67,8 +67,10 @@
   
   import java.io.IOException;
   import javax.servlet.ServletException;
  +import javax.servlet.ServletRequest;
   import javax.servlet.ServletRequestEvent;
   import javax.servlet.ServletRequestListener;
  +import org.apache.catalina.Globals;
   import org.apache.catalina.Logger;
   import org.apache.catalina.Request;
   import org.apache.catalina.Response;
  @@ -163,6 +165,10 @@
   } catch (Throwable t) {
   log(sm.getString("requestListenerValve.requestInit",
instances[i].getClass().getName()), t);
  +
  +ServletRequest sreq = request.getRequest();
  +sreq.setAttribute(Globals.EXCEPTION_ATTR,t);
  +return;
   }
   }
   
  @@ -182,6 +188,9 @@
   } catch (Throwable t) {
   log(sm.getString("requestListenerValve.requestDestroy",
instances[i].getClass().getName()), t);
  +
  +ServletRequest sreq = request.getRequest();
  +sreq.setAttribute(Globals.EXCEPTION_ATTR,t);
   }
   }
   
  
  
  

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

cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5 CoyoteRequest.java

[bobh]

bobh2002/11/18 10:36:05

  Modified:coyote/src/java/org/apache/coyote/tomcat5 CoyoteRequest.java
  Log:
  - Servlet 2.4, section 10.6 talks about how to handle "Listener Exceptions."
It says a listener exception should cause the error page handling stuff
to be triggered.  This change does that.
  
  Revision  ChangesPath
  1.7   +8 -6  
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteRequest.java
  
  Index: CoyoteRequest.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteRequest.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- CoyoteRequest.java18 Oct 2002 21:37:08 -  1.6
  +++ CoyoteRequest.java18 Nov 2002 18:36:05 -  1.7
  @@ -1167,8 +1167,9 @@
   try {
   listener.attributeRemoved(event);
   } catch (Throwable t) {
  -// FIXME - should we do anything besides log these?
   log(sm.getString("coyoteRequest.attributeEvent"), t);
  +// Error valve will pick this execption up and display it to user
  +attributes.put( Globals.EXCEPTION_ATTR, t );
   }
   }
   }
  @@ -1235,8 +1236,9 @@
   listener.attributeAdded(event);
   }
   } catch (Throwable t) {
  -// FIXME - should we do anything besides log these?
   log(sm.getString("coyoteRequest.attributeEvent"), t);
  +// Error valve will pick this execption up and display it to user
  +attributes.put( Globals.EXCEPTION_ATTR, t );
   }
   }
   }
  
  
  

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

DO NOT REPLY [Bug 14119] - MimeHeaders are allways encoded in UTF8

[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=14119

MimeHeaders are allways encoded in UTF8

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 18:32 ---
Your belief is incorrect. The definition of what can go in a header is, from
http://www.ietf.org/rfc/rfc2068.txt , section 4.2:
  field-content  = 

Where *TEXT is defined in section 2.2:
   "Words of *TEXT may contain characters from character sets other than ISO
   8859-1 [22] only when encoded according to the rules of RFC 1522."

An example of such an encoded piece of text is:
=?iso-8859-8?b?7eXs+SDv4SDp7Oj08A==?=

(there are no special characters there, the question marks are intended). Note
that it is self-describing with respect to its character encoding; it works this
way to allow stream handling of headers - you cannot use the character encoding
of the response body since this header might not have been read yet.

The other possible expansions of field-content are quoted strings (which are
quoted TEXT in the sense above) and token:
token  = 1*
CHAR   = 

In other words, *TEXT is the only expansion of field-content that allows non
US-ASCII characters, and those characters are ISO-8859-1 (not UTF-8, or the body
content charset)

If you wish to use international characters in headers, you need to supply code
to perform RFC1522 encoding, and note that you can't use such values in most
headers.

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

DO NOT REPLY [Bug 14645] New: - Connector does not support strings > 2K

[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=14645

Connector does not support strings > 2K

   Summary: Connector does not support strings > 2K
   Product: Tomcat 4
   Version: 4.0 Beta 1
  Platform: Other
OS/Version: Windows NT/2K
Status: NEW
  Severity: Blocker
  Priority: Other
 Component: Connector:Coyote JK 2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Apache 2.0.43
Tomcat 4.1.12
mod_jk2-2.0.43.dll
(all binaries from the Apache site)

When responding to a request sent to Apache (using the POST method) containing 
a parameter string longer than aproximately 2K bytes (an HTML text area for 
example), a blank page is returned. Strings less than 2K work fine. This 
precludes using JK2 for the majority of our applications.

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

DO NOT REPLY [Bug 14565] - Tomcat Server hangs and does not make entries in the database

[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=14565

Tomcat Server hangs and does not make entries in the database





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 17:30 ---
Could you tell me what is dbcp? Where do I find documentation for this? How do 
I get past this problem?

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

DO NOT REPLY [Bug 13969] - ':' in parameter breaks encodeURL() and encodeRedirectURL()

[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=13969

':' in parameter breaks encodeURL() and encodeRedirectURL()

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 16:43 ---
':' and '%' are reserved characters in the URL spec
(http://www.w3.org/Addressing/rfc1738.txt, see section 5). You need to URL
encoded them, or you'll get either a MalformedURLException or undefined behaviour.

It seems probably you've misunderstood the meaning of encodeURL(). This doesn't
URL-encode a string (yes it does sound similar :) ) It adds the session id if
you're using URL rewriting to maintain sessions. See
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/servletapi/javax/servlet/http/HttpServletResponse.html#encodeURL(java.lang.String)


The correct way to write your code would be:
 <%
response.sendRedirect(response.encodeRedirectURL("bug.jsp?ready="+java.net.URLEncoder.encode("Saturday
04:30"))); %>

this is JDK 1.3, in JDK 1.4, URLEncoder.encode(String) is deprecated and you
need to specify the charset for encoding:
<%
response.sendRedirect(response.encodeRedirectURL("bug.jsp?ready="+java.net.URLEncoder.encode("Saturday
04:30","UTF8"))); %>

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

DO NOT REPLY [Bug 13735] - Error code 302 in error-page XML tag prevents Authentication type FORM from working

[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=13735

Error code 302 in error-page XML tag prevents Authentication type FORM from working

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 16:31 ---
302 is not an 'error' as such - it is a temporary redirect, and is always sent
when you do a response.sendRedirect("blah") (which is what form based login does
internally). Is thus unsurprising that trying to catch 302s caused you a problem.

/All/ 1xx, 2xx, 3xx codes should be left well alone - they get interpreted by
the browser and don't show up as errors to the user. (For example - 304 results
in the page being served from the browser cache instead of from your server)
 
FYI, the codes which really /are/ errors worth handling are:
400, 401, 403, 404, 405, 411, 413, 415, 417, 500, 501, 503, 504

(theres more if you're using WebDAV, but even this set is excessive unless
you're proxying some requests)

Reading your comment '302 temporarily unavailable' it seems you may have
mistaken this for a 503 (Unavailable) code? See the servlet spec v2.3, section
2.3.3.2.

Hope this helps,
Baz

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

DO NOT REPLY [Bug 12184] - FORM based authentication / j_security_check not working

[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=12184

FORM based authentication / j_security_check not working

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|FORM based authentication / |FORM based authentication /
   |j_security_check not working|j_security_check not working



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 15:59 ---
First problem is duplicate of 
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9791
,and probably isn't a bug - see my explanation. Want to cc yourself in on that? 

This bug# can just track your second problem.

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

DO NOT REPLY [Bug 9590] - cookies stop sending to browser after nested loop

[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=9590

cookies stop sending to browser after nested loop





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 15:47 ---
Try testing if the response is committed before setting that last cookie,
eg <% if (response.isCommitted()) { System.err.println("train has left the
station"); } %>

If you'd managed to push 256 bytes of whitespace (for example) into the JSP
during that loop then you'll cause the response to commit, so you can no longer
set a 'Set-Cookie' header (or any other header). Also, because the second
addCookie is always adding the same thing, you might not be seeing the real
point that cookies fail, its more likely during the loop than afterwards - try
setting it to a counter instead. 

Finally, if the loop has > 19 iterations, the /browser/ will cause you a
problem. See
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/servletapi/javax/servlet/http/Cookie.html,
 - browsers only have to support 20 cookies per server. You'd have created 20
Set-Cookie headers and the browser would ignore the rest.

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

DO NOT REPLY [Bug 9791] - Form-based login fails using apache, mod_jk, mod_ssl without cookies

[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=9791

Form-based login fails using apache, mod_jk, mod_ssl without cookies





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 15:29 ---
Corey, I've checked through the code and the tomcat side looks fine. Are you
sure your login form is ok? For form based authentication without cookies, you
need to use URL rewriting on the form action in your login page, like so:



If you don't do this, then the session that created the login form will not be
requested when the login form is submitted. In particular, if you use a plain
.htm login form instead of a jsp, you /must/ use cookies.

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

DO NOT REPLY [Bug 10229] - Request parameters lost after authenticated through login page

[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=10229

Request parameters lost after authenticated through login page

[EMAIL PROTECTED] changed:

   What|Removed |Added

  Component|Catalina|Connector:Coyote HTTP/1.1
Version|4.0.3 Final |4.1.15



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 14:11 ---
This bug is a duplicate of http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2768 
but has been reintroduced with Coyote (possibly in multiple places - the same
bug is in the Tomcat 5 wrapper also). See setQueryString in
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java?rev=1.27&content-type=text/vnd.viewcvs-markup

NB there are a number of unimplemented HttpRequest methods in this class and so
there are likely to be more related bugs :(

juno, you might want to try a workaround of using the old Catalina Http 1.1
connector? It should not have this bug.

I've changed the version affected to the current 4.1 so this might get picked up
for the next release.

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

Personal Oracle9i and Tomcat 1.4

[RAamer]

Thanks Peter, I'm sure your diagnoses are correct. Would you mind guiding
me where in the script I need to hardcode? I mean the file and the
location? As a Tomcat newbie, I greatly appreciate your help.

Thanks

Rafi



 Oracle comes with it's own JDK and sets some environment variables.

 if you want both to coexist, hardcode the JDK in your catalina script. 
 when you uninstall, it reverts the environment settings and fixes your 
 tomcat problem.

 usually, that's the cause. 

 peter  








Hi guys,

I had my Tomcat running well until the day I installed Personal Oracle9i on
my machine. After that, I can not make Tomcat to run. When I try to start
it, the startup window opens for a fraction of a second and then closes
down without displaying any errors. There is nothing in the logs as well. I
deinstalled Oracle and it started working again. What's happening here?
Thanks

Rafi

PS: I installed Oracle without the HTTP server option.




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

Re: Personal Oracle9i and Tomcat 1.4

[peter lin]

Oracle comes with it's own JDK and sets some environment variables.

if you want both to coexist, hardcode the JDK in your catalina script.
when you uninstall, it reverts the environment settings and fixes your
tomcat problem.

usually, that's the cause.

peter


[EMAIL PROTECTED] wrote:
> 
> Hi guys,
> 
> I had my Tomcat running well until the day I installed Personal Oracle9i on
> my machine. After that, I can not make Tomcat to run. When I try to start
> it, the startup window opens for a fraction of a second and then closes
> down without displaying any errors. There is nothing in the logs as well. I
> deinstalled Oracle and it started working again. What's happening here?
> Thanks
> 
> Rafi
> 
> PS: I installed Oracle without the HTTP server option.
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 

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

DO NOT REPLY [Bug 11891] - JspC does not work for webapps

[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=11891

JspC does not work for webapps





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 12:48 ---
The patch attachment dated "09/03/03" along with Mark's notes from 10/18 worked
great with our application (334 jsp's, 8 or so directories).  

Previously we had two issues: if we compiled the whole app in one shot then we
had problems since we have files of the same name in different directories, but
if we compiled the application a directory at a time (setting the package
differently for each one) we had problems since we have one file that gets
included from different directories.

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

Personal Oracle9i and Tomcat 1.4

[RAamer]

Hi guys,

I had my Tomcat running well until the day I installed Personal Oracle9i on
my machine. After that, I can not make Tomcat to run. When I try to start
it, the startup window opens for a fraction of a second and then closes
down without displaying any errors. There is nothing in the logs as well. I
deinstalled Oracle and it started working again. What's happening here?
Thanks

Rafi

PS: I installed Oracle without the HTTP server option.



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

DO NOT REPLY [Bug 12299] - Setting cookie doesn't work in all cases.

[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=12299

Setting cookie doesn't work in all cases.

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 10:46 ---
Check the spec again: SRV 8.3, "The Include Method":
"It cannot set headers or call any method that affects
the headers of the response. Any attempt to do so must be ignored."

Setting cookies implies creating a 'Set-Cookie:' header, which you can't do in
an included jsp.

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

DO NOT REPLY [Bug 14635] New: - Should be possible not to have YYYY-MM-DD in log file names

[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=14635

Should be possible not to have -MM-DD in log file names

   Summary: Should be possible not to have -MM-DD in log file
names
   Product: Tomcat 4
   Version: 4.1.12
  Platform: All
OS/Version: All
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


There should be a configuration parameter to make 
org.apache.catalina.logger.FileLogger 
not add
-MM-DD to the file names it creates, and not
create a new log file for every 
day.

This would make it cooperate better with logrotate
on linux systems.

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