Tomcat 3.3 & mod_jk2

[David Cassidy]

Has anyone managed to get tomcat 3.3.1a to work with mod_jk2
and if so how ?

Thanks

David



--

This e-mail may contain confidential and/or privileged information. If you are not the 
intended recipient (or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail. Any unauthorized copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden.



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

DO NOT REPLY [Bug 20314] - Wrapped request object not the same when forwarding to a web resource in a filter

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

Wrapped request object not the same when forwarding to a web resource in a filter

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 12:12 ---
Per http://marc.theaimsgroup.com/?l=tomcat-dev&m=105419767921921&w=2

The spec contradicts itself with regard to this behavior. The link above has
better detail.

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

DO NOT REPLY [Bug 11366] - Handling of Wrapped Responses

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

Handling of Wrapped Responses

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 12:10 ---
Per .. http://marc.theaimsgroup.com/?l=tomcat-dev&m=105419767921921&w=2

This was probbaly fixed in the later 4.1 versions.

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

DO NOT REPLY [Bug 8566] - Filter using ServletRequestWrapper breaks RequestDispatcher.forward

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

Filter using ServletRequestWrapper breaks RequestDispatcher.forward

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 12:07 ---
*** Bug 9754 has been marked as a duplicate of this bug. ***

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

DO NOT REPLY [Bug 9754] - Request and response wrappers behavior

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

Request and response wrappers behavior

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 12:07 ---
dup per .. http://marc.theaimsgroup.com/?l=tomcat-dev&m=105419767921921&w=2

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

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

DO NOT REPLY [Bug 16032] - Not all attributes get copied when the request is forwarded

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

Not all attributes get copied when the request is forwarded

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 12:06 ---
This is probably fixed in the later 4.1.X versions.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16032

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

DO NOT REPLY [Bug 11335] - RequestDispatcher.forward() is not 2.3 spec compliant

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

RequestDispatcher.forward() is not 2.3 spec compliant

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 12:04 ---
This is probably fixed in 4.1

http://marc.theaimsgroup.com/?l=tomcat-dev&m=105419767921921&w=2

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

[GUMP] Build timed out - jk

[Craig McClanahan]

This email is autogenerated from the output from:



Buildfile: build.xml

init:
 [echo] /home/rubys
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk
 [echo] linux=true solaris=${solaris} win32=${win32} hpux=${hpux} 
netware=${netware}

apache20:

apache13:

iis:

netscape:

jni:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk/jni
   [so] Compiling 4 out of 4
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native/common/jk_map.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native/common/jk_pool.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native/common/jk_util.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native/jni/jk_jnicb.c
Linking /home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk/jni/jni_connect.so
/home/rubys/bin/timeout: timed out

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

Re: Class org.apache.naming.factory.MailSessionFactory and authentication

[Glenn Nielsen]

Patches are welcome.

If you create one please submit an enhancement request in bugzilla then attache
the patch.
Thanks,

Glenn

Thomas Raehalme wrote:
Hi,

I have been wondering about user authentication when sending e-mail 
messages using JavaMail (and SMTP). Tomcat provides pre-configured 
javax.mail.Session objects through JNDI, but does it provide means to 
specify authentication settings in the server?

I have been searching through the documentation and mailing list 
archives for information on how to provide authentication information in 
the server settings, but so far haven't found anything. I also noticed 
other messages asking similar questions.

If this issue hasn't been previously considered, maybe it would be a 
good idea to make the class org.apache.naming.factory.MailSessionFactory 
provide an Authenticator for the Session.getInstance method? The 
Authenticator implementation would get the necessary authentication 
information from the server configuration.

Naturally I volunteer to provide the basic implementation if necessary.

Best regards,
Thomas
---
Thomas Raehalme [EMAIL PROTECTED]
tuotekehitysjohtaja gsm  040 545 0605
Artamir Innovations Ltd.puh. 09 2517 5970
Tekniikantie 14, Innopoli IIfax  09 2517 5979
02150 Espoo http://www.artamir.com
---
Julkinen PGP-avain haettavissa osoitteesta http://www.keyserver.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


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

DO NOT REPLY [Bug 20307] - Setting content length causes Tomcat to ignore response status

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

Setting content length causes Tomcat to ignore response status

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 10:17 ---
It took me about 15 minutes to figure out what was going on.

The response is considered committed as soon as the amount of bytes specified in
the content length has been written. Since the content length is 0, the response
is considered committed as soon you call response.setContentLength(0). Since you
can't change the status after the response has been committed, that's why you
get a 200 status back.

This spec seems a bit weird in that case.

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

DO NOT REPLY [Bug 20330] - sendError does not set HTTP status 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=20330

sendError does not set HTTP status code

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 09:33 ---
For the content-type to work, you have to declare a mime mapping for *.shtml.
For the status code, this is a duplicate, which likely won't be fixed in Tomcat
4.1.x.

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

DO NOT REPLY [Bug 20351] - jasper failed to compile jsp's

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

jasper failed to compile jsp's

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 09:31 ---
This is a duplicate of many other bugs. To summarize, this cannot be made
foolproof, and thanks to Sun's unwillingness to proporly expose the Java
compiler, or interact with the Windows registry in a predictable fashion, the
installer cannot always find what it needs (thankfully, it works most of the time).

As a workaround, copy tools.jar to common/lib.

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

DO NOT REPLY [Bug 20351] New: - jasper failed to compile jsp's

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

jasper failed to compile jsp's

   Summary: jasper failed to compile jsp's
   Product: Tomcat 4
   Version: 4.1.24
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Jasper was not able to compile ANY jsp page after i installed tomcat as a "NT" 
service. After that I started up tomcat as console process which fixed the 
problem. After inspecting the tomcat server error log i discovered that jasper 
actually makes a native call to java.exe windows which failed. 

The logs are not clear as to WHY the call failed. For my next effort I tried 
the hit-the-enemy-in-the-dark method by assuming that createprocess could not 
locate the java.exe (what usually happens) file by appending java's bin path 
to my environment. But the bug persisted, and culminated in this very same bug-
report. 


Here is the log:

Created catalinaLoader in: d:\tomcat4\server\lib
May 30, 2003 10:42:29 AM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
May 30, 2003 10:42:29 AM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
May 30, 2003 10:42:30 AM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
May 30, 2003 10:42:31 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8081
May 30, 2003 10:42:36 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8081
May 30, 2003 10:42:36 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
May 30, 2003 10:42:36 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=31/78  config=d:\tomcat4\conf\jk2.properties
Error running javac.exe compiler
at 
org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.executeExternalC
ompile(DefaultCompilerAdapter.java:455)
at org.apache.tools.ant.taskdefs.compilers.JavacExternal.execute
(JavacExternal.java:81)
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:840)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:317)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
at org.apache.jasper.JspCompilationContext.compile
(JspCompilationContext.java:473)
at org.apache.jasper.servlet.JspServletWrapper.service
(JspServletWrapper.java:190)
at org.apache.jasper.servlet.JspServlet.serviceJspFile
(JspServlet.java:295)
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
(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:256)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe
xt(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe
xt(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2415)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:180)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe
xt(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:171)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe
xt(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:172)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe
xt(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.Contai

DO NOT REPLY [Bug 20346] - jasper generate invalid package name

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

jasper generate invalid package name





--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 03:31 ---
*** Bug 20347 has been marked as a duplicate of this bug. ***

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

DO NOT REPLY [Bug 20347] - jasper generate invalid package name

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

jasper generate invalid package name

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2003-05-30 03:31 ---


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

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

DO NOT REPLY [Bug 20347] New: - jasper generate invalid package name

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

jasper generate invalid package name

   Summary: jasper generate invalid package name
   Product: Tomcat 4
   Version: 4.1.24
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Jasper 2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


jasper generate invalid package name for 'template_resource/02/1.jsp' 
like 'package jsp.foresee.template_resource.02', java name '_1_jsp.java' is OK.

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

DO NOT REPLY [Bug 20346] New: - jasper generate invalid package name

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

jasper generate invalid package name

   Summary: jasper generate invalid package name
   Product: Tomcat 4
   Version: 4.1.24
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Jasper 2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


jasper generate invalid package name for 'template_resource/1.jsp' 
like 'package jsp.foresee.template_resource.02', java name '_1_jsp.java' is OK.

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

DO NOT REPLY [Bug 16688] - JSP's not compiling

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

JSP's not compiling

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |
Version|4.1.19  |4.1.24



--- Additional Comments From [EMAIL PROTECTED]  2003-05-29 22:29 ---
The Bug is still there. I have the same Problem.
Here is my Testcase:
1. I made a clean W2k Server install. (VMware rulez)
2. I installed SP3 (SP2 is needed for the new Sun SDK)
3. I installed j2sdk-1_4_1_02-windows-i586.exe with the default settings.
4. I installed jakarta-tomcat-4.1.24-LE-jdk14.exe, default settings,
   but NT Service checked.
5. I opened the shortcut "Tomcat Administration" -> same Error as stated by
   Steve Vanspall
6. I stopped the NT service and opened the shortcut "Start Tomcat" 
   -> opened "Tomcat Administration"
   -> everything is working fine.

I have the same wrong entry in 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Apache Tomcat 4.1
\Parameters\JVM Library as stated by Steve Fyfe. After I fixed it the tomcat 
service is working.

BTW. After my installation i have three jvm.dll on my system:
Two with the same size in:
C:\j2sdk1.4.1_02\jre\bin\client  and
C:\Program Files\Java\j2re1.4.1_02\bin\client
and one bigger in:
C:\j2sdk1.4.1_02\jre\bin\server

I think tomcat needs the server one.

I have not found where the wrong registry value for the service is set in 
tomcat.nsi so could someone give me a hint?

kind regards
Daniel

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

Class org.apache.naming.factory.MailSessionFactory and authentication

[Richard Backhouse]

Return Receipt
   
Your  Class org.apache.naming.factory.MailSessionFactory and   
document  authentication   
:  
   
was   Richard Backhouse/Durham/IBM 
received   
by:
   
at:   05/29/2003 14:47:18 EDT  
   





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

Class org.apache.naming.factory.MailSessionFactory and authentication

[Thomas Raehalme]

Hi,

I have been wondering about user authentication when sending e-mail 
messages using JavaMail (and SMTP). Tomcat provides pre-configured 
javax.mail.Session objects through JNDI, but does it provide means to 
specify authentication settings in the server?

I have been searching through the documentation and mailing list 
archives for information on how to provide authentication information in 
the server settings, but so far haven't found anything. I also noticed 
other messages asking similar questions.

If this issue hasn't been previously considered, maybe it would be a 
good idea to make the class org.apache.naming.factory.MailSessionFactory 
provide an Authenticator for the Session.getInstance method? The 
Authenticator implementation would get the necessary authentication 
information from the server configuration.

Naturally I volunteer to provide the basic implementation if necessary.

Best regards,
Thomas
---
Thomas Raehalme [EMAIL PROTECTED]
tuotekehitysjohtaja gsm  040 545 0605
Artamir Innovations Ltd.puh. 09 2517 5970
Tekniikantie 14, Innopoli IIfax  09 2517 5979
02150 Espoo http://www.artamir.com
---
Julkinen PGP-avain haettavissa osoitteesta http://www.keyserver.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 20330] New: - sendError does not set HTTP status 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=20330

sendError does not set HTTP status code

   Summary: sendError does not set HTTP status code
   Product: Tomcat 4
   Version: 4.1.18
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Servlet & JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I am running Tomcat 4.1.18 under JBOSS ... I am connecting to Tomcat directly 
(no mod_jk) ... I have an error page configured in my web.xml as follows:


500
/500.shtml


When I add the following to my servlet:

res.sendError(HttpServletResponse.SC_INTERNAL_SERVER_ERROR);

the error page is returned, but the HTTP status and Content-type are incorrect. 
I used ethereal to sniff the response and see this:

HTTP/1.1 200 OK\r\n
ETag: W/"853-1051564868000"\r\n
Last-Modified: Mon, 28 Apr 2003 21:21:08 GMT\r\n
Content-Type: text/plain\r\n
Content-Length: 853\r\n
Date: Thu, 29 May 2003 16:45:53 GMT\r\n
Server: Apache Coyote/1.0\r\n

So why isn't the sendError causing the response status to be 500 and the 
Content-type set to text/html?

The ultimate result of this problem is that my error document renders as plain 
text in Netscape ... IE ignores the Content-type header and renders it as 
HTML ...

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

cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup Embedded.java

[luehe]

luehe   2003/05/29 09:59:36

  Modified:catalina/src/share/org/apache/catalina/startup Embedded.java
  Log:
  Have all contexts inherit Embedded's logger, as mentioned in
  Embedded's constructor:
  
* @param logger Logger implementation to be inherited by all components
*  (unless overridden further down the container hierarchy)
  
  This fixes Bugtraq 4866227 ("Nothing is written to the server.log file
  when calling ServletContext.log")
  
  Revision  ChangesPath
  1.7   +2 -1  
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/Embedded.java
  
  Index: Embedded.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/Embedded.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- Embedded.java 20 Mar 2003 23:36:13 -  1.6
  +++ Embedded.java 29 May 2003 16:59:35 -  1.7
  @@ -621,6 +621,7 @@
   context.setDebug(debug);
   context.setDocBase(docBase);
   context.setPath(path);
  + context.setLogger(logger);
   
   ContextConfig config = new ContextConfig();
   config.setDebug(debug);
  
  
  

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

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/coreStandardContext.java

[Remy Maucherat]

Jean-Francois Arcand wrote:
Bonne nouvelle :-)

The problem right now is we ends up with 2 configuration files. If I 
have under webapps/ a file named test.xml that contains:



that always work. But if the path is equals to:



that will not work (even with my tentative patch). We will ends up with 
2 configurations file (test.xml and test2.xml) and the admin 
tool/HostDeployer will always use webapp/test.xml
According to the consensus, the context files will go in 
conf/[enginename]/[hostname]/

I'll try to be careful during the refactoring (which will not be done by 
today, sorry), and I'll try to make the deployer less dumb ;-)

