DO NOT REPLY [Bug 24085] New: - [Administration] The group and role list disappear! When "Create New User", "save" directly without filling in form.

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

[Administration] The group and role list disappear! When "Create New User", "save" 
directly without filling in form.

   Summary: [Administration] The group and role list disappear! When
"Create New User", "save" directly without filling in
form.
   Product: Tomcat 5
   Version: 5.0.12
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Webapps:Administration
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Hi, 
   In the "Create New User" page, click the "save" button directly without 
filling the form. Then there will be a validate error, return to this page 
agian. But the "Group" and "Role" list disappear! Why?
   This error also exists in the "Edit a Exited User" and "Create New Group".

Good Luck!

tigerlet.

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

Re: New to dev list

[Bob Herrmann]

On Thu, 2003-10-23 at 11:37, [EMAIL PROTECTED] wrote:
> Thanks, Bob. The presentation is good. Does Tomcat have design document? So I can 
> dig deeper to source code level.

I don't believe that it does.   This does seem to be a deficiency.  The
phrase "Use the Source Luke", springs to mind...  You can also peruse
the "documentation" section of the Tomcat site and pick up some things.

http://jakarta.apache.org/tomcat/

Perhaps a simple description of how Tomcat gets up and going will help.

The highly abridged version of things goes like this;

1. Some one starts the JavaVM with a bunch of options (usually via the
"startup" script.)

2. A bootstrap thing starts figuring out where things are and loading
some initial classes

3. The bootstrapper uses  the "Digester" to 'execute' the server.xml and
web.xml files.What is important to understand here is; Tomcat is a
collection of interfaces with some handy "Standard implementations." 
When the default server.xml is used, a bunch of 'Standard
implementations' are wired together and started (using some Lifecycle
interfaces to ensure everything starts in the right order.)   

So basically, Tomcat is a loose connection of components that implement
interfaces for "Connections to the Network, Session handling, Logging,
Valves, etc.."  You can implement your own versions or use the standard
versions.  To use your own, you only need to put the classes in the
"server/classes" directory and modify the server.xml to use your own
implementation.

Thus understanding how Tomcat works is broken down into understanding
the individual pieces and their interfaces (or contracts) 

Hopefully this helps.

Cheers,
-bob

> 
> > 
> > From: Bob Herrmann <[EMAIL PROTECTED]>
> > Date: 2003/10/23 Thu AM 01:18:12 EDT
> > To: Tomcat Developers List <[EMAIL PROTECTED]>
> > Subject: Re: new to dev list
> > 
> > Jamesmyang3 writes:
> > > I am new to this development list. I download tomcat source
> > > code and try to compile and run it. Can anyone provide me
> > > some information on how Tomcat is designed? 
> > 
> > The best I could ever find is a PDF of a presentation that
> > Craig McClanahan made back in June of 2000.  Look for "Tomcat Servlet"
> > in this page;
> > 
> > http://servlet.java.sun.com/javaone/conf/bofs/1290/google-sf2001.jsp
> > 
> > The pdf is free, but they seem to want to charge for the audio.
> > 
> > Cheers,
> > -bob
> > 
> > 
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 1
> 
> 
> -
> 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]

[Patch] BaseDirContextTestCase depcrecated junit methods

[Jeff Tulley]

Since assert is a reserved keyword, and is now part of the language,
junit moved away from using it for test assertions, opting instead for
things like assertTrue or assertEquals

Here is the patch for BaseDirContextTestCase, to bring it up to par with
junit's and Java's recommended practices.

Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
Index: BaseDirContextTestCase.java
===
RCS file: 
/home/cvspublic/jakarta-tomcat-4.0/catalina/src/test/org/apache/naming/resources/BaseDirContextTestCase.java,v
retrieving revision 1.3
diff -u -r1.3 BaseDirContextTestCase.java
--- BaseDirContextTestCase.java 21 Oct 2001 22:03:34 -  1.3
+++ BaseDirContextTestCase.java 23 Oct 2003 22:16:03 -
@@ -247,7 +247,7 @@
 // Look up the WEB-INF entry
 Object webInfEntry = context.lookup("WEB-INF");
 assertNotNull("Found WEB-INF entry", webInfEntry);
