DO NOT REPLY [Bug 53033] New: Cannot undeploy applications
https://issues.apache.org/bugzilla/show_bug.cgi?id=53033 Bug #: 53033 Summary: Cannot undeploy applications Product: Tomcat 5 Version: 5.5.26 Platform: Sun OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: Webapps:Manager AssignedTo: dev@tomcat.apache.org ReportedBy: ducnvlo...@gmail.com Classification: Unclassified When I click on Undeploy an application from the applications list. I get the message OK/ undeployed... but the application is still in the list with the status false . I cannot start/stop/undeploy anymore. Can some one help me with this please? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Who wants my Cassandra session manager for Tomcat?
On 03/04/2012 22:18, Morten Jorgensen wrote: Thanks to all for your feedback. I am providing some additional information as requested: That's interesting. Can you share some details about how it works? Sure. It is quite simple. Cassandra is effectively a multi-level distributed hash-map, so it lends itself very well do storing session attributes. The session manager maintains two column families (like tables), one to hold session meta-data such as the last access timestamp, etc. and one column family to hold session attributes. Storing or reading a session attribute is simply a matter of writing it using the session ID as the row ID, and the session attribute name as the column name, and the session attribute value as the column value. Session attributes are read and written independently, so the entire web session does not have to be loaded into memory - only the session attributes that are actually required to service a request are read. This greatly reduces the memory footprint of the web applications that I am developing for my employer. I'd be concerned about how chatty that was. Devil's advocate question: why store data in the session if it's not needed? For improved performance I have added a write-through and a write-back cache, implemented as servlet filters. The cache is flushed or written back once the current request has finished processing. I am sure there is room for improvement here, as multiple concurrent requests for the same session should be served using the same cache instance. But... (more devil's advocating, sorry) while this should address the chattiness* problem, doesn't it mean that your solution is invasive and can't be really deployed without modifying an app? * is that even a word? The Manager does not maintain any references to Session instances at all, allowing them to be garbage collected at any time. This makes things very simple, as Cassandra holds all session state, and the session managers in my Tomcat nodes only act as a cache in front of Cassandra. The nature of Cassandra and the Tomcat's implementation of web sessions go together extremely well. I am surprised that nothing like this exists already. It is a square hole, square peg sort of scenario. I'm not entirely sure I agree. Cassandra trades off consistency for availability and partition tolerance, whereas I'd suggest a session management solution would want to trade partition tolerance for consistency and availability. I'm also not sure that the comparison between column store and session attribute map stands up beyond the initial/apparent similarity between data type. Cassandra is write-optimised and hits disk (on at least two nodes for HA) for every write AFAIK. I also have an implementation of the Map interface that stores the values of each entry as a session attribute. The way many developers write web applications is to have a session bean (a session attribute) that contains a Map that maintains the actual session attributes. This is OK if the entire session is persisted as a whole, but it won't perform very well with the Cassandra session manager (or the Delta Session Manager from what I understand). A developer can replace their session bean's HashMap with the SessionMap utility, and the session attributes will be treated as proper session attributes by the session manager. Is there not a way to do this internally therefore transparently to the developer? Otherwise you're introducing more dependencies and creating more of a framework than a pluggable manager. 1. Be relatively self-contained -- i.e. not require much in the way of changes to existing classes There are no changes to existing classes. My session manager implements the existing org.apache.catalina.Manager interface. Instead of the filter, could you use a Valve? p 2. Not have any external dependencies (new JAR files, etc.). This might be a problem, depending on whether your code uses the REST API for Cassandra or a direct Java binding. This could be a problem... I use the Hector API to access Cassandra, and there are about 10 JARs required for this API. 3. Include good documentation for how to set it up. See the existing session-persistence documentation for a guide, and aim to do a better job ;) It is extremely easy to set up: 1) Configure your Cassandra ring (cluster). 2) Copy the required Hector API JARs and the Cassandra session manager JAR to tomcat/lib 3) Configure your web application descriptor to use the Cassandra session manager. Parameters in the web application descriptor point the session manager to one or more nodes in your Cassandra ring. 4. Include test cases and potentially instructions for setting-up a test environment (i.e. you're gonna need a working Cassandra instance). This is pretty much non-existent right now, so I'll put some effort in there. What format do you guys use for your documentation? Do you still use docbook? Thanks
[jira] [Created] (MTOMCAT-133) Servlet mapping to / does not work
Servlet mapping to / does not work - Key: MTOMCAT-133 URL: https://issues.apache.org/jira/browse/MTOMCAT-133 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat7 Affects Versions: 2.0 Environment: Mac OS X, Apple JRE 1.6 Reporter: Gildas Cuisinier Assignee: Olivier Lamy (*$^¨%`£) Using the Servlet 3.0 possibilities to add and configure servlet (ServletContainerInitializer through Spring 3.1 WebApplicationInitializer), I try to map a servlet /, but is not working properly. The servlet is started correctly, but the mapping does not work. If I replace / by test/*, everything work perfectly. For information, the / mapping works well in a standalone tomcat 7.0.25. I put a sample project on github that reproduce the bug : https://github.com/hikage/tomcat7-bug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #2 from Ferenc Lutischan yours...@freemail.hu 2012-04-04 11:30:55 UTC --- Created attachment 28542 -- https://issues.apache.org/bugzilla/attachment.cgi?id=28542 Test application Test application -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #3 from Ferenc Lutischan yours...@freemail.hu 2012-04-04 11:40:27 UTC --- Test case: - Unzip the downloaded Tomcat 7.0.26 from tomcat.apache.org site - Edit the unzipped dir/conf/tomcat-users.xml. Add the following line: user password=ide roles=standard,manager-gui,admin username=ide/ - Unzip the attached Test application into the unzipped dir/webapps - start tomcat - open http://localhost:8080/ServletRestartTest/ServletRestartTest - open the manager application (http://localhost:8080/manager/html) with ide/ide - reload the ServletRestartTest application from manager application - while it reloading try to reload the http://localhost:8080/ServletRestartTest/ServletRestartTest url. - You will get a 404 error page -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-133) Servlet mapping to / does not work
[
https://issues.apache.org/jira/browse/MTOMCAT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246186#comment-13246186
]
Gildas Cuisinier commented on MTOMCAT-133:
--
I try to map servlet to / in web.xml, that works.
For information, in Spring documentation, you have this quote :
{quote}
Mapping to '/' under Tomcat
Apache Tomcat maps its internal DefaultServlet to /, and on Tomcat versions
= 7.0.14, this servlet mapping cannot be overridden programmatically. 7.0.15
fixes this issue. Overriding the / servlet mapping has also been tested
successfully under GlassFish 3.1.
{quote}
The related issue in tomcat :
https://issues.apache.org/bugzilla/show_bug.cgi?id=51278
Servlet mapping to / does not work
-
Key: MTOMCAT-133
URL: https://issues.apache.org/jira/browse/MTOMCAT-133
Project: Apache Tomcat Maven Plugin
Issue Type: Bug
Components: tomcat7
Affects Versions: 2.0
Environment: Mac OS X, Apple JRE 1.6
Reporter: Gildas Cuisinier
Assignee: Olivier Lamy (*$^¨%`£)
Using the Servlet 3.0 possibilities to add and configure servlet
(ServletContainerInitializer through Spring 3.1 WebApplicationInitializer), I
try to map a servlet /, but is not working properly.
The servlet is started correctly, but the mapping does not work.
If I replace / by test/*, everything work perfectly.
For information, the / mapping works well in a standalone tomcat 7.0.25.
I put a sample project on github that reproduce the bug :
https://github.com/hikage/tomcat7-bug
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Issue Comment Edited] (MTOMCAT-133) Servlet mapping to / does not work
[
https://issues.apache.org/jira/browse/MTOMCAT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246186#comment-13246186
]
Gildas Cuisinier edited comment on MTOMCAT-133 at 4/4/12 11:44 AM:
---
I try to map servlet to / in web.xml, that works.
For information, in Spring documentation, you have this quote :
Mapping to '/' under Tomcat
Apache Tomcat maps its internal DefaultServlet to /, and on Tomcat versions
= 7.0.14, this servlet mapping cannot be overridden programmatically. 7.0.15
fixes this issue. Overriding the / servlet mapping has also been tested
successfully under GlassFish 3.1.
The related issue in tomcat :
https://issues.apache.org/bugzilla/show_bug.cgi?id=51278
was (Author: gcuisinier):
I try to map servlet to / in web.xml, that works.
For information, in Spring documentation, you have this quote :
{quote}
Mapping to '/' under Tomcat
Apache Tomcat maps its internal DefaultServlet to /, and on Tomcat versions
= 7.0.14, this servlet mapping cannot be overridden programmatically. 7.0.15
fixes this issue. Overriding the / servlet mapping has also been tested
successfully under GlassFish 3.1.
{quote}
The related issue in tomcat :
https://issues.apache.org/bugzilla/show_bug.cgi?id=51278
Servlet mapping to / does not work
-
Key: MTOMCAT-133
URL: https://issues.apache.org/jira/browse/MTOMCAT-133
Project: Apache Tomcat Maven Plugin
Issue Type: Bug
Components: tomcat7
Affects Versions: 2.0
Environment: Mac OS X, Apple JRE 1.6
Reporter: Gildas Cuisinier
Assignee: Olivier Lamy (*$^¨%`£)
Using the Servlet 3.0 possibilities to add and configure servlet
(ServletContainerInitializer through Spring 3.1 WebApplicationInitializer), I
try to map a servlet /, but is not working properly.
The servlet is started correctly, but the mapping does not work.
If I replace / by test/*, everything work perfectly.
For information, the / mapping works well in a standalone tomcat 7.0.25.
I put a sample project on github that reproduce the bug :
https://github.com/hikage/tomcat7-bug
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53034] New: apache tomcat deployed pom does not contain url or license
https://issues.apache.org/bugzilla/show_bug.cgi?id=53034 Bug #: 53034 Summary: apache tomcat deployed pom does not contain url or license Product: Tomcat 7 Version: 7.0.26 Platform: PC OS/Version: Linux Status: NEW Severity: trivial Priority: P2 Component: Packaging AssignedTo: dev@tomcat.apache.org ReportedBy: jie...@gmail.com Classification: Unclassified Even though Apache Tomcat doesn't manage itself with Apache Maven, it is really great that the project deploys artifacts for user consumption. Unfortunately, these artifacts are missing some important pieces of information that are really important for working in big organizations: there is no project.url defined, and there is no project.licenses section. Adding both of these would play nicely in automated systems which need to have that license available to produce a proper Bill of Materials. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53033] Cannot undeploy applications
https://issues.apache.org/bugzilla/show_bug.cgi?id=53033 duc nguyen ducnvlo...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Comment #2 from duc nguyen ducnvlo...@gmail.com 2012-04-04 13:15:53 UTC --- (In reply to comment #1) Bugzilla is not a support forum. Hi. I know this not a support forum. Just want to report a bug and if someone had this issue before can tell me how to solve it. That's it. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53033] Cannot undeploy applications
https://issues.apache.org/bugzilla/show_bug.cgi?id=53033 Chuck Caldarale chuck.caldar...@unisys.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Comment #3 from Chuck Caldarale chuck.caldar...@unisys.com 2012-04-04 14:06:20 UTC --- (In reply to comment #2) (In reply to comment #1) I know this not a support forum. Then stop trying to use it as such. If you have an issue to discuss, bring it up on the users mailing list, not bugzilla. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-133) Servlet mapping to / does not work
[ https://issues.apache.org/jira/browse/MTOMCAT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246314#comment-13246314 ] Gildas Cuisinier commented on MTOMCAT-133: -- Here is new information to solve this bug: The code to add mapping : ServletRegistration.Dynamic myServlet = servletContext.addServlet(//); SetString conflicts = myServlet.addMapping(/); In Tomcat 7 standalone, the conflits set is empty. In Maven Tomcat 7 plugin, the conflicts set contains the String /. I investigate, and one difference I found is that the Wrapper for the jsp servlet and the default servlet is overridable in tomcat 7 but not in maven plugin context. Servlet mapping to / does not work - Key: MTOMCAT-133 URL: https://issues.apache.org/jira/browse/MTOMCAT-133 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat7 Affects Versions: 2.0 Environment: Mac OS X, Apple JRE 1.6 Reporter: Gildas Cuisinier Assignee: Olivier Lamy (*$^¨%`£) Using the Servlet 3.0 possibilities to add and configure servlet (ServletContainerInitializer through Spring 3.1 WebApplicationInitializer), I try to map a servlet /, but is not working properly. The servlet is started correctly, but the mapping does not work. If I replace / by test/*, everything work perfectly. For information, the / mapping works well in a standalone tomcat 7.0.25. I put a sample project on github that reproduce the bug : https://github.com/hikage/tomcat7-bug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53032] Ant Jasper task fails to run when using XML namespaces; no output; no errors
https://issues.apache.org/bugzilla/show_bug.cgi?id=53032 --- Comment #2 from Nick Williams nicho...@nicholaswilliams.net 2012-04-04 15:18:54 UTC --- Since JspC is the only Tomcat Ant task that doesn't work with namespaces, and JspC is also the only Tomcat Ant task that /doesn't/ extend o.a.tools.ant.Task, it seems likely that is the culprit. I don't know this for sure, but from my initial examination of all of the code involved, it appears that is the case. JspC doesn't extend or implement /any/ Ant classes. As far as Ant goes, it appears to purely be a hacked-together class that just happens to implement the minimum methods that Ant expects a task to implement, and this can run as a task. But it is not, as for as Ant is concerned, an actual Task. It seems very unlikely that something other than this fact is causing this issue. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.27
[X] Stable - go ahead and release as 7.0.27 Stable - Original Message - From: Mark Thomas ma...@apache.org To: Tomcat Developers List dev@tomcat.apache.org Sent: Saturday, March 31, 2012 11:07:30 AM Subject: [VOTE] Release Apache Tomcat 7.0.27 The proposed Apache Tomcat 7.0.27 release is now available for voting. It can be obtained from: https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.27/ The Maven staging repo is: https://repository.apache.org/content/repositories/orgapachetomcat-132/ The svn tag is: http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_27/ The proposed 7.0.27 release is: [ ] Broken - do not release [ ] Stable - go ahead and release as 7.0.27 Stable Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1307093 - /tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
- Original Message -
From: ma...@apache.org
To: dev@tomcat.apache.org
Sent: Thursday, March 29, 2012 2:19:18 PM
Subject: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
Author: markt
Date: Thu Mar 29 20:19:18 2012
New Revision: 1307093
@Override
-public Object invoke(Object proxy, Method method, Object[] args)
throws Throwable {
+public Object invoke(Object proxy, Method method, Object[] args)
+throws Throwable {
Can we change the line length to something more modern than our 1980s monitors
that were limited to 80 characters.
In today's environment, 80 characters is like your chat window, surely we can
go 120 or 150 and get way more readable code
Filip
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Who wants my Cassandra session manager for Tomcat?
Thanks again for your comments. More replies below: That's interesting. Can you share some details about how it works? Sure. It is quite simple. Cassandra is effectively a multi-level distributed hash-map, so it lends itself very well do storing session attributes. The session manager maintains two column families (like tables), one to hold session meta-data such as the last access timestamp, etc. and one column family to hold session attributes. Storing or reading a session attribute is simply a matter of writing it using the session ID as the row ID, and the session attribute name as the column name, and the session attribute value as the column value. Session attributes are read and written independently, so the entire web session does not have to be loaded into memory - only the session attributes that are actually required to service a request are read. This greatly reduces the memory footprint of the web applications that I am developing for my employer. I'd be concerned about how chatty that was. Devil's advocate question: why store data in the session if it's not needed? Good question. For large web applications, and particularly web-based UIs with multiple user screens, you would have certain data in your session for the various screens/pages. Not all pages need _all_ data in your session, and since the session manager loads session attributes only when the web app code asks for it, only the data that is required for the current page is loaded from Cassandra. For improved performance I have added a write-through and a write-back cache, implemented as servlet filters. The cache is flushed or written back once the current request has finished processing. I am sure there is room for improvement here, as multiple concurrent requests for the same session should be served using the same cache instance. But... (more devil's advocating, sorry) while this should address the chattiness* problem, doesn't it mean that your solution is invasive and can't be really deployed without modifying an app? The session manager works without this cache, but is slow. The cache is configured as a filter configured in web.xml. The code of a web app won't have to be changed, but you need to update your web.xml to use the session manager effectively. * is that even a word? Yes it is, according to dictionary.com The Manager does not maintain any references to Session instances at all, allowing them to be garbage collected at any time. This makes things very simple, as Cassandra holds all session state, and the session managers in my Tomcat nodes only act as a cache in front of Cassandra. The nature of Cassandra and the Tomcat's implementation of web sessions go together extremely well. I am surprised that nothing like this exists already. It is a square hole, square peg sort of scenario. I'm not entirely sure I agree. Cassandra trades off consistency for availability and partition tolerance, whereas I'd suggest a session management solution would want to trade partition tolerance for consistency and availability. I'm also not sure that the comparison between column store and session attribute map stands up beyond the initial/apparent similarity between data type. Cassandra is write-optimised and hits disk (on at least two nodes for HA) for every write AFAIK. Cassandra allows you choose your consistency level. I use a quorum write, which writes to (N/2)+1 Cassandra nodes, where the Cassandra ring contains N nodes. I think this makes sense for web session data, and my current implementation has this consistency-level hard-coded. I think it would probably make sense to allow this to be configured. I also have an implementation of the Map interface that stores the values of each entry as a session attribute. The way many developers write web applications is to have a session bean (a session attribute) that contains a Map that maintains the actual session attributes. This is OK if the entire session is persisted as a whole, but it won't perform very well with the Cassandra session manager (or the Delta Session Manager from what I understand). A developer can replace their session bean's HashMap with the SessionMap utility, and the session attributes will be treated as proper session attributes by the session manager. Is there not a way to do this internally therefore transparently to the developer? Otherwise you're introducing more dependencies and creating more of a framework than a pluggable manager. I don't think there is a clean way of doing this without overriding the default Map implementations of the JVM. But, I think storing session data as individual session attributes rather than large object hierarchies is good (but not common) programming practice. It allows the session container/manager to manage read/write operations of the session attributes separately. This practice should benefit not only my Cassandra session manager but also the existing Delta manager. 1. Be
Re: svn commit: r1307093 - /tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
On 04/04/2012 17:12, Filip Hanik Mailing Lists wrote:
- Original Message -
From: ma...@apache.org To: dev@tomcat.apache.org Sent: Thursday,
March 29, 2012 2:19:18 PM Subject: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
Author: markt
Date: Thu Mar 29 20:19:18 2012 New Revision: 1307093
@Override -public Object invoke(Object proxy, Method method,
Object[] args) throws Throwable { +public Object invoke(Object
proxy, Method method, Object[] args) +throws Throwable
{
Can we change the line length to something more modern than our 1980s
monitors that were limited to 80 characters. In today's environment,
80 characters is like your chat window, surely we can go 120 or 150
and get way more readable code
If I was going to dedicate my whole screen to the code pane then yes,
but there are other useful panes I want to see as well. 80 chars is
about right for the code window (and the line length we generally stick
to throughout the Tomcat code base).
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[RESULT][VOTE] Release Apache Tomcat 7.0.27
This vote passes. The votes were as follows: +1: markt (binding) rjung (binding) olamy (binding) kkolinko (binding) schultz fhanik (binding) I'll move the files to /dist, give the mirrors time to sync and then announce the release. Might happen later tonight, might be tomorrow. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r598 - /dev/tomcat/tomcat-7/v7.0.27/ /release/tomcat/tomcat-7/v7.0.27/
Author: markt Date: Wed Apr 4 17:27:14 2012 New Revision: 598 Log: Release Apache Tomcat 7.0.27 Added: release/tomcat/tomcat-7/v7.0.27/ - copied from r597, dev/tomcat/tomcat-7/v7.0.27/ Removed: dev/tomcat/tomcat-7/v7.0.27/ - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r598 - /dev/tomcat/tomcat-7/v7.0.27/ /release/tomcat/tomcat-7/v7.0.27/
Author: markt Date: Wed Apr 4 17:27:14 2012 New Revision: 598 Log: Release Apache Tomcat 7.0.27 Added: release/tomcat/tomcat-7/v7.0.27/ - copied from r597, dev/tomcat/tomcat-7/v7.0.27/ Removed: dev/tomcat/tomcat-7/v7.0.27/ - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1307093 - /tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
- Original Message -
From: Mark Thomas ma...@apache.org
To: Tomcat Developers List dev@tomcat.apache.org
Sent: Wednesday, April 4, 2012 11:18:42 AM
Subject: Re: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
On 04/04/2012 17:12, Filip Hanik Mailing Lists wrote:
- Original Message -
From: ma...@apache.org To: dev@tomcat.apache.org Sent: Thursday,
March 29, 2012 2:19:18 PM Subject: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
Author: markt
Date: Thu Mar 29 20:19:18 2012 New Revision: 1307093
@Override -public Object invoke(Object proxy, Method method,
Object[] args) throws Throwable { +public Object invoke(Object
proxy, Method method, Object[] args) +throws Throwable
{
Can we change the line length to something more modern than our
1980s
monitors that were limited to 80 characters. In today's
environment,
80 characters is like your chat window, surely we can go 120 or 150
and get way more readable code
If I was going to dedicate my whole screen to the code pane then yes,
whole screen can probably fit 300+ characters, so were not talking whole screen.
80 is so tiny that it takes up a quarter of my screen or less.
I would therefor suggest to increase this, as it will dramatically shrink the
number of lines of code, and readability
but there are other useful panes I want to see as well. 80 chars is
about right for the code window (and the line length we generally
stick
to throughout the Tomcat code base).
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1307093 - /tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
2012/4/4 Filip Hanik Mailing Lists devli...@hanik.com:
- Original Message -
From: Mark Thomas ma...@apache.org
To: Tomcat Developers List dev@tomcat.apache.org
Sent: Wednesday, April 4, 2012 11:18:42 AM
Subject: Re: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
On 04/04/2012 17:12, Filip Hanik Mailing Lists wrote:
- Original Message -
From: ma...@apache.org To: dev@tomcat.apache.org Sent: Thursday,
March 29, 2012 2:19:18 PM Subject: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
Author: markt
Date: Thu Mar 29 20:19:18 2012 New Revision: 1307093
@Override - public Object invoke(Object proxy, Method method,
Object[] args) throws Throwable { + public Object invoke(Object
proxy, Method method, Object[] args) + throws Throwable
{
Can we change the line length to something more modern than our
1980s
monitors that were limited to 80 characters. In today's
environment,
80 characters is like your chat window, surely we can go 120 or 150
and get way more readable code
If I was going to dedicate my whole screen to the code pane then yes,
whole screen can probably fit 300+ characters, so were not talking whole
screen.
80 is so tiny that it takes up a quarter of my screen or less.
I would therefor suggest to increase this, as it will dramatically shrink the
number of lines of code, and readability
I know of two places where long lines cause problems:
1. Commit e-mails.
Long lines are wrapped and it impacts readability.
2. Side-by-side comparison in viewvc when you do colored comparison
Therefore I would like to stick to the current convention of 80 chars.
It is not a hard convention (we do not enforce it through checkstyle),
but something to follow.
There should be several previous discussions on this topic in the archives...
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Registering Filters via API: isMatchAfter behaves weird
Hello, I came across weird behavior using the JEE Servlet 3.0 API for adding Filters with Tomcat 7.0.26 When I map two filters on the same URL and I use the isMatchAfter attribute I would expect the filter having isMatchAfter set to true to be invoked last. For example: FilterRegistration.Dynamic registration1 = servletContext.addFilter(filter1, new Filter1()); registration1.addMappingForUrlPatterns(null, true, /Filter); FilterRegistration.Dynamic registration2 = servletContext.addFilter(filter2, new Filter2()); registration2.addMappingForUrlPatterns(null, false, /Filter); Filter1 prints Filter1 to console when invoked, Filter2 prints Filter2 to console when invoked. The isMatchAfter of filter one is set to true, which should mean it should be invoked last when another filter is mapped on the same URL. So I would expect that filter one is invoked AFTER filter two. This seems to be inversed, Tomcat output: Filter1 Filter2 I verified the example but with Glassfish 3.1.1 and this one delivered the results as expected; INFO: Filter2 INFO: Filter1 The flag does seem to have impact, because if I switch it: I set isMatchAfter to false on filter one and isMatchAfter to true on filter 2 I get this with tomcat: Filter2 Filter1 So it looks like this flag was miss interpreted somehow and treated as a isMatchBefore. Thanks, Koen.
[Tomcat Wiki] Update of PoweredBy by Voicent
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Tomcat Wiki for change
notification.
The PoweredBy page has been changed by Voicent:
http://wiki.apache.org/tomcat/PoweredBy?action=diffrev1=401rev2=402
This section contains cases added by users without further external
information, or found on the [[http://tomcat.apache.org/lists.html|Tomcat
mailing lists]].
=== 3ware ===
- {{http://www.3ware.it/img/logo/logo.png}} [[http://www.3ware.it|3ware]] is a
software house specialized in web based application.
- {{http://www.3ware.it/img/logo/g.PRO-medium.png}}
[[http://www.3ware.it/gestionale_g.pro.html|g•PRO]] is our framework based on
pure HTML5/CSS3 standards for the client side and on Java/J2EE for the server
side, proudly running on Tomcat application server.
+ {{http://www.3ware.it/img/logo/logo.png}} [[http://www.3ware.it|3ware]] is a
software house specialized in web based application.
{{http://www.3ware.it/img/logo/g.PRO-medium.png}}
[[http://www.3ware.it/gestionale_g.pro.html|g•PRO]] is our framework based on
pure HTML5/CSS3 standards for the client side and on Java/J2EE for the server
side, proudly running on Tomcat application server.
=== AccesStream ===
{{http://www.accesstream.com/templates/accesstream/images/accesstream_header_logo.gif}}
[[http://www.accesstream.com|AccesStream]] is an open-source Identity and
Access Management suite.
@@ -307, +306 @@
[[http://www.orangepics.com|www.orangepics.com]] - Simple, Safe Photo Sharing
=== PC Gesund ===
- {{http://www.pcgesund.de/_content/about/img/screens/logo_small.png}}
[[http://www.pcgesund.de]] - PC Gesund is the leading remote support computer
helpdesk in Germany.
+ {{http://www.pcgesund.de/_content/about/img/screens/logo_small.png}}
http://www.pcgesund.de - PC Gesund is the leading remote support computer
helpdesk in Germany.
=== Popcorn Monsters ===
{{http://popcornmonsters.com/images/logo_1.jpg}}
[[http://PopcornMonsters.com|PopcornMonsters.com]] - A free movie information
portal that averages 100,000 unique visitors a month.
@@ -389, +388 @@
=== Virtual Pair Programmers ===
{{https://www.virtualpairprogrammers.com/img/logo.gif}}
[[http://www.virtualpairprogrammers.com|VirtualPairProgrammers]] - power their
E-Commerce operation on Tomcat.
+
+ === Voicent Communications ===
+ {{http://www.voicent.com/images/voicent.jpg}} [[http://www.voicnt.com|Voicent
Communications]] - Communication tools for sales, marketing, customer service,
call centers, appointment reminder, and much more; built on Tomcat.
=== Volagratis.it ===
[[http://www.volagratis.com/vg1/home.do?utm_source=VGutm_medium=TOMutm_campaign=1|Volagratis.it]]
is an E-Commerce site.
@@ -419, +421 @@
[[http://www.a2hosting.com/|A2 Hosting]] -
[[http://www.a2hosting.com/server-software/tomcat-hosting|Tomcat Hosting]] is
available on CentOS, Debian, Fedora or Ubuntu VPS packages. Install Tomcat in
moments with A2 Hosting's exclusive Quickinstaller tool.
=== AcuGIS Hosting ===
-
{{http://www.acugis.com/images/logo.png}}
[[http://www.acugis.com/|AcuGIS]] Tomcat hosting solutions with emphasis on
GIS (GeoServer and PostGIS). Tomcat 6 and 7 options with private JVM. High
performance hosting with SAS 15k disks and 1 Gb public/private network on all
hosting plans.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1307093 - /tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
- Original Message -
From: Konstantin Kolinko knst.koli...@gmail.com
To: Tomcat Developers List dev@tomcat.apache.org
Sent: Wednesday, April 4, 2012 11:52:01 AM
Subject: Re: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
2012/4/4 Filip Hanik Mailing Lists devli...@hanik.com:
- Original Message -
From: Mark Thomas ma...@apache.org
To: Tomcat Developers List dev@tomcat.apache.org
Sent: Wednesday, April 4, 2012 11:18:42 AM
Subject: Re: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
On 04/04/2012 17:12, Filip Hanik Mailing Lists wrote:
- Original Message -
From: ma...@apache.org To: dev@tomcat.apache.org Sent:
Thursday,
March 29, 2012 2:19:18 PM Subject: svn commit: r1307093 -
/tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
Author: markt
Date: Thu Mar 29 20:19:18 2012 New Revision: 1307093
@Override - public Object invoke(Object proxy, Method
method,
Object[] args) throws Throwable { + public Object
invoke(Object
proxy, Method method, Object[] args) + throws
Throwable
{
Can we change the line length to something more modern than our
1980s
monitors that were limited to 80 characters. In today's
environment,
80 characters is like your chat window, surely we can go 120 or
150
and get way more readable code
If I was going to dedicate my whole screen to the code pane then
yes,
whole screen can probably fit 300+ characters, so were not talking
whole screen.
80 is so tiny that it takes up a quarter of my screen or less.
I would therefor suggest to increase this, as it will dramatically
shrink the number of lines of code, and readability
I know of two places where long lines cause problems:
1. Commit e-mails.
Long lines are wrapped and it impacts readability.
2. Side-by-side comparison in viewvc when you do colored comparison
here I see a challenge, since so many of our commits, are not code commits, but
like a line wrap commit like this,
this pollutes our diffs and why I'm not a big fan of changing it for changing
it.
Therefore I would like to stick to the current convention of 80
chars.
It is not a hard convention (we do not enforce it through
checkstyle),
but something to follow.
The convention is something fairly new. For most of the time of Tomcat's life
time, it was the committers preference, but fairly recently is when we started
modifying style for style's sake. So the archives you refer to, can't go that
far back. The only convention we've had through the history of Tomcat, is
spaces, not tabs, not line length etc.
There should be several previous discussions on this topic in the
archives...
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Trivial Update of PoweredBy by Voicent
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Tomcat Wiki for change
notification.
The PoweredBy page has been changed by Voicent:
http://wiki.apache.org/tomcat/PoweredBy?action=diffrev1=402rev2=403
=== PC Gesund ===
{{http://www.pcgesund.de/_content/about/img/screens/logo_small.png}}
http://www.pcgesund.de - PC Gesund is the leading remote support computer
helpdesk in Germany.
-
=== Popcorn Monsters ===
{{http://popcornmonsters.com/images/logo_1.jpg}}
[[http://PopcornMonsters.com|PopcornMonsters.com]] - A free movie information
portal that averages 100,000 unique visitors a month.
@@ -390, +389 @@
{{https://www.virtualpairprogrammers.com/img/logo.gif}}
[[http://www.virtualpairprogrammers.com|VirtualPairProgrammers]] - power their
E-Commerce operation on Tomcat.
=== Voicent Communications ===
- {{http://www.voicent.com/images/voicent.jpg}} [[http://www.voicnt.com|Voicent
Communications]] - Communication tools for sales, marketing, customer service,
call centers, appointment reminder, and much more; built on Tomcat.
+ {{http://www.voicent.com/images/voicent.jpg}} [[http://www.voicnt.com|Voicent
Communications]] - Voicent uses Tomcat to Power:
[[http://www.voicent.com/call-center-software.php|Call Center Manager]],
[[http://www.voicent.com/ivr.php|IVR Studio]], and
[[http://www.voicent.com/autodialers.php|BroadcastByPhone]], as well as many
other titles.
- === Volagratis.it ===
+ === Volagratis ===
[[http://www.volagratis.com/vg1/home.do?utm_source=VGutm_medium=TOMutm_campaign=1|Volagratis.it]]
is an E-Commerce site.
=== WebShots ===
@@ -421, +420 @@
[[http://www.a2hosting.com/|A2 Hosting]] -
[[http://www.a2hosting.com/server-software/tomcat-hosting|Tomcat Hosting]] is
available on CentOS, Debian, Fedora or Ubuntu VPS packages. Install Tomcat in
moments with A2 Hosting's exclusive Quickinstaller tool.
=== AcuGIS Hosting ===
+
+ /!\ '''Edit conflict - other version:'''
+
+ /!\ '''Edit conflict - your version:'''
+
+ /!\ '''End of edit conflict'''
+
+ /!\ '''Edit conflict - other version:'''
+
+ /!\ '''Edit conflict - your version:'''
+
+ === AcuGIS Hosting ===
+
+
+ /!\ '''End of edit conflict'''
{{http://www.acugis.com/images/logo.png}}
[[http://www.acugis.com/|AcuGIS]] Tomcat hosting solutions with emphasis on
GIS (GeoServer and PostGIS). Tomcat 6 and 7 options with private JVM. High
performance hosting with SAS 15k disks and 1 Gb public/private network on all
hosting plans.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: Improving Ant Task for JSP Compilation
-Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Monday, April 02, 2012 4:24 PM To: Tomcat Developers List Subject: Re: Improving Ant Task for JSP Compilation Nick, On 3/31/12 4:34 PM, Nick Williams wrote: This morning I filed issues 53011 and 53012, about general improvements to the Ant task used for compiling JSPs. These two issues are rather important to our team, and are making using the compiler rather difficult. In the interest of both improving Tomcat and meeting our needs as quickly as possible, I am interested in possibly contributing code changes to effect these improvements, and possible others. Great! I read the information at http://tomcat.apache.org/getinvolved.html and related links, and understand that my first step is building Tomcat and my second is proposing patches to the other developers (presumably by attaching them to the issues I filed). If I'm missing anything so far, please let me know. That sounds like a good start. Remember that everything you do should be in Tomcat's 'trunk'. Here's the svn root for that: http://svn.apache.org/repos/asf/tomcat/trunk All patches should be against trunk (they'll get back-ported to 7.0.x and possibly 6.0.x). What I'd really like is a little further guidance about this particular feature in Tomcat. Who is really familiar with it that I can ask questions of if I don't understand something I see? Perhaps the best thing to do is look at the svn history for the files involved. Start with org.apache.jasper.JspC and the related files like Compiler, etc. to see who has updated them recently. Mostly, it's best to ask questions on this list and let anyone answer them who can, rather than trying to directly contact any one person. What do the developers on the list think about the ideas proposed in these two issues? Bug 53011 - Ant Jasper task fails after one error +1 - seems reasonable. I've added some comments to the bug. Bug 53012 - Ant Jasper task does not name including file when included file has compile error +1 also seems reasonable. Check the current behavior of the trunk to make sure this isn't already in there. I believe they make Tomcat better, but that's just because they meet our immediate needs. That's host these projects grow: patches are always welcome. Basically anything that doesn't a) violate the servlet specification or b) significantly impact performance or c) require sweeping changes to the code is fair game. Thanks, -chris - Alright, I've analyzed the o.a.tools.ant.Task, o.a.tools.ant.taskdefs.Java, o.a.tools.ant.taskdefs.Javac, o.a.jasper.JspC, o.a.jasper.compiler.Compiler, and the classes in o.a.catalina.ant. I learned a lot ... in some cases more than I wanted to. ;-) Here are some of my observations: - JspC is the only Ant task in Tomcat that doesn't actually extend o.a.tools.ant.Task. All the other tasks extend Task, but not JspC. JspC just happens to implement enough methods that Ant will blindly execute it. This is likely the primary cause behind 53032. - JspC does a lot of things wrong for executing in Ant-world. I'm sure it's all perfectly right for its original intended purpose, but it's wrong in Ant-world. The way it logs, handles files and classpaths, etc. are all counter to standards used in Ant. The getFork() method it implements isn't even related to Ant; it's implementing the getFork() method in o.a.jasper.Options. This all makes 53011, 53012 and 53031 difficult (at best) to solve. - JspC is so tightly coupled with the other things in Tomcat that I believe it would be next to impossible to retrofit it to be a well-behaved Ant task. For that matter, I believe it would be next to impossible to even /use/ it in a new well-behaved Ant task. - I have not yet figured out exactly how compile errors are output to determine if 53012 is already fixed in trunk. I'm still investigating. With those, here are my general recommendations: - Create a new class o.a.catalina.ant.JspCompileTask extends o.a.catalina.ant.BaseRedirectionHelperTask (which extends o.a.tools.ant.Task). This class will do a lot of the same things that JspC does, but in a simpler way, making some assumptions because it knows that it's always running within an Ant project. It will still have most of the plethora of options that JspC has, such as compilerSourceVM, compile, getStringsAsCharArray, etc. It will accept a Classpath for use in the compilation phase of JSPs. It will fork upon request, but not by default, just like java/javac/junit. It will fail on error by default, but not required, and will have an errorProperty, just like java/javac/junit. It will fail only after all errors, just like java/javac/junit, but will have a failFast option to fail after a single error if desired (off by default). - Change o.a.jasper.compiler.Compiler to make the log field non-final and add a setter
[Tomcat Wiki] Update of PoweredBy by Voicent
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Tomcat Wiki for change
notification.
The PoweredBy page has been changed by Voicent:
http://wiki.apache.org/tomcat/PoweredBy?action=diffrev1=403rev2=404
=== PC Gesund ===
{{http://www.pcgesund.de/_content/about/img/screens/logo_small.png}}
http://www.pcgesund.de - PC Gesund is the leading remote support computer
helpdesk in Germany.
+
=== Popcorn Monsters ===
{{http://popcornmonsters.com/images/logo_1.jpg}}
[[http://PopcornMonsters.com|PopcornMonsters.com]] - A free movie information
portal that averages 100,000 unique visitors a month.
@@ -389, +390 @@
{{https://www.virtualpairprogrammers.com/img/logo.gif}}
[[http://www.virtualpairprogrammers.com|VirtualPairProgrammers]] - power their
E-Commerce operation on Tomcat.
=== Voicent Communications ===
- {{http://www.voicent.com/images/voicent.jpg}} [[http://www.voicnt.com|Voicent
Communications]] - Voicent uses Tomcat to Power:
[[http://www.voicent.com/call-center-software.php|Call Center Manager]],
[[http://www.voicent.com/ivr.php|IVR Studio]], and
[[http://www.voicent.com/autodialers.php|BroadcastByPhone]], as well as many
other titles.
+ {{http://www.voicent.com/images/voicent.jpg}} [[http://www.voicnt.com|Voicent
Communications]] - Voicent uses Tomcat to Power:
[[http://www.voicent.com/call-center-software.php|Call Center Software]],
[[http://www.voicent.com/ivr.php|IVR]], and
[[http://www.voicent.com/autodialers.php|Auto dialer]], as well as many other
titles.
=== Volagratis ===
[[http://www.volagratis.com/vg1/home.do?utm_source=VGutm_medium=TOMutm_campaign=1|Volagratis.it]]
is an E-Commerce site.
@@ -420, +421 @@
[[http://www.a2hosting.com/|A2 Hosting]] -
[[http://www.a2hosting.com/server-software/tomcat-hosting|Tomcat Hosting]] is
available on CentOS, Debian, Fedora or Ubuntu VPS packages. Install Tomcat in
moments with A2 Hosting's exclusive Quickinstaller tool.
=== AcuGIS Hosting ===
-
+
- /!\ '''Edit conflict - other version:'''
+ /!\ '''Edit conflict - other version:'''
+
+
+
- /!\ '''Edit conflict - your version:'''
+ /!\ '''Edit conflict - your version:'''
+
+
+
- /!\ '''End of edit conflict'''
+ /!\ '''End of edit conflict'''
+
+
+
- /!\ '''Edit conflict - other version:'''
+ /!\ '''Edit conflict - other version:'''
+
+
+
- /!\ '''Edit conflict - your version:'''
+ /!\ '''Edit conflict - your version:'''
+
+
=== AcuGIS Hosting ===
+
-
-
- /!\ '''End of edit conflict'''
+ /!\ '''End of edit conflict'''
+
+
{{http://www.acugis.com/images/logo.png}}
[[http://www.acugis.com/|AcuGIS]] Tomcat hosting solutions with emphasis on
GIS (GeoServer and PostGIS). Tomcat 6 and 7 options with private JVM. High
performance hosting with SAS 15k disks and 1 Gb public/private network on all
hosting plans.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 52791] [PATCH] read windows installer default values from config file
https://issues.apache.org/bugzilla/show_bug.cgi?id=52791
Sandra Madden smad...@vocera.com changed:
What|Removed |Added
Attachment #28399|0 |1
is obsolete||
--- Comment #3 from Sandra Madden smad...@vocera.com 2012-04-04 18:58:31 UTC
---
Created attachment 28543
-- https://issues.apache.org/bugzilla/attachment.cgi?id=28543
Rev2 of the patch to add config file support. Incorporated changes suggested by
Konstantin Kolinko
Thanks for the constructive feedback Konstantin. I changed the patch to only
read the ini file when it is passed in on the cmdline as /C=fully qualified
path to filename.
I also improved the way the macro/function hybrid to read the values is
written. I initially based it on sample code I found online, but now cleaned it
all up to have less clutter and match the needs of the tomcat installer better.
The patch is still not reading in the config file at once and parse it from
memory. I wanted to keep using the established macro ${ConfigRead} instead of
writing something new to minimize possible introduction of bugs.
-Sandra
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-134) Empty additionalClasspathDir causes NPE in RunMojo.java
Empty additionalClasspathDir causes NPE in RunMojo.java --- Key: MTOMCAT-134 URL: https://issues.apache.org/jira/browse/MTOMCAT-134 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat6, tomcat7 Affects Versions: 2.0-beta-1 Environment: plugin groupIdorg.apache.tomcat.maven/groupId artifactIdtomcat7-maven-plugin/artifactId version2.0-SNAPSHOT/version configuration port9090/port path/myapp-1.0/path !--contextFile/contextFile-- systemProperties/systemProperties useTestClasspathfalse/useTestClasspath additionalClasspathDirs additionalClasspathDir/additionalClasspathDir /additionalClasspathDirs /configuration executions execution idtomcat-run/id goals goalexec-war-only/goal /goals phasepackage/phase configuration path/myapp-1.0/path /configuration /execution /executions /plugin Reporter: John Meyer Assignee: Olivier Lamy (*$^¨%`£) Priority: Minor Hit an issue where specifying an empty additionalClasspathDir caused a mysterious NPE and no explaination of what was wrong -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-134) Empty additionalClasspathDir causes NPE in RunMojo.java
[ https://issues.apache.org/jira/browse/MTOMCAT-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Meyer updated MTOMCAT-134: --- Attachment: MTOMCAT-134.diff Proposed fix Empty additionalClasspathDir causes NPE in RunMojo.java --- Key: MTOMCAT-134 URL: https://issues.apache.org/jira/browse/MTOMCAT-134 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat6, tomcat7 Affects Versions: 2.0-beta-1 Environment: plugin groupIdorg.apache.tomcat.maven/groupId artifactIdtomcat7-maven-plugin/artifactId version2.0-SNAPSHOT/version configuration port9090/port path/myapp-1.0/path !--contextFile/contextFile-- systemProperties/systemProperties useTestClasspathfalse/useTestClasspath additionalClasspathDirs additionalClasspathDir/additionalClasspathDir /additionalClasspathDirs /configuration executions execution idtomcat-run/id goals goalexec-war-only/goal /goals phasepackage/phase configuration path/myapp-1.0/path /configuration /execution /executions /plugin Reporter: John Meyer Assignee: Olivier Lamy (*$^¨%`£) Priority: Minor Attachments: MTOMCAT-134.diff Hit an issue where specifying an empty additionalClasspathDir caused a mysterious NPE and no explaination of what was wrong -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-134) Empty additionalClasspathDir causes NPE in RunMojo.java
[ https://issues.apache.org/jira/browse/MTOMCAT-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MTOMCAT-134: --- Fix Version/s: 2.0 Empty additionalClasspathDir causes NPE in RunMojo.java --- Key: MTOMCAT-134 URL: https://issues.apache.org/jira/browse/MTOMCAT-134 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat6, tomcat7 Affects Versions: 2.0-beta-1 Environment: plugin groupIdorg.apache.tomcat.maven/groupId artifactIdtomcat7-maven-plugin/artifactId version2.0-SNAPSHOT/version configuration port9090/port path/myapp-1.0/path !--contextFile/contextFile-- systemProperties/systemProperties useTestClasspathfalse/useTestClasspath additionalClasspathDirs additionalClasspathDir/additionalClasspathDir /additionalClasspathDirs /configuration executions execution idtomcat-run/id goals goalexec-war-only/goal /goals phasepackage/phase configuration path/myapp-1.0/path /configuration /execution /executions /plugin Reporter: John Meyer Assignee: Olivier Lamy (*$^¨%`£) Priority: Minor Fix For: 2.0 Attachments: MTOMCAT-134.diff Hit an issue where specifying an empty additionalClasspathDir caused a mysterious NPE and no explaination of what was wrong -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1309560 - in /tomcat/maven-plugin/trunk: tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/
Author: olamy
Date: Wed Apr 4 19:31:33 2012
New Revision: 1309560
URL: http://svn.apache.org/viewvc?rev=1309560view=rev
Log:
[MTOMCAT-134] Empty additionalClasspathDir causes NPE in RunMojo.java
Submitted by John Meyer.
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java?rev=1309560r1=1309559r2=1309560view=diff
==
---
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
(original)
+++
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
Wed Apr 4 19:31:33 2012
@@ -23,6 +23,7 @@ import org.apache.catalina.Context;
import org.apache.catalina.loader.WebappLoader;
import org.apache.catalina.startup.Embedded;
import org.apache.commons.io.FileUtils;
+import org.apache.commons.lang.StringUtils;
import org.apache.maven.artifact.Artifact;
import org.apache.maven.plugin.MojoExecutionException;
import org.apache.tomcat.maven.common.run.ClassLoaderEntriesCalculator;
@@ -48,7 +49,7 @@ import java.util.Set;
*
* @author Jurgen Lust
* @author Mark Hobson markhob...@gmail.com
- * @version $Id: RunMojo.java 13551 2011-02-09 16:05:47Z olamy $
+ * @version $Id$
* @goal run
* @execute phase=compile
* @requiresDependencyResolution test
@@ -204,13 +205,16 @@ public class RunMojo
{
for ( String additionalClasspathDir : additionalClasspathDirs )
{
-File file = new File( additionalClasspathDir );
-if ( file.exists() )
-{
-String fileUri = file.toURI().toString();
-getLog().debug( add file: + fileUri + as a
additionalClasspathDir );
-loader.addRepository( fileUri );
-}
+ if( StringUtils.isNotBlank(additionalClasspathDir))
+ {
+ File file = new File( additionalClasspathDir );
+ if ( file.exists() )
+ {
+ String fileUri = file.toURI().toString();
+ getLog().debug( add file: + fileUri + as a
additionalClasspathDir );
+ loader.addRepository( fileUri );
+ }
+ }
}
}
}
Modified:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java?rev=1309560r1=1309559r2=1309560view=diff
==
---
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java
(original)
+++
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java
Wed Apr 4 19:31:33 2012
@@ -20,6 +20,7 @@ package org.apache.tomcat.maven.plugin.t
import org.apache.catalina.loader.WebappLoader;
import org.apache.commons.io.FileUtils;
+import org.apache.commons.lang.StringUtils;
import org.apache.maven.artifact.Artifact;
import org.apache.maven.plugin.MojoExecutionException;
import org.apache.tomcat.maven.common.run.ClassLoaderEntriesCalculator;
@@ -265,13 +266,16 @@ public class RunMojo
{
for ( String additionalClasspathDir : additionalClasspathDirs )
{
-File file = new File( additionalClasspathDir );
-if ( file.exists() )
-{
-String fileUri = file.toURI().toString();
-getLog().debug( add file: + fileUri + as a
additionalClasspathDir );
-loader.addRepository( fileUri );
-}
+ if( StringUtils.isNotBlank(additionalClasspathDir))
+ {
+ File file = new File( additionalClasspathDir );
+ if ( file.exists() )
+ {
+ String fileUri = file.toURI().toString();
+ getLog().debug( add file: + fileUri + as a
additionalClasspathDir );
+
[jira] [Closed] (MTOMCAT-134) Empty additionalClasspathDir causes NPE in RunMojo.java
[ https://issues.apache.org/jira/browse/MTOMCAT-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-134. -- Resolution: Fixed patch applied. Thanks! Empty additionalClasspathDir causes NPE in RunMojo.java --- Key: MTOMCAT-134 URL: https://issues.apache.org/jira/browse/MTOMCAT-134 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat6, tomcat7 Affects Versions: 2.0-beta-1 Environment: plugin groupIdorg.apache.tomcat.maven/groupId artifactIdtomcat7-maven-plugin/artifactId version2.0-SNAPSHOT/version configuration port9090/port path/myapp-1.0/path !--contextFile/contextFile-- systemProperties/systemProperties useTestClasspathfalse/useTestClasspath additionalClasspathDirs additionalClasspathDir/additionalClasspathDir /additionalClasspathDirs /configuration executions execution idtomcat-run/id goals goalexec-war-only/goal /goals phasepackage/phase configuration path/myapp-1.0/path /configuration /execution /executions /plugin Reporter: John Meyer Assignee: Olivier Lamy (*$^¨%`£) Priority: Minor Fix For: 2.0 Attachments: MTOMCAT-134.diff Hit an issue where specifying an empty additionalClasspathDir caused a mysterious NPE and no explaination of what was wrong -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-134) Empty additionalClasspathDir causes NPE in RunMojo.java
[ https://issues.apache.org/jira/browse/MTOMCAT-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246647#comment-13246647 ] Hudson commented on MTOMCAT-134: Integrated in TomcatMavenPlugin-mvn3.x #120 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/120/]) [MTOMCAT-134] Empty additionalClasspathDir causes NPE in RunMojo.java Submitted by John Meyer. (Revision 1309560) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=revrev=1309560 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java Empty additionalClasspathDir causes NPE in RunMojo.java --- Key: MTOMCAT-134 URL: https://issues.apache.org/jira/browse/MTOMCAT-134 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat6, tomcat7 Affects Versions: 2.0-beta-1 Environment: plugin groupIdorg.apache.tomcat.maven/groupId artifactIdtomcat7-maven-plugin/artifactId version2.0-SNAPSHOT/version configuration port9090/port path/myapp-1.0/path !--contextFile/contextFile-- systemProperties/systemProperties useTestClasspathfalse/useTestClasspath additionalClasspathDirs additionalClasspathDir/additionalClasspathDir /additionalClasspathDirs /configuration executions execution idtomcat-run/id goals goalexec-war-only/goal /goals phasepackage/phase configuration path/myapp-1.0/path /configuration /execution /executions /plugin Reporter: John Meyer Assignee: Olivier Lamy (*$^¨%`£) Priority: Minor Fix For: 2.0 Attachments: MTOMCAT-134.diff Hit an issue where specifying an empty additionalClasspathDir caused a mysterious NPE and no explaination of what was wrong -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-133) Servlet mapping to / does not work
[ https://issues.apache.org/jira/browse/MTOMCAT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1324#comment-1324 ] Gildas Cuisinier commented on MTOMCAT-133: -- The difference comes from the declaration of default servlets. In the plugin, the declaration is made into Tomcat class, in the method initWebappDefaults. Wrapper servlet = addServlet( ctx, default, org.apache.catalina.servlets.DefaultServlet); servlet.setLoadOnStartup(1); // JSP servlet (by class name - to avoid loading all deps) servlet = addServlet( ctx, jsp, org.apache.jasper.servlet.JspServlet); servlet.addInitParameter(fork, false); servlet.setLoadOnStartup(3) And in this way, the wrapper is not set as overridable. Servlet mapping to / does not work - Key: MTOMCAT-133 URL: https://issues.apache.org/jira/browse/MTOMCAT-133 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat7 Affects Versions: 2.0 Environment: Mac OS X, Apple JRE 1.6 Reporter: Gildas Cuisinier Assignee: Olivier Lamy (*$^¨%`£) Using the Servlet 3.0 possibilities to add and configure servlet (ServletContainerInitializer through Spring 3.1 WebApplicationInitializer), I try to map a servlet /, but is not working properly. The servlet is started correctly, but the mapping does not work. If I replace / by test/*, everything work perfectly. For information, the / mapping works well in a standalone tomcat 7.0.25. I put a sample project on github that reproduce the bug : https://github.com/hikage/tomcat7-bug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1307093 - /tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DisposableConnectionFacade.java
2012/4/4 Filip Hanik Mailing Lists devli...@hanik.com: I know of two places where long lines cause problems: 1. Commit e-mails. Long lines are wrapped and it impacts readability. 2. Side-by-side comparison in viewvc when you do colored comparison here I see a challenge, since so many of our commits, are not code commits, but like a line wrap commit like this, this pollutes our diffs and why I'm not a big fan of changing it for changing it. I do not remember many line-wrap commits. There are ending whitespace commits, because sometimes people forget to run checkstyle and we would be nagged if someone does not fix the code. Therefore I would like to stick to the current convention of 80 chars. It is not a hard convention (we do not enforce it through checkstyle), but something to follow. The convention is something fairly new. For most of the time of Tomcat's life time, it was the committers preference, but fairly recently is when we started modifying style for style's sake. So the archives you refer to, can't go that far back. The only convention we've had through the history of Tomcat, is spaces, not tabs, not line length etc. a. I might be not very careful in selecting English words. Please excuse me. b. I do not see much difference between convention and preference. If it is a preference of many then it has to be respected as a convention. Isn't it? Previous discussion (December 2010): http://markmail.org/thread/alo77qd4yiduvqvz We also have this description of our coding style: http://tomcat.apache.org/getinvolved.html#Coding_Conventions Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1309603 - /tomcat/maven-plugin/trunk/pom.xml
Author: olamy Date: Wed Apr 4 21:23:49 2012 New Revision: 1309603 URL: http://svn.apache.org/viewvc?rev=1309603view=rev Log: use tomcat 7.0.27 artifacts Modified: tomcat/maven-plugin/trunk/pom.xml Modified: tomcat/maven-plugin/trunk/pom.xml URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/pom.xml?rev=1309603r1=1309602r2=1309603view=diff == --- tomcat/maven-plugin/trunk/pom.xml (original) +++ tomcat/maven-plugin/trunk/pom.xml Wed Apr 4 21:23:49 2012 @@ -66,8 +66,7 @@ its.ajp.port2001/its.ajp.port !-- server port for it tests -- its.server.port2008/its.server.port -!-- 7.0.26 issue see https://issues.apache.org/bugzilla/show_bug.cgi?id=52833 -- -tomcat7Version7.0.25/tomcat7Version +tomcat7Version7.0.27/tomcat7Version /properties prerequisites - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Who wants my Cassandra session manager for Tomcat?
Pid, On 4/4/12 6:46 AM, Pid wrote: On 03/04/2012 22:18, Morten Jorgensen wrote: Thanks to all for your feedback. I am providing some additional information as requested: That's interesting. Can you share some details about how it works? Sure. It is quite simple. Cassandra is effectively a multi-level distributed hash-map, so it lends itself very well do storing session attributes. The session manager maintains two column families (like tables), one to hold session meta-data such as the last access timestamp, etc. and one column family to hold session attributes. Storing or reading a session attribute is simply a matter of writing it using the session ID as the row ID, and the session attribute name as the column name, and the session attribute value as the column value. Session attributes are read and written independently, so the entire web session does not have to be loaded into memory - only the session attributes that are actually required to service a request are read. This greatly reduces the memory footprint of the web applications that I am developing for my employer. I'd be concerned about how chatty that was. Devil's advocate question: why store data in the session if it's not needed? Honestly, I was thinking the same thing today: usually, non-memory-based data management is usually done in such a way as to be completely divorced from the HttpSession concept, anyway. One needs to use HttpSession for things like unique ids being assigned to clients, etc. but then everything else can be done completely separately from that. There's no reason that a CassandraSessionManager would really need to exist unless you wanted to have completely seamless Cassandra-based storage. I would argue that you don't actually want that, since you have to put so much plumbing code in that you end up being a slave to HttpSession when what you really want to do is store binary data (since that's all Cassandra *can* store) and have it bound to some unique identifier (coincidentally the HttpSession id). I almost think that a Map implementation (with associated identifier, which could be session-id-based) with a Cassandra backing-store would be more useful since you could use it in any container and even entirely outside a container. I'm starting to be more like +0 to this idea. -chris signature.asc Description: OpenPGP digital signature
Re: Who wants my Cassandra session manager for Tomcat?
Morten, On 4/4/12 12:18 PM, Morten Jorgensen wrote: For the cache? The main reason why I use a filter is to be able to tie a cache object to a thread-local variable for the period for which the request is being processed. As soon as the response is streamed to the client the cache is released. If Tomcat already contains some internal reference to the current request then I won't need to use a filter in this manner. I am not a fan of thread-local variables, so I'd very much like to remove the dependency on having this filter in place. I wonder if this Filter would fail to work properly in an asynchronous context. You would certainly have to test that and document it appropriately. -chris signature.asc Description: OpenPGP digital signature
[Tomcat Wiki] Update of FAQ/Developing by ChristopherSchultz
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Tomcat Wiki for change
notification.
The FAQ/Developing page has been changed by ChristopherSchultz:
http://wiki.apache.org/tomcat/FAQ/Developing?action=diffrev1=12rev2=13
Comment:
Added hacking with Eclipse section
This section of the FAQ discusses common questions related to Tomcat
development.
== Questions ==
+ 1. [[#Hacking|Hacking]]
+1. [[#Q5|How do I start hacking Tomcat in Eclipse?]]
1. [[#Debugging|Debugging]]
1. [[#Q1|How do I configure Tomcat to support remote debugging?]]
1. [[#Q2|How do I remotely debug Tomcat using Eclipse?]]
@@ -11, +13 @@
1. Other
1. [[#Q4|How do I change the monitoring interval for modified resources
and application reloading?]]
== Answers ==
+
+ === Hacking ===
+
+ Anchor(Q5)
+ How do I start hacking Tomcat in Eclipse?
+
+ Briefly:
+
+ {{{
+ $ svn checkout http://svn.apache.org/repos/asf/tomcat/trunk
+ (or whatever branch you want: clearly, this would be better
+ to do directly from within Eclipse but it's easier to describe
+ as a command)
+
+ $ cd trunk
+
+ $ echo base.path=/path/to/where/tomcat/can/put/its/3rd-party/libs
build.properties
+
+ $ ant ide-eclipse
+ }}}
+
+ Then, in Eclipse, go to Preferences | Java/Build Path/Classpath Variables and
set
+ the following variables:
+
+ {{{
+ ANT_HOME=path to your Ant install (where lib/ant.jar can be found)
+ TOMCAT_LIBS_BASE=[whatever you set base.path to above]
+ }}}
+
+ If you look in (project
root)/res/ide-support/eclipse/java-compiler-errors-warnings.txt, you'll see a
set of compiler warnings and import organization rules that you will have to
set up manually in your project. If you set those up properly, you are more
likely to submit cleaner patches.
=== Debugging ===
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-validate has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 3 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-validate : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-validate.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-validate (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-05042012.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-05042012.jar:/srv/gump/public/workspace/junit/dist/junit-05042012.jar:/srv/gump /public/workspace/junit/dist/junit-dep-05042012.jar:guava-gump-31032012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-05042012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-05042012.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05042012.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05042012-dep.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar - download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar downloadzip: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:447: Could not create type checkstyle due to java.lang.NoClassDefFoundError: com/google/common/collect/Lists at com.puppycrawl.tools.checkstyle.CheckStyleTask.init(CheckStyleTask.java:78) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at org.apache.tools.ant.AntTypeDefinition.innerCreateAndSet(AntTypeDefinition.java:328) at org.apache.tools.ant.AntTypeDefinition.createAndSet(AntTypeDefinition.java:274) at org.apache.tools.ant.AntTypeDefinition.icreate(AntTypeDefinition.java:219) at org.apache.tools.ant.AntTypeDefinition.create(AntTypeDefinition.java:206) at org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:286) at org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:264) at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:417) at
[GUMP@vmgump]: Project tomcat-trunk-validate (in module tomcat-trunk) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-trunk-validate has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 3 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-validate : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/gump_work/build_tomcat-trunk_tomcat-trunk-validate.html Work Name: build_tomcat-trunk_tomcat-trunk-validate (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-05042012.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-05042012.jar:/srv/gump/public/workspace/junit/dist/junit-05042012.jar:/srv/gump /public/workspace/junit/dist/junit-dep-05042012.jar:guava-gump-31032012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-05042012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-05042012.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05042012.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05042012-dep.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar - download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar downloadzip: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-trunk/output/res/checkstyle BUILD FAILED /srv/gump/public/workspace/tomcat-trunk/build.xml:458: Could not create type checkstyle due to java.lang.NoClassDefFoundError: com/google/common/collect/Lists at com.puppycrawl.tools.checkstyle.CheckStyleTask.init(CheckStyleTask.java:78) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at org.apache.tools.ant.AntTypeDefinition.innerCreateAndSet(AntTypeDefinition.java:328) at org.apache.tools.ant.AntTypeDefinition.createAndSet(AntTypeDefinition.java:274) at org.apache.tools.ant.AntTypeDefinition.icreate(AntTypeDefinition.java:219) at org.apache.tools.ant.AntTypeDefinition.create(AntTypeDefinition.java:206) at org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:286) at org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:264) at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:417) at
[GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module tomcat-7.0.x) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-test has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-test : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-7.0.x/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-test.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 56 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-05042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-05042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-05042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-05042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-05042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-7.0.x/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-7.
[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-trunk-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 6 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-test : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.html Work Name: build_tomcat-trunk_tomcat-trunk-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 25 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-05042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-05042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-05042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-05042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-05042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-trunk/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-jni.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org