Remy

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

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

[remm]

remm2003/05/29 09:34:38

  Modified:jasper2/src/share/org/apache/jasper/compiler
JspRuntimeContext.java
  Log:
  - Only do the security init if there's a security manager.
  
  Revision  ChangesPath
  1.14  +7 -5  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspRuntimeContext.java
  
  Index: JspRuntimeContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspRuntimeContext.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- JspRuntimeContext.java15 May 2003 18:45:40 -  1.13
  +++ JspRuntimeContext.java29 May 2003 16:34:37 -  1.14
  @@ -191,7 +191,9 @@
return;
}
   
  -initSecurity();
  +if (System.getSecurityManager() != null) {
  +initSecurity();
  +}
   
   // If this web application context is running from a
   // directory, start the background compilation thread
  
  
  

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

cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/naming LocalStrings.properties LocalStrings_fr.properties NamingContext.java

[remm]

remm2003/05/29 09:19:54

  Modified:catalina/src/share/org/apache/naming LocalStrings.properties
LocalStrings_fr.properties NamingContext.java
  Log:
  - Add logging of unexpected exceptions occuring during reference resolution.
  
  Revision  ChangesPath
  1.2   +1 -0  
jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/LocalStrings.properties
  
  Index: LocalStrings.properties
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/LocalStrings.properties,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- LocalStrings.properties   18 Jul 2002 16:47:31 -  1.1
  +++ LocalStrings.properties   29 May 2003 16:19:53 -  1.2
  @@ -3,6 +3,7 @@
   contextBindings.noContextBoundToCL=No naming context bound to this class loader
   selectorContext.noJavaUrl=This context must be accessed throught a java: URL
   namingContext.contextExpected=Name is not bound to a Context
  +namingContext.failResolvingReference=Unexpected exception resolving reference
   namingContext.nameNotBound=Name {0} is not bound in this Context
   namingContext.readOnly=Context is read only
   namingContext.invalidName=Name is not valid
  
  
  
  1.2   +1 -0  
jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/LocalStrings_fr.properties
  
  Index: LocalStrings_fr.properties
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/LocalStrings_fr.properties,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- LocalStrings_fr.properties5 Nov 2002 09:35:48 -   1.1
  +++ LocalStrings_fr.properties29 May 2003 16:19:53 -  1.2
  @@ -3,6 +3,7 @@
   contextBindings.noContextBoundToCL=Aucun Contexte de nommage lié à ce chargeur de 
classes
   selectorContext.noJavaUrl=Ce Contexte doit être accédé par une java: URL
   namingContext.contextExpected=Le Nom n''est pas lié à un Contexte
  +namingContext.failResolvingReference=Une erreur s est produite durant la résolution 
de la référence
   namingContext.nameNotBound=Le Nom {0} n''est pas lié à ce Contexte
   namingContext.readOnly=Le Contexte est en lecture seule
   namingContext.invalidName=Le Nom est invalide
  
  
  
  1.2   +10 -5 
jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/NamingContext.java
  
  Index: NamingContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/NamingContext.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- NamingContext.java18 Jul 2002 16:47:31 -  1.1
  +++ NamingContext.java29 May 2003 16:19:53 -  1.2
  @@ -87,7 +87,6 @@
* @author Remy Maucherat
* @version $Revision$ $Date$
*/
  -
   public class NamingContext implements Context {
   
   
  @@ -100,6 +99,10 @@
   protected static final NameParser nameParser = new NameParserImpl();
   
   
  +private static org.apache.commons.logging.Log log =
  +org.apache.commons.logging.LogFactory.getLog(NamingContext.class);
  +
  +
   // --- Constructors
   
   
  @@ -841,6 +844,8 @@
   } catch (NamingException e) {
   throw e;
   } catch (Exception e) {
  +log.warn(sm.getString
  + ("namingContext.failResolvingReference"), e);
   throw new NamingException(e.getMessage());
   }
   } else {
  
  
  

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

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/coreStandardContext.java

[Jean-Francois Arcand]

Remy Maucherat wrote:

[EMAIL PROTECTED] wrote:

jfarcand2003/05/28 21:13:24

  Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
  Log:
  Revert back my latest changes since it did not fix the problem 
completely.


Don't worry about that IMO. I'll have to rewrite that code for the 
deployer refactoring I'll do (today).
I hope I'll be done in one day :)
Bonne nouvelle :-)

The problem right now is we ends up with 2 configuration files. If I 
have under webapps/ a file named test.xml that contains:



that always work. But if the path is equals to:



that will not work (even with my tentative patch). We will ends up with 
2 configurations file (test.xml and test2.xml) and the admin 
tool/HostDeployer will always use webapp/test.xml

-- Jeanfrancois






Remy

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



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