-assert("WEB-INF entry is a DirContext",
+assertTrue("WEB-INF entry is a DirContext",
webInfEntry instanceof DirContext);
 DirContext webInfContext = (DirContext) webInfEntry;
 
@@ -303,7 +303,7 @@
 // Look up the WEB-INF entry
 Object webInfEntry = context.lookup("WEB-INF");
 assertNotNull("Found WEB-INF entry", webInfEntry);
-assert("WEB-INF entry is a DirContext",
+assertTrue("WEB-INF entry is a DirContext",
webInfEntry instanceof DirContext);
 DirContext webInfContext = (DirContext) webInfEntry;
 
@@ -353,20 +353,20 @@
 while (ne.hasMore()) {
 
 Object next = ne.next();
-assert("list() returns NameClassPair instances",
+assertTrue("list() returns NameClassPair instances",
next instanceof NameClassPair);
 NameClassPair ncp = (NameClassPair) next;
 
-assert("Name '" + ncp.getName() + "' is expected",
+assertTrue("Name '" + ncp.getName() + "' is expected",
isListed(ncp.getName(), list));
 
 if (isDirContext(ncp.getName())) {
-assert("Class '" + ncp.getClassName() + "' is '" +
+assertTrue("Class '" + ncp.getClassName() + "' is '" +
contextClassName + "'",
contextClassName.equals(ncp.getClassName()));
 }
 
-assert("Relative is 'true'", ncp.isRelative());
+assertTrue("Relative is 'true'", ncp.isRelative());
 
 }
 
@@ -391,29 +391,29 @@
 while (ne.hasMore()) {
 
 Object next = ne.next();
-assert("listBindings() returns Binding instances",
+assertTrue("listBindings() returns Binding instances",
next instanceof Binding);
 Binding b = (Binding) next;
 
-assert("Name '" + b.getName() + "' is expected",
+assertTrue("Name '" + b.getName() + "' is expected",
isListed(b.getName(), list));
 
 if (isDirContext(b.getName())) {
-assert("Class '" + b.getClassName() + "' is '" +
+assertTrue("Class '" + b.getClassName() + "' is '" +
contextClassName + "'",
contextClassName.equals(b.getClassName()));
 }
 
-assert("Relative is 'true'", b.isRelative());
+assertTrue("Relative is 'true'", b.isRelative());
 
 Object object = b.getObject();
 assertNotNull("Name '" + b.getName() + "' has a non-null object",
   object);
 if (b.getName().equals("web.xml")) {
-assert("Entry '" + b.getName() + "' is a Resource",
+assertTrue("Entry '" + b.getName() + "' is a Resource",
object instanceof Resource);
 } else {
-assert("Entry '" + b.getName() + "' is a DirContext",
+assertTrue("Entry '" + b.getName() + "' is a DirContext",
object instanceof DirContext);
 }
 
@@ -445,35 +445,35 @@
 while (ne.hasMore()) {
 
 Object next = ne.next();
-assert("getAll() returns Attribute instances",
+assertTrue("getAll() returns Attribute instances",
next instanceof Attribute);
 Attribute attr = (Attribute) next;
 String name = attr.getID();
 int index = getIndex(name, webInfAttrs);
-assert("WEB-INF attribute '" + name + "' is expected",
+assertTrue("WEB-INF attribute '" + name + "' is expected",
index >= 0);
 Object value = attr.get();
 assertNotNull("get() returned non-null", value);
 
 if (name.equals("creationdate")) {
-ass

DO NOT REPLY [Bug 24075] New: - mod_jk will not resolve hostnames

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

mod_jk will not resolve hostnames

   Summary: mod_jk will not resolve hostnames
   Product: Tomcat 4
   Version: 4.1.24
  Platform: Sun
OS/Version: Solaris
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Connector:JK/AJP (deprecated)
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I just installed mod_jk on apache 2.0.47 and was unable to connect to tomcat. I
knew tomcat was configured correctly because I had an older apache 1.3
distribution with mod_jk on the same machine connecting to the same tomcat with
no problems. After some debugging and code fiddeling, I found out that my
hostname of "localhost" wasn't getting resolved. When I put in 127.0.0.1
instead, it worked fine.

I know this module is deprecated, but I hope this will help others with this
connector.

-Josh

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

Re: http://www.apache.org/dist/jakarta/tomcat-4/source/

[Bill Barker]

Remy has been packaging Jasper in the j-t-4.1.x-src tarball (as "jasper").

- Original Message -
From: "jean-frederic clere" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 23, 2003 8:52 AM
Subject: http://www.apache.org/dist/jakarta/tomcat-4/source/


> Hi,
>
> I am "playing" building binaries of Tomcat:
> In http://www.apache.org/dist/jakarta/tomcat-4/source/ we only have
> jakarta-tomcat and jakarta-tomcat-connectors.
> I think we should add jakarta-tomcat-jasper/jasper2 and
jakarta-servletapi-4
> otherwise it is quite hard to rebuild a binary from the sources.
>
> Comments?
>
> Cheers
>
> Jean-Frederic
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication in 
error, please notify us immediately by e-mail and then delete all copies of this 
message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the 
Internet is not secure. Do not send confidential or sensitive information, such as 
social security numbers, account numbers, personal identification numbers and 
passwords, to us via ordinary (unencrypted) e-mail.

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

DO NOT REPLY [Bug 24073] New: - hang/deadlock, possibly in FileLogger

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

hang/deadlock, possibly in FileLogger

   Summary: hang/deadlock, possibly in FileLogger
   Product: Tomcat 4
   Version: 4.1.27
  Platform: PC
   URL: http://www.nap.edu/building/catalina_hang_trace.txt
OS/Version: Linux
Status: NEW
  Severity: Major
  Priority: Other
 Component: Catalina:Modules
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Based on some Googling this may be a JDK/JRE problem, rather than a
Catalina-specific issue, but since I'm not real sure how to read Java thread
dumps in the first place I figure I'll check here first.

We've had a recurring hang on our standalone 4.1.24 and 4.1.27 installations
(the binary distributions thereof), using Sun's 1.4.2 JDK.  The server will sit
quietly for a few days, handling no requests except our local monitoring
software's periodic "GET /" every ten minutes or so.  Once every day or three,
it'll wedge hard, and requests to the 8080 socket time out.  Nothing shows up in
logs (with every debug parameter I could find set to 99), and it takes a kill -9
to bring it down.  Unfortunately, I can't seem to produce a system state that'll
instantly reproduce the problem, so I just have to sit around and wait for a
couple of days before it crops up again. :/

I tossed a -QUIT at the most recent occurence on a 4.1.27 install, and the thing
my (very inexpert) eye immediately sees is the interaction between threads 23
and 18 and the locking on the FileWriter (0x456997c8), which doesn't seem to
crop up if I dump threads on a normally functioning server.

I'll put the full thread dump in that little URL box up there, in case that's
more helpful than what I've pasted.

"Thread-23" daemon prio=1 tid=0x0885f958 nid=0x84f waiting for monitor entry
[4f26a000..4f26a714]
at java.io.PrintWriter.println(PrintWriter.java:515)
- waiting to lock <0x456997c8> (a java.io.FileWriter)
at org.apache.catalina.logger.FileLogger.log(FileLogger.java:293)
at org.apache.catalina.core.ContainerBase.log(ContainerBase.java:1418)
at
org.apache.catalina.core.StandardEngineMapper.map(StandardEngineMapper.java:193)
at org.apache.catalina.core.ContainerBase.map(ContainerBase.java:1016)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:534)

"Thread-18" daemon prio=1 tid=0x0872be00 nid=0x84f waiting on condition
[4efe5000..4efe5714]
at java.io.Writer.write(Writer.java:126)
at java.io.PrintWriter.newLine(PrintWriter.java:254)
- locked <0x456997c8> (a java.io.FileWriter)
at java.io.PrintWriter.println(PrintWriter.java:405)
at java.io.PrintWriter.println(PrintWriter.java:516)
- locked <0x456997c8> (a java.io.FileWriter)
at org.apache.catalina.logger.FileLogger.log(FileLogger.java:293)
at org.apache.catalina.core.ContainerBase.log(ContainerBase.java:1418)
at
org.apache.catalina.core.StandardEngineMapper.map(StandardEngineMapper.java:221)
at org.apache.catalina.core.ContainerBase.map(ContainerBase.java:1016)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(Pool

Re: no main in Embedded.java

[Mark W. Webb]

Forgive me if I am sounding like a complete idiot.  But are you saying 
that I should use the JMX API in order to launch tomcat?  After looking 
at some of the MX4J example code, this is the case.  But I am not sure 
what class I should call from the JMX code in order to get Tomcat to 
start.  I will keep digging, but any help you could offer, or 
documentation I could reference would be greatly appreciated.

thank you very much

Remy Maucherat wrote:

Mark W. Webb wrote:

My main motivation for this is that I am looking for a way to start 
embedded Tomcat from within a C program using the Invocation API.  
What would be the new entry point class that I should look?  Whatever 
this class is, its the one that I want to call from my C program.


That method was the equivalent of server.xml. So the idea is that you 
should code it yourself according to your needs.

If you're upgrading to something different, I would rather create an 
embedded Tomcat through either Ant or directly JMX.

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]

cvs commit: jakarta-tomcat-5 build.properties.default

[remm]

remm2003/10/23 10:33:32

  Modified:.build.properties.default
  Log:
  - Upgrade to new DBCP and pool.
  
  Revision  ChangesPath
  1.110 +9 -9  jakarta-tomcat-5/build.properties.default
  
  Index: build.properties.default
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/build.properties.default,v
  retrieving revision 1.109
  retrieving revision 1.110
  diff -u -r1.109 -r1.110
  --- build.properties.default  29 Sep 2003 10:27:40 -  1.109
  +++ build.properties.default  23 Oct 2003 17:33:32 -  1.110
  @@ -142,11 +142,11 @@
   
log4j.loc=http://archive.apache.org/dist/jakarta/log4j/binaries/jakarta-log4j-1.2.8.tar.gz
   
   
  -# - Commons DBCP, version 1.0 or later -
  -commons-dbcp.home=${base.path}/commons-dbcp-1.0
  +# - Commons DBCP, version 1.1 or later -
  +commons-dbcp.home=${base.path}/commons-dbcp-1.1
   commons-dbcp.lib=${commons-dbcp.home}
  -commons-dbcp.jar=${commons-dbcp.lib}/commons-dbcp.jar
  
-commons-dbcp.loc=http://archive.apache.org/dist/jakarta/commons/dbcp/binaries/commons-dbcp-1.0.tar.gz
  +commons-dbcp.jar=${commons-dbcp.lib}/commons-dbcp-1.1.jar
  
+commons-dbcp.loc=http://archive.apache.org/dist/jakarta/commons/dbcp/binaries/commons-dbcp-1.1.tar.gz
   
   
   # - Commons HttpClient, version 2.0 or later -
  @@ -156,11 +156,11 @@
   
commons-httpclient.loc=http://archive.apache.org/dist/jakarta/commons/httpclient/binary/commons-httpclient-2.0-rc1.tar.gz
   
   
  -# - Commons Pool, version 1.0.1 or later -
  -commons-pool.home=${base.path}/commons-pool-1.0.1
  +# - Commons Pool, version 1.1 or later -
  +commons-pool.home=${base.path}/commons-pool-1.1
   commons-pool.lib=${commons-pool.home}
  -commons-pool.jar=${commons-pool.lib}/commons-pool.jar
  
-commons-pool.loc=http://archive.apache.org/dist/jakarta/commons/pool/binaries/pool-1.0.1.tar.gz
  +commons-pool.jar=${commons-pool.lib}/commons-pool-1.1.jar
  
+commons-pool.loc=http://archive.apache.org/dist/jakarta/commons/pool/binaries/commons-pool-1.1.tar.gz
   
   
   # - Commons FileUpload, version 1.0-20030531 or later -
  
  
  

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

cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenticator AuthenticatorBase.java

[remm]

remm2003/10/23 10:33:10

  Modified:catalina/src/share/org/apache/catalina/authenticator
AuthenticatorBase.java
  Log:
  - Add the caching flags even over a secure connection, due to Mozilla bugs.
  - I'm willing to revert that. I think Bill originally added the !isSecure.
  
  Revision  ChangesPath
  1.13  +7 -5  
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java
  
  Index: AuthenticatorBase.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- AuthenticatorBase.java21 Oct 2003 02:58:42 -  1.12
  +++ AuthenticatorBase.java23 Oct 2003 17:33:10 -  1.13
  @@ -514,7 +514,9 @@
   // or browsers as caching can provide a security hole
   HttpServletRequest hsrequest = (HttpServletRequest)hrequest.getRequest();
   if (disableProxyCaching && 
  -!hsrequest.isSecure() &&
  +// FIXME: Disabled for Mozilla FORM support over SSL 
  +// (improper caching issue)
  +//!hsrequest.isSecure() &&
   !"POST".equalsIgnoreCase(hsrequest.getMethod())) {
   HttpServletResponse sresponse = 
   (HttpServletResponse) response.getResponse();
  
  
  

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

DO NOT REPLY [Bug 23970] - form-based authentication and SSL, general principles

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

form-based authentication and SSL, general principles

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-10-23 17:32 ---
If you read the spec, you'll see the word "forward" being metioned in
conjunction with the login page. Hence, it doesn't have to go through the
constraints checks.
This will not be implemented, as most people considered using a sendRedirect for
FORM handling was evil.

There are two areas which have different behavior in TC 5:
- welcome files redirection
- FORM redirection
Since those are important changes, they weren't ported to Tomcat 4.1.x.

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

Re: no main in Embedded.java

[Remy Maucherat]

Mark W. Webb wrote:

My main motivation for this is that I am looking for a way to start 
embedded Tomcat from within a C program using the Invocation API.  What 
would be the new entry point class that I should look?  Whatever this 
class is, its the one that I want to call from my C program.
That method was the equivalent of server.xml. So the idea is that you 
should code it yourself according to your needs.

If you're upgrading to something different, I would rather create an 
embedded Tomcat through either Ant or directly JMX.

Remy



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

Re: no main in Embedded.java

[Mark W. Webb]

My main motivation for this is that I am looking for a way to start 
embedded Tomcat from within a C program using the Invocation API.  What 
would be the new entry point class that I should look?  Whatever this 
class is, its the one that I want to call from my C program.

Thank you.



Jean-Francois Arcand wrote:

The Embedded.main has been removed a long time ago (at the time of 
introducing JMX). As for the sh/bat, I did remove the option2 days 
ago (just browse the list). The JMX approach is in my opinion a good 
alternative:

http://apache.crihan.fr/dist/jakarta/tomcat-5/v5.0.12-beta/bin/jakarta-tomcat-5.0.12-embed.tar.gz 

I don't have any problem to bring the option back if you dig and 
submit a patch that bring back the Embedded.main (a lot of things has 
changed so be sure we are not regressing)

-- Jeanfrancois

Mark W. Webb wrote:

I was looking at the tomcat 5.0.12 source and noticed that the file 
Embedded.java does not contain a main.  I think that there should be 
one, since catalina.sh references this class as the entry point to 
start tomcat.

PS.  I do alot of work with embedded java and would like to help out 
more.  Please let me know if I may be of any help to the people 
maintaining that part of tomcat.

thanks.





-
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]




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

DO NOT REPLY [Bug 24065] New: - setLocale() still overrides charset from setContentType().

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

setLocale() still overrides charset from setContentType().

   Summary: setLocale() still overrides charset from
setContentType().
   Product: Tomcat 5
   Version: 5.0.0
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Servlet & JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Make a servlet with this service method:

public void service(ServletRequest request,
ServletResponse response)
throws IOException, ServletException {

response.setContentType("text/html; charset=ISO-8859-4");
java.io.PrintWriter writer = response.getWriter();
writer.println("Wakawaka");
writer.flush();

}

Requests to this servlet yield this response in JWSDP 1.3:

HTTP/1.1 200 OK
X-Powered-By: Servlet/2.4
Content-Type: text/html; charset=ISO-8859-4
Date: Thu, 23 Oct 2003 15:35:52 GMT
Server: Sun-Java-System/JWSDP-1.3
Connection: close

Wakawaka

modify the servlet to include a call to setLocale() as we do in the
resolution of this issue:

public void service(ServletRequest request,
ServletResponse response)
throws IOException, ServletException {

response.setContentType("text/html; charset=ISO-8859-4");
response.setLocale(java.util.Locale.GERMAN);
java.io.PrintWriter writer = response.getWriter();
writer.println("Wakawaka");
writer.flush();

}

Requests to this servlet yield this response in JWSDP 1.3:

HTTP/1.1 200 OK
X-Powered-By: Servlet/2.4
Content-Type: text/html; charset=ISO-8859-1
Content-Language: de
Date: Thu, 23 Oct 2003 15:36:31 GMT
Server: Sun-Java-System/JWSDP-1.3
Connection: close

Wakawaka

CONCLUSION: This behaviour is not correct.  The charset should be ISF-8859-4.

This bug is present in JWSDP 1.3.

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

Re: http://www.apache.org/dist/jakarta/tomcat-4/source/

[jean-frederic clere]

I have forgotten to tell that it is for Tomcat 4.1.x...

Clere, Jean-Frederic wrote:
Hi,

I am "playing" building binaries of Tomcat:
In http://www.apache.org/dist/jakarta/tomcat-4/source/ we only have 
jakarta-tomcat and jakarta-tomcat-connectors.
I think we should add jakarta-tomcat-jasper/jasper2 and 
jakarta-servletapi-4 otherwise it is quite hard to rebuild a binary from 
the sources.

Comments?

Cheers

Jean-Frederic

-
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]

http://www.apache.org/dist/jakarta/tomcat-4/source/

[jean-frederic clere]

Hi,

I am "playing" building binaries of Tomcat:
In http://www.apache.org/dist/jakarta/tomcat-4/source/ we only have 
jakarta-tomcat and jakarta-tomcat-connectors.
I think we should add jakarta-tomcat-jasper/jasper2 and jakarta-servletapi-4 
otherwise it is quite hard to rebuild a binary from the sources.

Comments?

Cheers

Jean-Frederic

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

Re: Re: new to dev list

[jamesmyang3]

Thanks, Bob. The presentation is good. Does Tomcat have design document? So I can dig 
deeper to source code level.

> 
> From: Bob Herrmann <[EMAIL PROTECTED]>
> Date: 2003/10/23 Thu AM 01:18:12 EDT
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> Subject: Re: new to dev list
> 
> Jamesmyang3 writes:
> > I am new to this development list. I download tomcat source
> > code and try to compile and run it. Can anyone provide me
> > some information on how Tomcat is designed? 
> 
> The best I could ever find is a PDF of a presentation that
> Craig McClanahan made back in June of 2000.  Look for "Tomcat Servlet"
> in this page;
> 
> http://servlet.java.sun.com/javaone/conf/bofs/1290/google-sf2001.jsp
> 
> The pdf is free, but they seem to want to charge for the audio.
> 
> Cheers,
> -bob
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

1


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

Re: cvs commit: jakarta-tomcat-connectors/procrun tomcat.dsp (KMM883223C0KM)

[SDLC-EXT]

Dear Jean-Francois Arcand,


Please remove from this alias.


Sincerely,

Lexia Sumsion
Sun Customer Service Specialist



Original Message Follows:
-

mturk   2003/10/23 07:01:42

  Modified:procrun  tomcat.dsp
  Log:
  Fix the missing POCRUN_EXTENDED preprocesor
  define to include TC specifics for the procrun.

  Revision  ChangesPath
  1.2   +7 -5  jakarta-tomcat-connectors/procrun/tomcat.dsp

  Index: tomcat.dsp
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/procrun/tomcat.dsp,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- tomcat.dsp29 Sep 2003 09:01:39 -  1.1
  +++ tomcat.dsp23 Oct 2003 14:01:42 -  1.2
  @@ -85,7 +85,8 @@
   # ADD BSC32 /nologo
   LINK32=link.exe
   # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
odbc32.lib odbccp32.lib comctl32.lib shlwapi.lib /nologo
/subsystem:windows /debug /machine:IX86 /out:"bin\tomcatw.exe"
/pdbtype:sept /opt:ref /opt:icf
  -# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
odbc32.lib odbccp32.lib comctl32.lib shlwapi.lib /nologo
/subsystem:windows /debug /machine:IX86 /out:"bin\tomcatw.exe"
/pdbtype:sept /opt:ref /opt:icf
  +# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
odbc32.lib odbccp32.lib comctl32.lib shlwapi.lib /nologo
/subsystem:windows /machine:IX86 /out:"bin\tomcatw.exe" /pdbtype:sept
/opt:ref /opt:icf
  +# SUBTRACT LINK32 /debug

   !ELSEIF  "$(CFG)" == "tomcat - Win32 Debug CONSOLE"

  @@ -101,7 +102,7 @@
   # PROP Ignore_Export_Lib 0
   # PROP Target_Dir ""
   # ADD BASE CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I
"$(JAVA_HOME)\include" /I "$(JAVA_HOME)\include\win32" /D "_WIN32" /D
"WIN32" /D "_DEBUG" /D "_DEBUG_TRACE" /D "_CONSOLE" /D "STRICT" /D
_WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D "_MBCS" /GZ
PRECOMP_VC7_TOBEREMOVED /c
  -# ADD CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I "$(JAVA_HOME)\include"
/I "$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "_DEBUG" /D
"_DEBUG_TRACE" /D "_CONSOLE" /D "STRICT" /D _WIN32_WINNT=0x0400 /D
"PROCRUN_CONSOLE" /D "_MBCS" /GZ /c
  +# ADD CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I "$(JAVA_HOME)\include"
/I "$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "_DEBUG" /D
"_DEBUG_TRACE" /D "_CONSOLE" /D "STRICT" /D _WIN32_WINNT=0x0400 /D
"PROCRUN_CONSOLE" /D "_MBCS" /D "PROCRUN_EXTENDED" /GZ /c
   # ADD BASE MTL /nologo /win32
   # ADD MTL /nologo /win32
   # ADD BASE RSC /l 0x409
  @@ -129,17 +130,18 @@
   # PROP Ignore_Export_Lib 0
   # PROP Target_Dir ""
   # ADD BASE CPP /nologo /MT /W3 /GX /Zi /O2 /I "$(JAVA_HOME)\include"
/I "$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "NDEBUG" /D
"_CONSOLE" /D "STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D
"_MBCS" /GF PRECOMP_VC7_TOBEREMOVED /c
  -# ADD CPP /nologo /MD /W3 /GX /Zi /O2 /I "$(JAVA_HOME)\include" /I
"$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "NDEBUG" /D
"_CONSOLE" /D "STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D
"_MBCS" /D "PROCRUN_EXTEND" /GF /c
  +# ADD CPP /nologo /MD /W3 /GX /Zi /O2 /I "$(JAVA_HOME)\include" /I
"$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "NDEBUG" /D
"_CONSOLE" /D "STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D
"_MBCS" /D "PROCRUN_EXTENDED" /GF /c
   # ADD BASE MTL /nologo /win32
   # ADD MTL /nologo /win32
   # ADD BASE RSC /l 0x409
  -# ADD RSC /l 0x409 /d "PROCRUN_EXTENDED"
  +# ADD RSC /l 0x409 /d "PROCRUN_EXTENDED" /d "PROCRUN_CONSOLE"
   BSC32=bscmake.exe
   # ADD BASE BSC32 /nologo
   # ADD BSC32 /nologo
   LINK32=link.exe
   # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
odbc32.lib odbccp32.lib comctl32.lib shlwapi.lib /nologo
/subsystem:console /debug /machine:IX86 /out:"bin\tomcat.exe"
/pdbtype:sept /opt:ref /opt:icf
  -# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
odbc32.lib odbccp32.lib comctl32.lib shlwapi.lib /nologo
/subsystem:console /debug /machine:IX86 /out:"bin\tomcat.exe"
/pdbtype:sept /opt:ref /opt:icf
  +# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
odbc32.lib odbccp32.lib comctl32.lib shlwapi.lib /nologo
/subsystem:console /machine:IX86 /out:"bin\tomcat.exe" /pdbtype:sept
/opt:ref /opt:icf
  +# SUBTRACT LINK32 /debug

   !ELSEIF  "$(CFG)" == "tomcat - Win32 DebugDLL"





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


-

cvs commit: jakarta-tomcat-4.0 build.properties.sample build.xml

[jfclere]

jfclere 2003/10/23 08:32:10

  Modified:.build.properties.sample build.xml
  Log:
  Arrange some minor problems with ant download task.
  
  Revision  ChangesPath
  1.70  +6 -6  jakarta-tomcat-4.0/build.properties.sample
  
  Index: build.properties.sample
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
  retrieving revision 1.69
  retrieving revision 1.70
  diff -u -r1.69 -r1.70
  --- build.properties.sample   23 Oct 2003 12:20:09 -  1.69
  +++ build.properties.sample   23 Oct 2003 15:32:09 -  1.70
  @@ -153,8 +153,8 @@
   
   
   # - Commons Daemon, version 1.0-Alpha or later -
  -commons-daemon.home=${base.path}/commons-daemon
  -commons-daemon.lib=${commons-daemon.home}/dist
  +commons-daemon.home=${base.path}/commons-daemon-1.0-Alpha
  +commons-daemon.lib=${commons-daemon.home}
   commons-daemon.jar=${commons-daemon.lib}/commons-daemon.jar
   
#commons-daemon.loc=${base-jakarta.loc}/commons/daemon/binaries/daemon-1.0-Alpha.tar.gz
   
commons-daemon.loc=http://www.apache.org/dist/jakarta/commons/daemon/binaries/commons-daemon-1.0-Alpha.tar.gz
  @@ -162,15 +162,15 @@
   
   # - Commons DBCP, version 1.0 or later -
   commons-dbcp.home=${base.path}/commons-dbcp-1.0
  -commons-dbcp.lib=${commons-dbcp.home}/commons-dbcp-1.0
  +commons-dbcp.lib=${commons-dbcp.home}
   commons-dbcp.jar=${commons-dbcp.lib}/commons-dbcp.jar
  -commons-dbcp.loc=${base-jakarta.loc}/commons/dbcp/binaries/dbcp-1.0.tar.gz
  +commons-dbcp.loc=${base-jakarta.loc}/commons/dbcp/binaries/commons-dbcp-1.0.tar.gz
   
   
   # - Commons Pool, version 1.0 or later -
   commons-pool.home=${base.path}/commons-pool-1.1
   commons-pool.lib=${commons-pool.home}
  -commons-pool.jar=${commons-pool.lib}/commons-pool.jar
  +commons-pool.jar=${commons-pool.lib}/commons-pool-1.1.jar
   commons-pool.loc=${base-jakarta.loc}/commons/pool/binaries/commons-pool-1.1.tar.gz
   
   
  
  
  
  1.82  +1 -2  jakarta-tomcat-4.0/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/build.xml,v
  retrieving revision 1.81
  retrieving revision 1.82
  diff -u -r1.81 -r1.82
  --- build.xml 23 Oct 2003 12:20:09 -  1.81
  +++ build.xml 23 Oct 2003 15:32:10 -  1.82
  @@ -506,10 +506,9 @@
 
   
   
  -
  +
 
 
  -  
   
   
 
  
  
  

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

Re: no main in Embedded.java

[Jean-Francois Arcand]

Remy Maucherat wrote:

Jean-Francois Arcand wrote:

The Embedded.main has been removed a long time ago (at the time of 
introducing JMX). As for the sh/bat, I did remove the option2 
days ago (just browse the list). The JMX approach is in my opinion a 
good alternative:

http://apache.crihan.fr/dist/jakarta/tomcat-5/v5.0.12-beta/bin/jakarta-tomcat-5.0.12-embed.tar.gz

I don't have any problem to bring the option back if you dig and 
submit a patch that bring back the Embedded.main (a lot of things has 
changed so be sure we are not regressing)


That method was nothing more than an example anyway. It has no place 
in the distribution.
I believe the Embedde API itself is still backwards compatible. 
Yes, it works fine.some products you may remember still use it ;-)



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]

Re: no main in Embedded.java

[Mark W. Webb]

Thanks for the information. 

I downloaded the tomcat-embedded tarball that you referenced.  It looks 
very minimal, which is nice.

Just a couple of points that I hope you can answer, my customer has some 
rigid requirements that I must follow:
1. The tomcat that I provide to the customer must be built from source, 
with instructions on how I compiled it.  Therefore, I ask the question; 
how can I compile the embedded tomcat from source?
2.  I do not see a startup script in the tarball that you provided me.  
Where may I find this?
3.  Where can I get more information on the new way in which embedded 
tomcat works using JMX?

thank you *very* much for your help.

Jean-Francois Arcand wrote:

The Embedded.main has been removed a long time ago (at the time of 
introducing JMX). As for the sh/bat, I did remove the option2 days 
ago (just browse the list). The JMX approach is in my opinion a good 
alternative:

http://apache.crihan.fr/dist/jakarta/tomcat-5/v5.0.12-beta/bin/jakarta-tomcat-5.0.12-embed.tar.gz 

I don't have any problem to bring the option back if you dig and 
submit a patch that bring back the Embedded.main (a lot of things has 
changed so be sure we are not regressing)

-- Jeanfrancois

Mark W. Webb wrote:

I was looking at the tomcat 5.0.12 source and noticed that the file 
Embedded.java does not contain a main.  I think that there should be 
one, since catalina.sh references this class as the entry point to 
start tomcat.

PS.  I do alot of work with embedded java and would like to help out 
more.  Please let me know if I may be of any help to the people 
maintaining that part of tomcat.

thanks.





-
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]




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

Re: no main in Embedded.java

[Remy Maucherat]

Jean-Francois Arcand wrote:

The Embedded.main has been removed a long time ago (at the time of 
introducing JMX). As for the sh/bat, I did remove the option2 days 
ago (just browse the list). The JMX approach is in my opinion a good 
alternative:

http://apache.crihan.fr/dist/jakarta/tomcat-5/v5.0.12-beta/bin/jakarta-tomcat-5.0.12-embed.tar.gz 

I don't have any problem to bring the option back if you dig and submit 
a patch that bring back the Embedded.main (a lot of things has changed 
so be sure we are not regressing)
That method was nothing more than an example anyway. It has no place in 
the distribution.
I believe the Embedde API itself is still backwards compatible.

Remy



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

Re: no main in Embedded.java

[Jean-Francois Arcand]

The Embedded.main has been removed a long time ago (at the time of 
introducing JMX). As for the sh/bat, I did remove the option2 days 
ago (just browse the list). The JMX approach is in my opinion a good 
alternative:

http://apache.crihan.fr/dist/jakarta/tomcat-5/v5.0.12-beta/bin/jakarta-tomcat-5.0.12-embed.tar.gz

I don't have any problem to bring the option back if you dig and submit 
a patch that bring back the Embedded.main (a lot of things has changed 
so be sure we are not regressing)

-- Jeanfrancois

Mark W. Webb wrote:

I was looking at the tomcat 5.0.12 source and noticed that the file 
Embedded.java does not contain a main.  I think that there should be 
one, since catalina.sh references this class as the entry point to 
start tomcat.

PS.  I do alot of work with embedded java and would like to help out 
more.  Please let me know if I may be of any help to the people 
maintaining that part of tomcat.

thanks.





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



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

cvs commit: jakarta-tomcat-connectors/procrun tomcat.rc

[mturk]

mturk   2003/10/23 07:05:11

  Modified:procrun  tomcat.rc
  Log:
  Add only the icon for the console mode.
  This also makes the binary about 10K smaller.
  
  Revision  ChangesPath
  1.3   +2 -2  jakarta-tomcat-connectors/procrun/tomcat.rc
  
  Index: tomcat.rc
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/procrun/tomcat.rc,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- tomcat.rc 1 Oct 2003 18:08:58 -   1.2
  +++ tomcat.rc 23 Oct 2003 14:05:11 -  1.3
  @@ -60,11 +60,11 @@
   #include "windows.h"
   
   IDI_ICOCONWRAP ICON"tomcatp.ico"
  +#ifndef PROCRUN_CONSOLE
   IDI_ICOCONTRY  ICON"tomcatr.ico"
   IDI_ICOCONTRYSTOP  ICON"tomcats.ico"
   
  -#ifdef _MSC_VER
  -IDB_BMPSPLASH  BITMAP   DISCARDABLE"tomcat.bmp"
  +BMPSPLASH  BITMAP  "tomcat.bmp"
   #endif
   
   #include "procrun.rc"
  
  
  

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

cvs commit: jakarta-tomcat-connectors/procrun/bin tomcat.exe tomcatw.exe

[mturk]

mturk   2003/10/23 07:02:52

  Modified:procrun/bin tomcat.exe tomcatw.exe
  Log:
  Latest builds...
  BTW what was the conclusion for the location of
  those binaries?
  
  Revision  ChangesPath
  1.5   +28 -72jakarta-tomcat-connectors/procrun/bin/tomcat.exe
  
<>
  
  
  1.5   +39 -37jakarta-tomcat-connectors/procrun/bin/tomcatw.exe
  
<>
  
  

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

cvs commit: jakarta-tomcat-connectors/procrun tomcat.dsp

[mturk]

mturk   2003/10/23 07:01:42

  Modified:procrun  tomcat.dsp
  Log:
  Fix the missing POCRUN_EXTENDED preprocesor
  define to include TC specifics for the procrun.
  
  Revision  ChangesPath
  1.2   +7 -5  jakarta-tomcat-connectors/procrun/tomcat.dsp
  
  Index: tomcat.dsp
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/procrun/tomcat.dsp,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- tomcat.dsp29 Sep 2003 09:01:39 -  1.1
  +++ tomcat.dsp23 Oct 2003 14:01:42 -  1.2
  @@ -85,7 +85,8 @@
   # ADD BSC32 /nologo
   LINK32=link.exe
   # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
comctl32.lib shlwapi.lib /nologo /subsystem:windows /debug /machine:IX86 
/out:"bin\tomcatw.exe" /pdbtype:sept /opt:ref /opt:icf
  -# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
comctl32.lib shlwapi.lib /nologo /subsystem:windows /debug /machine:IX86 
/out:"bin\tomcatw.exe" /pdbtype:sept /opt:ref /opt:icf
  +# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
comctl32.lib shlwapi.lib /nologo /subsystem:windows /machine:IX86 
/out:"bin\tomcatw.exe" /pdbtype:sept /opt:ref /opt:icf
  +# SUBTRACT LINK32 /debug
   
   !ELSEIF  "$(CFG)" == "tomcat - Win32 Debug CONSOLE"
   
  @@ -101,7 +102,7 @@
   # PROP Ignore_Export_Lib 0
   # PROP Target_Dir ""
   # ADD BASE CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I "$(JAVA_HOME)\include" /I 
"$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "_DEBUG" /D "_DEBUG_TRACE" /D 
"_CONSOLE" /D "STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D "_MBCS" /GZ 
PRECOMP_VC7_TOBEREMOVED /c
  -# ADD CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I "$(JAVA_HOME)\include" /I 
"$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "_DEBUG" /D "_DEBUG_TRACE" /D 
"_CONSOLE" /D "STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D "_MBCS" /GZ /c
  +# ADD CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I "$(JAVA_HOME)\include" /I 
"$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "_DEBUG" /D "_DEBUG_TRACE" /D 
"_CONSOLE" /D "STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D "_MBCS" /D 
"PROCRUN_EXTENDED" /GZ /c
   # ADD BASE MTL /nologo /win32
   # ADD MTL /nologo /win32
   # ADD BASE RSC /l 0x409
  @@ -129,17 +130,18 @@
   # PROP Ignore_Export_Lib 0
   # PROP Target_Dir ""
   # ADD BASE CPP /nologo /MT /W3 /GX /Zi /O2 /I "$(JAVA_HOME)\include" /I 
"$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D 
"STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D "_MBCS" /GF 
PRECOMP_VC7_TOBEREMOVED /c
  -# ADD CPP /nologo /MD /W3 /GX /Zi /O2 /I "$(JAVA_HOME)\include" /I 
"$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D 
"STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D "_MBCS" /D "PROCRUN_EXTEND" 
/GF /c
  +# ADD CPP /nologo /MD /W3 /GX /Zi /O2 /I "$(JAVA_HOME)\include" /I 
"$(JAVA_HOME)\include\win32" /D "_WIN32" /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D 
"STRICT" /D _WIN32_WINNT=0x0400 /D "PROCRUN_CONSOLE" /D "_MBCS" /D "PROCRUN_EXTENDED" 
/GF /c
   # ADD BASE MTL /nologo /win32
   # ADD MTL /nologo /win32
   # ADD BASE RSC /l 0x409
  -# ADD RSC /l 0x409 /d "PROCRUN_EXTENDED"
  +# ADD RSC /l 0x409 /d "PROCRUN_EXTENDED" /d "PROCRUN_CONSOLE"
   BSC32=bscmake.exe
   # ADD BASE BSC32 /nologo
   # ADD BSC32 /nologo
   LINK32=link.exe
   # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
comctl32.lib shlwapi.lib /nologo /subsystem:console /debug /machine:IX86 
/out:"bin\tomcat.exe" /pdbtype:sept /opt:ref /opt:icf
  -# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
comctl32.lib shlwapi.lib /nologo /subsystem:console /debug /machine:IX86 
/out:"bin\tomcat.exe" /pdbtype:sept /opt:ref /opt:icf
  +# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
comctl32.lib shlwapi.lib /nologo /subsystem:console /machine:IX86 
/out:"bin\tomcat.exe" /pdbtype:sept /opt:ref /opt:icf
  +# SUBTRACT LINK32 /debug
   
   !ELSEIF  "$(CFG)" == "tomcat - Win32 DebugDLL"
   
  
  
  

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

no main in Embedded.java

[Mark W. Webb]

I was looking at the tomcat 5.0.12 source and noticed that the file 
Embedded.java does not contain a main.  I think that there should be 
one, since catalina.sh references this class as the entry point to start 
tomcat.

PS.  I do alot of work with embedded java and would like to help out 
more.  Please let me know if I may be of any help to the people 
maintaining that part of tomcat.

thanks.





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

DO NOT REPLY [Bug 24011] - 5.0.13 Installer creates wrong service Registry key

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

5.0.13 Installer creates wrong service Registry key





--- Additional Comments From [EMAIL PROTECTED]  2003-10-23 13:54 ---

Sorry ;-).
Mea culpa (forgot /DPROCRUN_EXTENDED) for tomcat.exe
Fixed in the cvs...

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

DO NOT REPLY [Bug 24011] - 5.0.13 Installer creates wrong service Registry key

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

5.0.13 Installer creates wrong service Registry key





--- Additional Comments From [EMAIL PROTECTED]  2003-10-23 13:48 ---
I got the same problem: I can't run in service mode (running from systray is
ok). I did a reinstall and used the latest binaries. Are you sure there isn't
some kind of problem, or the banaries built wrong ?

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

DO NOT REPLY [Bug 24011] - 5.0.13 Installer creates wrong service Registry key

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

5.0.13 Installer creates wrong service Registry key

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-10-23 13:42 ---

This is a correct behavior.
All the tomcat code has been pulled out from procrun,
and now exists inside j-t-c/procrun.
Those are mainly bitmaps, splash screen, etc.
To build you will need the procrun sources from daemon.

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

cvs commit: jakarta-tomcat-4.0 build.properties.sample build.xml

[jfclere]

jfclere 2003/10/23 05:20:09

  Modified:.build.properties.sample build.xml
  Log:
  Use archive and arrange some location.
  Use the Alpha of daemon instead cvs.
  
  Revision  ChangesPath
  1.69  +18 -14jakarta-tomcat-4.0/build.properties.sample
  
  Index: build.properties.sample
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
  retrieving revision 1.68
  retrieving revision 1.69
  diff -u -r1.68 -r1.69
  --- build.properties.sample   7 Oct 2003 13:25:45 -   1.68
  +++ build.properties.sample   23 Oct 2003 12:20:09 -  1.69
  @@ -51,6 +51,9 @@
   #jasper.home=../jakarta-tomcat-jasper/jasper2
   
   
  +# - Jakarta files base location -
  +base-jakarta.loc=http://archive.apache.org/dist/jakarta/
  +
   # --
   #REQUIRED LIBRARIES
   # --
  @@ -60,28 +63,28 @@
   commons-beanutils.home=${base.path}/commons-beanutils-1.6.1
   commons-beanutils.lib=${commons-beanutils.home}
   commons-beanutils.jar=${commons-beanutils.lib}/commons-beanutils.jar
  
-commons-beanutils.loc=http://www.apache.org/dist/jakarta/commons/beanutils/binaries/commons-beanutils-1.6.1.tar.gz
  
+commons-beanutils.loc=${base-jakarta.loc}/commons/beanutils/binaries/commons-beanutils-1.6.1.tar.gz
   
   
   # - Commons Collections, version 1.0 or later -
   commons-collections.home=${base.path}/commons-collections-2.1
   commons-collections.lib=${commons-collections.home}
   commons-collections.jar=${commons-collections.lib}/commons-collections.jar
  
-commons-collections.loc=http://www.apache.org/dist/jakarta/commons/collections/binaries/collections-2.1.tar.gz
  
+commons-collections.loc=${base-jakarta.loc}/commons/collections/binaries/collections-2.1.tar.gz
   
   
   # - Commons Digester, version 1.1.1 or later -
   commons-digester.home=${base.path}/commons-digester-1.5
   commons-digester.lib=${commons-digester.home}
   commons-digester.jar=${commons-digester.lib}/commons-digester.jar
  
-commons-digester.loc=http://www.apache.org/dist/jakarta/commons/digester/binaries/commons-digester-1.5.tar.gz
  
+commons-digester.loc=${base-jakarta.loc}/commons/digester/binaries/commons-digester-1.5.tar.gz
   
   
   # - Commons FileUpload, nightly build -
   commons-fileupload.home=${base.path}/commons-fileupload-1.0
   commons-fileupload.lib=${commons-fileupload.home}
   commons-fileupload.jar=${commons-fileupload.lib}/commons-fileupload-1.0.jar
  
-commons-fileupload.loc=http://www.apache.org/dist/jakarta/commons/fileupload/commons-fileupload-1.0.tar.gz
  
+commons-fileupload.loc=${base-jakarta.loc}/commons/fileupload/binaries/commons-fileupload-1.0.tar.gz
   
   
   # - Commons Logging, version 1.0.1 or later -
  @@ -89,7 +92,7 @@
   commons-logging.lib=${commons-logging.home}
   commons-logging-api.jar=${commons-logging.lib}/commons-logging-api.jar
   commons-logging.jar=${commons-logging.lib}/commons-logging.jar
  
-commons-logging.loc=http://www.apache.org/dist/jakarta/commons/logging/binaries/commons-logging-1.0.3.tar.gz
  
+commons-logging.loc=${base-jakarta.loc}/commons/logging/binaries/commons-logging-1.0.3.tar.gz
   
   
   # - Java Naming and Directory Interface (JNDI), version 1.2 or later -
  @@ -105,14 +108,14 @@
   commons-modeler.home=${base.path}/commons-modeler-1.1
   commons-modeler.lib=${commons-modeler.home}
   commons-modeler.jar=${commons-modeler.lib}/commons-modeler.jar
  
-commons-modeler.loc=http://archive.apache.org/dist/jakarta/commons/modeler/binaries/modeler-1.1.tar.gz
  +commons-modeler.loc=${base-jakarta.loc}/commons/modeler/binaries/modeler-1.1.tar.gz
   
   
   # - Jakarta Regular Expressions Library, version 1.2 -
   regexp.home=${base.path}/jakarta-regexp-1.3
   regexp.lib=${regexp.home}
   regexp.jar=${regexp.lib}/jakarta-regexp-1.3.jar
  
-regexp.loc=http://archive.apache.org/dist/jakarta/regexp/binaries/jakarta-regexp-1.3.tar.gz
  +regexp.loc=${base-jakarta.loc}/regexp/binaries/jakarta-regexp-1.3.tar.gz
   
   
   # - Jakarta Servlet API Classes (Servlet 2.3 / JSP 1.2) -
  @@ -149,25 +152,26 @@
   activation.jar=${activation.lib}/activation.jar
   
   
  -# - Commons Daemon, version 20020219 or later -
  +# - Commons Daemon, version 1.0-Alpha or later -
   commons-daemon.home=${base.path}/commons-daemon
   commons-daemon.lib=${commons-daemon.home}/dist
   commons-daemon.jar=${commons-daemon.lib}/commons-daemon.jar
  -commons-daemon.loc=jakarta-commons-sandbox/daemon
  
+#commons-daemon.loc=${base-jakarta.loc}/commons/daemon/binaries/daemon-1.0-Alpha.tar.gz
  
+commons-daemon.loc=http://www.apache.org/dist/jakarta/commons/daemon/binaries/commons-daemon-1.0-Alpha.tar.gz
   
   
   # - Commons DBCP, version 1.0 or later -
   commons-dbcp.home=${base.path}/commons-dbcp-1.0
   commons-dbc

error starting tomcat ....

[asad khan]

hi

 i have downloaded tomcat 5.0.12 from jakarta website
. having win 2000 as operating system and java2 sdk
1.4.0 ...

  now i have follewed all the instructions find on the
online tutorial of configuring ans starting tomcat .

  but when i run catalina 
i found errors of :

java.lang.reflect.InvocationTargetException .

  would u plz help me to sort it out and tell me wat
to do to start the tomcat 


 waiting for your reply ..


 best regards .




__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

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

Re: new to dev list

[Bob Herrmann]

Jamesmyang3 writes:
> I am new to this development list. I download tomcat source
> code and try to compile and run it. Can anyone provide me
> some information on how Tomcat is designed? 

The best I could ever find is a PDF of a presentation that
Craig McClanahan made back in June of 2000.  Look for "Tomcat Servlet"
in this page;

http://servlet.java.sun.com/javaone/conf/bofs/1290/google-sf2001.jsp

The pdf is free, but they seem to want to charge for the audio.

Cheers,
-bob





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

DO NOT REPLY [Bug 24011] - 5.0.13 Installer creates wrong service Registry key

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

5.0.13 Installer creates wrong service Registry key





--- Additional Comments From [EMAIL PROTECTED]  2003-10-23 10:25 ---
I can reproduce the issue. Mladen or Bill, can you fix the issue before tomorrow ?

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

DO NOT REPLY [Bug 24050] - Logs folder not present in 5.0.12 tgz

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

Logs folder not present in 5.0.12 tgz

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-10-23 10:13 ---
The logs folder is correctly present in the distribution. Please use GNU TAR.

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

DO NOT REPLY [Bug 24050] New: - Logs folder not present in 5.0.12 tgz

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

Logs folder not present in 5.0.12 tgz

   Summary: Logs folder not present in 5.0.12 tgz
   Product: Tomcat 5
   Version: 5.0.12
  Platform: Other
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Native:Packaging
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The 5.0.12 tgz does not have the "logs" folder. This is required for the
startup.sh script to work.

A short term solution would be to create the logs folder oneself.

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

Re: New builds ?

[Remy Maucherat]

David Rees wrote:
Remy Maucherat wrote:

David Rees wrote:

I've been using 4.1.29 for development without any issues for a few 
days now.  Just one minor annoyance, I get this message twice when 
starting
Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"


Very good point. I'll tag new 4.1.30 and 5.0.14 builds tomorrow.
Hopefully more people will vote next time :)


Anyone have any idea on what's causing that message from Coyote to end 
up in the cataline log file?
Well, we switched to Coyote from TC 5, so this adds a requirement on 
JMX. Apparently, it does work even if JMX isn't there (I'm a bit surprised).

Remy

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

Logs folder not present in 5.0.12 (Was: Re: New builds ?)

[Sriram N]

Remy:

I downloaded 5.0.12 yesterday and tried it on Linux.

I got the following error
touch: creating `/root/jakarta-tomcat-5.0.12/logs/catalina.out': No such file
or directory
/root/jakarta-tomcat-5.0.12/bin/catalina.sh: line 231:
/root/jakarta-tomcat-5.0.12/logs/catalina.out: No such file or directory

I was able to remedy this by creating the "logs" folder myself. Could you fix
this in the next release ?

-- Sriram

--- Remy Maucherat <[EMAIL PROTECTED]> wrote:
> David Rees wrote:
> 
> > Remy Maucherat wrote:
> > 
> >> So, what do we do with 4.1.28 ? AFAIK, no significant issue has been 
> >> found with this build, with minor tweaks being made since then in the 
> >> connectors.
> >> Is a 4.1.29 needed, or is it simply people forgot about that build ?
> >>
> >> Comments ?
> > 
> > 
> > I've been using 4.1.29 for development without any issues for a few days 
> > now.  Just one minor annoyance, I get this message twice when starting
> > Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"
> > 
> > Now that new versions of commons dbcp and pool have been released, 
> > upgrading to the latest may be a good idea and an excuse to retag 
> > 4.1.30.  I don't think you'll get many testers until it's called beta, 
> > though.
> > 
> > Other than that, looks good!
> 
> Very good point. I'll tag new 4.1.30 and 5.0.14 builds tomorrow.
> Hopefully more people will vote next time :)
> 
> Rémy
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

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

Re: New builds ?

[David Rees]

Remy Maucherat wrote:
David Rees wrote:
I've been using 4.1.29 for development without any issues for a few 
days now.  Just one minor annoyance, I get this message twice when 
starting
Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"
Very good point. I'll tag new 4.1.30 and 5.0.14 builds tomorrow.
Hopefully more people will vote next time :)
Anyone have any idea on what's causing that message from Coyote to end 
up in the cataline log file?

-Dave

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

Re: New builds ?

[Remy Maucherat]

David Rees wrote:

Remy Maucherat wrote:

So, what do we do with 4.1.28 ? AFAIK, no significant issue has been 
found with this build, with minor tweaks being made since then in the 
connectors.
Is a 4.1.29 needed, or is it simply people forgot about that build ?

Comments ?


I've been using 4.1.29 for development without any issues for a few days 
now.  Just one minor annoyance, I get this message twice when starting
Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"

Now that new versions of commons dbcp and pool have been released, 
upgrading to the latest may be a good idea and an excuse to retag 
4.1.30.  I don't think you'll get many testers until it's called beta, 
though.

Other than that, looks good!
Very good point. I'll tag new 4.1.30 and 5.0.14 builds tomorrow.
Hopefully more people will vote next time :)
Rémy



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

Re: New builds ?

[David Rees]

Remy Maucherat wrote:
So, what do we do with 4.1.28 ? AFAIK, no significant issue has been 
found with this build, with minor tweaks being made since then in the 
connectors.
Is a 4.1.29 needed, or is it simply people forgot about that build ?

Comments ?
I've been using 4.1.29 for development without any issues for a few days 
now.  Just one minor annoyance, I get this message twice when starting
Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"

Now that new versions of commons dbcp and pool have been released, 
upgrading to the latest may be a good idea and an excuse to retag 
4.1.30.  I don't think you'll get many testers until it's called beta, 
though.

Other than that, looks good!

-Dave

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