William L. Thomson Jr. | 1 Aug 01:11 2007
Picon

Re: Inlining dependencies

On Tue, 2007-07-31 at 14:59 -0400, Yoav Shapira wrote:
> > It's all done in Ant tasks: look for how
> the Tomcat build handles Jakarta Commons DBCP for example.

I absolutely despise how that is built. It makes building that jar a
complete NIGHTMARE. Presently we do not offer than jar on Gentoo and I
have no plans to. Or worse potential ways to.

Because I will have to hack around our packaging system to even make an
attempt. Hard coding versions of a libraries sources within another
package, and not as a package dependency. But as additional sources for
Tomcat :(. Despite a newer version of those libraries already existing
on the system. Which also means they have downloaded a copy of that
packages sources, but might not have installed the sources.

It is the oldest bug wrt to Tomcat on Gentoo :(
http://bugs.gentoo.org/buglist.cgi?quicksearch=tomcat

It came up in the past here, where others also disliked the process of
how it was built. But so far has fallen on deaf ears. I have not had the
time or chance to address the issue and provide you all with a code work
around.
http://marc.info/?l=tomcat-dev&m=115808287528288&w=2

>   We don't
> trim them down AFAIK, nor do we have to do any porting because we
> re-grab the library (ideally from a known stable version) with every
> release.

I see there are some slight modifications. Other than the re-branding
(Continue reading)

Mark Thomas | 1 Aug 02:55 2007
Picon

Re: [VOTE] Release build 6.0.14

Remy Maucherat wrote:
> The candidates binaries are available here:
> http://people.apache.org/~remm/tomcat-6/v6.0.14/
> 
> According to the release process, the 6.0.14 tag is:
> [ ] Broken
> [ ] Alpha
> [ ] Beta
> [X] Stable

No issues found.

Mark
bugzilla | 1 Aug 04:03 2007
Picon

DO NOT REPLY [Bug 42922] - Comments not removed when using XML Syntax

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42922>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42922

markt <at> apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED

------- Additional Comments From markt <at> apache.org  2007-07-31 19:03 -------
My bad. When I fixed bug 22802 I wasn't careful enough with the copy and paste
and introduced this problem.

The fix is now in svn and will be included in the next release.

Thanks for the report.

--

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
markt | 1 Aug 04:22 2007
Picon

svn commit: r561623 - in /tomcat: container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt jasper/branches/tc4.1.x/src/share/org/apache/jasper/compiler/JspDocumentParser.java

Author: markt
Date: Tue Jul 31 19:22:56 2007
New Revision: 561623

URL: http://svn.apache.org/viewvc?view=rev&rev=561623
Log:
Fix bug 42922. Treat XML comments as comments in JSP documents

Modified:
    tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt
    tomcat/jasper/branches/tc4.1.x/src/share/org/apache/jasper/compiler/JspDocumentParser.java

Modified: tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt
URL: http://svn.apache.org/viewvc/tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt?view=diff&rev=561623&r1=561622&r2=561623
==============================================================================
--- tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt (original)
+++ tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt Tue Jul 31 19:22:56 2007
 <at>  <at>  -2399,6 +2399,10  <at>  <at> 
          <jsp:include> whose target performs a 'forward' does not behave as
          expected

+[4.1.37] #42922
+         Generator
+         XML comments were treated as template text in JSP Documents
+

 ============================
 KNOWN ISSUES IN THIS RELEASE:

Modified: tomcat/jasper/branches/tc4.1.x/src/share/org/apache/jasper/compiler/JspDocumentParser.java
(Continue reading)

David Blevins | 1 Aug 04:47 2007

Re: Juli/Logging


On Jul 31, 2007, at 2:27 PM, Rainer Jung wrote:

> Hi David,
>
> our default bundled JULI only has a binding for java.util.logging. On
>
> http://tomcat.apache.org/tomcat-6.0-doc/extras.html
>
> there is a very short description, how one builds a JULI, that is  
> log4j enabled. The static binding was chosen, because commons- 
> logging auto detection provided to many problems w.r.t.  
> redeployment and classloader leaks.

Cool, thanks.

> My personal opinion: java.util.logging very much lacks a good  
> formatter. The default 2 line formatting of messages, splitting  
> timestamps and message in separate lines, is not really useful in  
> production. Many ad hoc log analysis practices work on a line  
> oriented basis.

Was wondering about that.  I've heard people grumble about  
java.util.logging, but haven't (till now) heard anything specific.   
Maybe I wasn't paying close enough attention, but the Tomcat 6 log  
files still seem to follow the one line per message format.  How did  
you pull that off?

-David

(Continue reading)

dlullier | 1 Aug 04:48 2007
Picon

Denis LULLIER/Paris est absent(e).


Je serai absent(e) du  01/08/2007 au 27/08/2007.

Je répondrai à votre message dès mon retour. En cas d'urgence, vous pouvez
contacter Christine DUHAU ou Marc-Olivier JOUAN
Santosh [ಸಂತೋಷ ] | 1 Aug 08:20 2007
Picon

Development of admin webapp

Hi All,

        As admin webapp is not supported in tomcat 6.0.x, i have taken admin
webapp of tomcat 5.5.23 and modified according to tomcat 6.0.7 code. Now my
admin webapp is up and running in tomcat 6.0.7. Following operations are
working in admin webapp,

1. Logging in
2. Updation to Tomcat Server (Server, Connector, Host)
3. Adding new host.

Following are not working,

1. Addition or deletion of resources.
2. Addition or deletion of User Definition.

Whenever i try these operations, i am getting HTTP 500 error and message is
"*Error invoking operation **addEnvironment*" (While adding environment
variables). I think mbean for
"Catalina:type=NamingResources,resourcetype=Global" is not
registered/created in tomcat 6.07.

Please someone help to get these working.

Regards,
Santosh
Rainer Jung | 1 Aug 10:30 2007
Picon

Re: Juli/Logging

David Blevins wrote:
>> My personal opinion: java.util.logging very much lacks a good 
>> formatter. The default 2 line formatting of messages, splitting 
>> timestamps and message in separate lines, is not really useful in 
>> production. Many ad hoc log analysis practices work on a line oriented 
>> basis.
> 
> Was wondering about that.  I've heard people grumble about 
> java.util.logging, but haven't (till now) heard anything specific.  
> Maybe I wasn't paying close enough attention, but the Tomcat 6 log files 
> still seem to follow the one line per message format.  How did you pull 
> that off?

That's what I get:

Aug 1, 2007 10:26:37 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-28680
Aug 1, 2007 10:26:37 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2854 ms
Aug 1, 2007 10:26:37 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Aug 1, 2007 10:26:37 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.13
Aug 1, 2007 10:26:40 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-28680

One line for timestamp, class and method, a second line for log level 
and message. That's the format of the default formatter, the simple log 
format.

(Continue reading)

Remy Maucherat | 1 Aug 10:40 2007
Picon

Re: Juli/Logging

Rainer Jung wrote:
> That's why it would be nice if someone took the burden of writing a 
> better log formatter for j.u.l.

What should it look like ?

Rémy
Rainer Jung | 1 Aug 11:50 2007
Picon

Re: Juli/Logging

Hi Remy,

if we only want to give an alternative for the SimpleFormatter:

that one is not configurable, so it's capabilities are printing out a 
localized timestamp, after that the class and method, a localized level 
string, and last the log message. All of those are basically given by 
the log record, level localization is provided by the Level class, 
Timestamp is not problem (milliseconds in the log record), and should 
also contain the millisesond fraction.

Of course we could add configurability in a next step, which would 
basically mean an accesslog/log4j like pattern string for the log line.

The log record carries the following information:

- level
- message
- milliseconds timestamp
- source class and method name
- thread id
- logger name
- sequence number (interesting feature, so one can easily describe, 
which message instance in a log one is talking about)

and more complex objects

- thrown (throwable associated with the record)
- resource bundle and/or resource bundle name to format message string
- parameters, log data extension
(Continue reading)


Gmane