Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 43741]  - .tag files in a .tar recompiled for each
 .jsp -- extremely slow (with fix)
In-Reply-To: <bug-43741-78@http.issues.apache.org/bugzilla/>
Message-Id: <20080129231714.C10F271423E@brutus.apache.org>
Date: Tue, 29 Jan 2008 15:17:14 -0800 (PST)

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=43741>.
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=43741


------- Additional Comments From markt@apache.org  2008-01-29 15:17 -------
I have looked at this some more.

I think your patch is pretty much spot on. Generally, if a JAR changes, the app
needs to be re-loaded (eg using reloadable or watched resources). That is true
for any other JAR and I don't see why it shouldn't be true for JARs containing
tag files.

Compiling tags in a single pass (bug 43742) would also help.

Bug 43878 will also contribute to poor performance, although in a different way.

Your patch has been applied to trunk and proposed for 6.0.x.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org