Re: [VOTE] minimal JSR 154 only distribution
It would cause nightmares if you knew how badly I've got my e-mails cross-linked :). This is to +1 the original VOTE. While I'm personally a heavy JSP user, having patched TC 3.3.x to allow it to run in servlet-only mode, I see the need for offering a servlet-only container. According to the Costin-vote-watch, we still need at least one more (binding) +1 to authorize a servlet-only release of Tomcat. - Original Message - From: IAS [EMAIL PROTECTED] To: 'Tomcat Developers List' [EMAIL PROTECTED] Sent: Friday, December 06, 2002 11:02 PM Subject: RE: [VOTE] minimal JSR 154 only distribution I'm very glad to see this vote proposal because it seems to me like the first step of Servlet/JSP mutual independence. Two months ago I proposed Tomcat architectural refactoring plan (at that time Tomcat subproject plan) on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg34720.html. I also showed JSF+Struts+Catalina ensemble on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg35116.html and a possible Jasper-Catalina relationship on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg35119.html. I sincerely understand a very few of Tomcat committers share interest in this issue like jean-frederic clere's seconding on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg34768.html. In my humble opinion, in terms of technology, it is not imperative that Servlet should go with JSP. In fact, the mother of Tomcat, JServ also started as a Servlet engine. In other words, Servlet technology itself is independent one. It also implies that Java Web developers have freedom of choosing dynamic page generation technology over Servlet. We can say we have right to use JSP, but on the other hand, we have right not to use JSP in purely technical perspective. However, I totally agree on the need that we deliver JSP equipped Tomcat for the majority of Tomcat users who are very familiar with JSP (even cannot live without JSP like me :-). I guess the problem is Who will do (or exactly speaking, be willing to do) the job, i.e. making Servlet-only-Tomcat since we need a considerable number of Tomcat committers (Costin said 3) for that. If we get wide support from Tomcat committers but they can't afford the job, how about gathering Servlet-only-Tomcat team whether they belong to committers or not? I hope there would be many people who will volunteer for that, including myself. The detailed processes respecting the work could be discussed from now on, and this chance might be a new attempt to develop greater Tomcat empowered by volunteers. Thanks in advance. IAS === Lee, Changshin (Korean name) IAS (International name) Company Web Site: http://www.tmax.co.kr Personal Web Site: http://www.iasandcb.pe.kr --- Senior Researcher Java Technology Evangelist JCP member - http://jcp.org/en/participation/members/L RD Institute Tmax Soft, Inc. JCP member - http://jcp.org/en/participation/members/T == -Original Message- From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 07, 2002 1:09 AM To: tomcat-dev Subject: [VOTE] minimal JSR 154 only distribution Create a separate minimal JSR 154 only distribution of Tomcat 4.x: +1 [] 0 [] -1 [] -jon -- StudioZ.tv /\ Bar/Nightclub/Entertainment 314 11th Street @ Folsom /\ San Francisco http://studioz.tv/ -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/clusterJGCluster.java JGManager.java ReplicatedSession.java ReplicationStream.javaSerializablePrincipal.java SessionMessage.java
Filip Hanik wrote: Mmm, ok, and would would these be ? I see a few changes in the sf.net project which haven't been merged, but it doesn't look like critical changes. first of all, I wouldn't have the InMemoryReplicationManager extend the standard manager, since some workarounds had to be done with the principal. I'd like to get the save/restore on shutdown features of the std manager, and can't really see any major problem it would cause. then, when a server joins a cluster, there is a possibility that some sessions might not get replicated correctly, because a state transfer has to happen. Thanks to Bela Ban pointing this out and later in the future, instead of having every node keep a copy of the session, just use primary and secondary servers for the cluster data. So only two servers are active members of the cluster ? Is a cluster with let's say 6 members really too expensive network wise (assuming a dedicated gig ether link between the cluster members) ? Anyway, I think by far the most important feature to add is a TCP or HTTP redirector, possibly written with NBIO. Until then, the clustering doesn't have much practical interest (usless you're willing to buy additional expensive hardware; could squid get the job done, BTW ?). I'm ok with proposing you as a committer, provided you accept to respect the coding style and general design in Tomcat (I've had to do significant work to adapt the code submitted). I have no problem with this. You could have even asked me to do this, I had no idea you were gonna commit the code into the Tomcat CVS :) Mmmh, ok. I thought when code was contributed, it was to get it in the Tomcat CVS ;-) lemme know what you plan to do Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
On 6/12/02 16:09 Jon Scott Stevens [EMAIL PROTECTED] wrote: Create a separate minimal JSR 154 only distribution of Tomcat 4.x: +1 [X] 0 [ ] -1 [ ] Or simply use Jetty :-) Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Jon Scott Stevens wrote: Create a separate minimal JSR 154 only distribution of Tomcat 4.x: +1 [] 0 [] -1 [X] - I think this distribution doesn't have much interest (Jasper is rather small + the vast majority of users want the feature) - As the release manager, I feel lazy, and would like to minimize the possibilities of screwing up a distribution - Some Tomcat features depend on Jasper (like the admin webapp) - If we follow Costin's ideas on bundling, full-tomcat will bundle lots of projects; we can also bundle Velocity here (probably on the condition that it moves to commons-logging, to harmonize dependencies) - Users are used to the idea of having JSP support bundled, so this could further increase support issues (even if you put no JSP in bold, I think people will report that their JSP doesn't work) I'll add a checkbox in the Windows installer for Jasper eventually (as well as a few other components), and I think this is enough. Personally, I think this is a yes or no vote, so I don't think either choice needs a justification. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Bill Barker wrote: It would cause nightmares if you knew how badly I've got my e-mails cross-linked :). This is to +1 the original VOTE. While I'm personally a heavy JSP user, having patched TC 3.3.x to allow it to run in servlet-only mode, I see the need for offering a servlet-only container. According to the Costin-vote-watch, we still need at least one more (binding) +1 to authorize a servlet-only release of Tomcat. Now it needs 2 -1 votes :-) Bill - let me understand this - do you really want and need this ? Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Remy Maucherat wrote: - As the release manager, I feel lazy, and would like to minimize the possibilities of screwing up a distribution You don't have to do that - one of the people who voted +1 will have to volunteer as release manager for that release, and they are supposed to maintain it. - If we follow Costin's ideas on bundling, full-tomcat will bundle lots of projects; we can also bundle Velocity here (probably on the condition that it moves to commons-logging, to harmonize dependencies) It seems Jon is more interested in a release without jsp then in a release that includes velocity. Too bad. Personally, I think this is a yes or no vote, so I don't think either choice needs a justification. The majority decision works only if enough people vote. So far we have: +1: Jon, Pier, Bill -0: Costin -1: Remy Anyone else ? Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
AW: [VOTE] minimal JSR 154 only distribution
Hi, I would like to have the possibility to not include jasper in our production system. We are using TC 3.3.2-dev plus Velocity. It does not really hurt us, but having fewer code is always better IHMO :) I really love the modularity og TC 3.3.x Bill, can you give me hints, how to patch TC 3.3.2-dev to exclude jasper ? Another thought regarding the Admin Webapp in TC 4.x/TC 5.0: (please forgive me if I am completly off the track here) I would rather like to be able to use the Admin Webapp on a seperate remote Admin Tomcat to control our production system. I really do not want to install such sensitive code on our live servers. So the Admin Webapp could connect to the production Tomcat and execute for example ant tasks to restart contexts, deploy a webapp and so on. (The localhost shutdown restriction is no option, since our servers are at out ISP and have to be controlled from within our office.) Thanks, Hans -Ursprüngliche Nachricht- Von: Bill Barker [mailto:[EMAIL PROTECTED]] Gesendet: Samstag, 7. Dezember 2002 09:59 An: Tomcat Developers List Betreff: Re: [VOTE] minimal JSR 154 only distribution It would cause nightmares if you knew how badly I've got my e-mails cross-linked :). This is to +1 the original VOTE. While I'm personally a heavy JSP user, having patched TC 3.3.x to allow it to run in servlet-only mode, I see the need for offering a servlet-only container. According to the Costin-vote-watch, we still need at least one more (binding) +1 to authorize a servlet-only release of Tomcat. - Original Message - From: IAS [EMAIL PROTECTED] To: 'Tomcat Developers List' [EMAIL PROTECTED] Sent: Friday, December 06, 2002 11:02 PM Subject: RE: [VOTE] minimal JSR 154 only distribution I'm very glad to see this vote proposal because it seems to me like the first step of Servlet/JSP mutual independence. Two months ago I proposed Tomcat architectural refactoring plan (at that time Tomcat subproject plan) on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg34720.html. I also showed JSF+Struts+Catalina ensemble on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg35116.html and a possible Jasper-Catalina relationship on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg35119.html. I sincerely understand a very few of Tomcat committers share interest in this issue like jean-frederic clere's seconding on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg34768.html. In my humble opinion, in terms of technology, it is not imperative that Servlet should go with JSP. In fact, the mother of Tomcat, JServ also started as a Servlet engine. In other words, Servlet technology itself is independent one. It also implies that Java Web developers have freedom of choosing dynamic page generation technology over Servlet. We can say we have right to use JSP, but on the other hand, we have right not to use JSP in purely technical perspective. However, I totally agree on the need that we deliver JSP equipped Tomcat for the majority of Tomcat users who are very familiar with JSP (even cannot live without JSP like me :-). I guess the problem is Who will do (or exactly speaking, be willing to do) the job, i.e. making Servlet-only-Tomcat since we need a considerable number of Tomcat committers (Costin said 3) for that. If we get wide support from Tomcat committers but they can't afford the job, how about gathering Servlet-only-Tomcat team whether they belong to committers or not? I hope there would be many people who will volunteer for that, including myself. The detailed processes respecting the work could be discussed from now on, and this chance might be a new attempt to develop greater Tomcat empowered by volunteers. Thanks in advance. IAS === Lee, Changshin (Korean name) IAS (International name) Company Web Site: http://www.tmax.co.kr Personal Web Site: http://www.iasandcb.pe.kr --- Senior Researcher Java Technology Evangelist JCP member - http://jcp.org/en/participation/members/L RD Institute Tmax Soft, Inc. JCP member - http://jcp.org/en/participation/members/T == -Original Message- From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 07, 2002 1:09 AM To: tomcat-dev Subject: [VOTE] minimal JSR 154 only distribution Create a separate minimal JSR 154 only distribution of Tomcat 4.x: +1 [] 0 [] -1 [] -jon -- StudioZ.tv /\ Bar/Nightclub/Entertainment 314 11th Street @ Folsom /\ San Francisco http://studioz.tv/ -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands,
What do these errors mean?
Hello everybody! I have installed Tomcat 4.1.12 as Servlet Container and IIS as Web Server in my Windows 2000 machine. I use the ISAPI filter to redirect requests from IIS to Tomcat: in particular I use the JK connector isapi_redirector.dll you can find at: http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0 /bin/win32/ After some time IIS and Tomcat working I have read Tomcat's log files to check that all works properly and I have seen these strange errors: In iis_redir.log: //this is the log file for the ISAPI filter isapi_redirector.dll. [Mon Dec 02 09:47:03 2002] [jk_uri_worker_map.c (586)]: In jk_uri_worker_map_t::map_uri_to_worker, found a security fraud in '/www.myserver.com/myurl/tmp/mainbody.jsp.htm' In catalina_log.2002-12-02.txt: //this is the log file ( 2nd december 2002) for the Tomcat's Cataline engine. It is in /logs folder of Tomcat. 2002-12-02 13:11:32 Ajp13Processor[8009][6] process: invoke java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:126) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:501) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:536) WHAT DO THESE TWO ERRORS MEAN? HOW CAN AVOID THEM? The strange thing is that when the second error occurs Tomcat suspends itself and it doesn't accept requests any more: so I must restart the service WHY? :-( I hope someone can help me. Thanks everybody in advance! Luca
Re: [VOTE] minimal JSR 154 only distribution
I will consider voting +1 if any of the other tomcat devs who want this will volunteer to be the release manager for the servlet only distribution. I would find this handy when using Tomcat as a SOAP server where JSP is not needed. Glenn Jon Scott Stevens wrote: Create a separate minimal JSR 154 only distribution of Tomcat 4.x: +1 [] 0 [] -1 [] -jon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config server.xml service.xml
glenn 2002/12/07 09:40:38 Modified:webapps/tomcat-docs/config server.xml service.xml Log: Minor patch to docs Revision ChangesPath 1.6 +8 -6 jakarta-tomcat-4.0/webapps/tomcat-docs/config/server.xml Index: server.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/server.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- server.xml4 Sep 2002 14:09:50 - 1.5 +++ server.xml7 Dec 2002 17:40:38 - 1.6 @@ -58,12 +58,14 @@ It supports the following additional attributes (in addition to the common attributes listed above):/p - attribute name=debug required=false -pThe level of debugging detail logged by this strongServer/strong -to the associated a href=logger.htmlLogger/a. Higher numbers -generate more detailed output. If not specified, the default -debugging detail level is zero (0)./p - /attribute + attributes +attribute name=debug required=false + pThe level of debugging detail logged by this strongServer/strong + to the associated a href=logger.htmlLogger/a. Higher numbers + generate more detailed output. If not specified, the default + debugging detail level is zero (0)./p +/attribute + /attributes /subsection 1.5 +8 -6 jakarta-tomcat-4.0/webapps/tomcat-docs/config/service.xml Index: service.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/service.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- service.xml 4 Sep 2002 14:09:50 - 1.4 +++ service.xml 7 Dec 2002 17:40:38 - 1.5 @@ -57,12 +57,14 @@ It supports the following additional attributes (in addition to the common attributes listed above):/p - attribute name=debug required=false -pThe level of debugging detail logged by this strongService/strong -to the associated a href=logger.htmlLogger/a. Higher numbers -generate more detailed output. If not specified, the default -debugging detail level is zero (0)./p - /attribute + attributes +attribute name=debug required=false + pThe level of debugging detail logged by this strongService/strong + to the associated a href=logger.htmlLogger/a. Higher numbers + generate more detailed output. If not specified, the default + debugging detail level is zero (0)./p +/attribute + /attributes /subsection -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
It seems Jon is more interested in a release without jsp then in a release that includes velocity. Too bad. I think that's to Jon's credit. It shows the goal isn't to put Velocity and JSP on even footing, but just to provide what users want, which is often a more secure server without JSP. -jh- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
- Original Message - From: Hans Schmid [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Saturday, December 07, 2002 9:03 AM Subject: AW: [VOTE] minimal JSR 154 only distribution Hi, I would like to have the possibility to not include jasper in our production system. We are using TC 3.3.2-dev plus Velocity. It does not really hurt us, but having fewer code is always better IHMO :) I really love the modularity og TC 3.3.x Bill, can you give me hints, how to patch TC 3.3.2-dev to exclude jasper ? If you remove JspInterceptor from server.xml in TC 3.3.2-dev (or even 3.3.1), Tomcat will no longer understand anything about JSPs. In this case, it will be a Servlet-only container. Another thought regarding the Admin Webapp in TC 4.x/TC 5.0: (please forgive me if I am completly off the track here) I would rather like to be able to use the Admin Webapp on a seperate remote Admin Tomcat to control our production system. I really do not want to install such sensitive code on our live servers. So the Admin Webapp could connect to the production Tomcat and execute for example ant tasks to restart contexts, deploy a webapp and so on. (The localhost shutdown restriction is no option, since our servers are at out ISP and have to be controlled from within our office.) Thanks, Hans -Ursprüngliche Nachricht- Von: Bill Barker [mailto:[EMAIL PROTECTED]] Gesendet: Samstag, 7. Dezember 2002 09:59 An: Tomcat Developers List Betreff: Re: [VOTE] minimal JSR 154 only distribution It would cause nightmares if you knew how badly I've got my e-mails cross-linked :). This is to +1 the original VOTE. While I'm personally a heavy JSP user, having patched TC 3.3.x to allow it to run in servlet-only mode, I see the need for offering a servlet-only container. According to the Costin-vote-watch, we still need at least one more (binding) +1 to authorize a servlet-only release of Tomcat. - Original Message - From: IAS [EMAIL PROTECTED] To: 'Tomcat Developers List' [EMAIL PROTECTED] Sent: Friday, December 06, 2002 11:02 PM Subject: RE: [VOTE] minimal JSR 154 only distribution I'm very glad to see this vote proposal because it seems to me like the first step of Servlet/JSP mutual independence. Two months ago I proposed Tomcat architectural refactoring plan (at that time Tomcat subproject plan) on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg34720.html. I also showed JSF+Struts+Catalina ensemble on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg35116.html and a possible Jasper-Catalina relationship on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg35119.html. I sincerely understand a very few of Tomcat committers share interest in this issue like jean-frederic clere's seconding on http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg34768.html. In my humble opinion, in terms of technology, it is not imperative that Servlet should go with JSP. In fact, the mother of Tomcat, JServ also started as a Servlet engine. In other words, Servlet technology itself is independent one. It also implies that Java Web developers have freedom of choosing dynamic page generation technology over Servlet. We can say we have right to use JSP, but on the other hand, we have right not to use JSP in purely technical perspective. However, I totally agree on the need that we deliver JSP equipped Tomcat for the majority of Tomcat users who are very familiar with JSP (even cannot live without JSP like me :-). I guess the problem is Who will do (or exactly speaking, be willing to do) the job, i.e. making Servlet-only-Tomcat since we need a considerable number of Tomcat committers (Costin said 3) for that. If we get wide support from Tomcat committers but they can't afford the job, how about gathering Servlet-only-Tomcat team whether they belong to committers or not? I hope there would be many people who will volunteer for that, including myself. The detailed processes respecting the work could be discussed from now on, and this chance might be a new attempt to develop greater Tomcat empowered by volunteers. Thanks in advance. IAS === Lee, Changshin (Korean name) IAS (International name) Company Web Site: http://www.tmax.co.kr Personal Web Site: http://www.iasandcb.pe.kr --- Senior Researcher Java Technology Evangelist JCP member - http://jcp.org/en/participation/members/L RD Institute Tmax Soft, Inc. JCP member - http://jcp.org/en/participation/members/T == -Original Message- From: Jon Scott Stevens [mailto:[EMAIL
Re: [VOTE] minimal JSR 154 only distribution
on 2002/12/7 7:08 AM, Remy Maucherat [EMAIL PROTECTED] wrote: - I think this distribution doesn't have much interest (Jasper is rather small + the vast majority of users want the feature) I don't agree with that, and you have no conclusive proof of that. - As the release manager, I feel lazy, and would like to minimize the possibilities of screwing up a distribution I'm +1 which means that I'm willing to help. I have already posted the ant build for it. - Some Tomcat features depend on Jasper (like the admin webapp) It is a minimal distribution. - If we follow Costin's ideas on bundling, full-tomcat will bundle lots of projects; we can also bundle Velocity here (probably on the condition that it moves to commons-logging, to harmonize dependencies) I never mentioned Velocity and I don't care about bundles of software. I WANT A MINIMAL DISTRIBUTION OF JUST JSR 154. - Users are used to the idea of having JSP support bundled, so this could further increase support issues (even if you put no JSP in bold, I think people will report that their JSP doesn't work) Apache JServ never included JSP and was the first major open source servlet engine. In fact, at the time, JServ couldn't even properly run JSP's. Personally, I think this is a yes or no vote, so I don't think either choice needs a justification. Doesn't really matter what you personally think. The voting rules are clearly defined by the Jakarta charter. -jon -- StudioZ.tv /\ Bar/Nightclub/Entertainment 314 11th Street @ Folsom /\ San Francisco http://studioz.tv/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
on 2002/12/7 9:37 AM, Glenn Nielsen [EMAIL PROTECTED] wrote: I will consider voting +1 if any of the other tomcat devs who want this will volunteer to be the release manager for the servlet only distribution. I would find this handy when using Tomcat as a SOAP server where JSP is not needed. Glenn I will volunteer to be the release manager. -jon -- StudioZ.tv /\ Bar/Nightclub/Entertainment 314 11th Street @ Folsom /\ San Francisco http://studioz.tv/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
on 2002/12/7 10:45 AM, Jason Hunter [EMAIL PROTECTED] wrote: It seems Jon is more interested in a release without jsp then in a release that includes velocity. Too bad. I think that's to Jon's credit. It shows the goal isn't to put Velocity and JSP on even footing, but just to provide what users want, which is often a more secure server without JSP. -jh- I always love how Jason just gets it. =) Although, security is one point, I simply just don't want JSP in my JSR 154 container. -jon -- StudioZ.tv /\ Bar/Nightclub/Entertainment 314 11th Street @ Folsom /\ San Francisco http://studioz.tv/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [newbie] where do I get TagFileInfo, etc.?
Kin-Man Chung wrote: It's in jakarta-servletapi-4, which IS mentioned in BUILDING_txt. Make sure that you have servlet.home defined correctly in build.properties. I'm trying to build jakarta-tomcat-4.0, but it wanted jakarta-tomcat-jasper (not mentioned in BUILDING.txt). I checked that out, but it's build fails with undefined symbols. Where can I find these? I was relying on Debian's libservlet2.3-java package. But it's not in jakarta-servletapi-4, either. I built that, and pointed jakarta-tomcat-4.0/build.properties to it, but get the same errors. I grepped the tree, too, and couldn't find 'package.*javax\.servlet\.jsp\.el', for example. So far, I've got the CVS from jakarta-servletapi-4 jakarta-tomcat-connectors jakarta-tomcat-4.0 jakarta-tomcat-jasper Thanks. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Jon Scott Stevens wrote: Create a separate minimal JSR 154 only distribution of Tomcat 4.x: +1 [X] 0 [] -1 [] -jon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
I am not a committer, and I am not against JSP at all, but I cannot see how having options and alternatives (without insane proliferation, of course) could be a bad thing. Micael At 05:56 PM 12/7/2002 -0600, you wrote: Jon Scott Stevens wrote: Create a separate minimal JSR 154 only distribution of Tomcat 4.x: +1 [X] 0 [] -1 [] -jon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
On 7/12/02 16:32 Costin Manolache [EMAIL PROTECTED] wrote: The majority decision works only if enough people vote. So far we have: +1: Jon, Pier, Bill -0: Costin -1: Remy Anyone else ? For the records, please check in $CVSROOT/avail... I'm not a committer... I only support _strongly_ the argument as an EX committer, because that was the actual reason which forced me to move to some alternative servlet containers (it was JUST A BIG F'IN pain in the ass to strip out all the crap from the distribution every time a new release came along)... That said, I also have to say that I won't be able to help in any way, as reluctantly, now I'm spending my times coding around those other alternatives to Tomcat, AKA Jetty... Jon, I'm very sorry mate, you're 4 months too late :-( I lost my fight about this very same topic back then... Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
on 2002/12/7 4:25 PM, Pier Fumagalli [EMAIL PROTECTED] wrote: Jon, I'm very sorry mate, you're 4 months too late :-( I lost my fight about this very same topic back then... Pier Maybe to late for your opinion, but honestly, I haven't been that impressed with Jetty. I saw very little if any speed increase with Jetty and Scarab and I actually consider Jetty's distribution to be packed with more crud than Tomcat's...but maybe I'm just biased by Tomcat. At this point, I don't think that with JSR 154 and JSR 152 being separate, there is much that anyone here can say negative about distributing JSR 154 only engine. Clearly there is a demand. Clearly it is a good thing to have options. -jon -- StudioZ.tv /\ Bar/Nightclub/Entertainment 314 11th Street @ Folsom /\ San Francisco http://studioz.tv/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
On 8/12/02 0:43 Jon Scott Stevens [EMAIL PROTECTED] wrote: on 2002/12/7 4:25 PM, Pier Fumagalli [EMAIL PROTECTED] wrote: Jon, I'm very sorry mate, you're 4 months too late :-( I lost my fight about this very same topic back then... Maybe to late for your opinion, but honestly, I haven't been that impressed with Jetty. In my case it speeds up my stuff around 3/4 times faster. And the footprint is considerably slower... Depends on the app... I saw very little if any speed increase with Jetty and Scarab and I actually consider Jetty's distribution to be packed with more crud than Tomcat's...but maybe I'm just biased by Tomcat. That's what I'm working on! :-) Greg just removed (finally) all the Win .BAT files from CVS and distros! :-) 3 less files! :-) At this point, I don't think that with JSR 154 and JSR 152 being separate, there is much that anyone here can say negative about distributing JSR 154 only engine. Clearly there is a demand. Clearly it is a good thing to have options. +1 +1 +1 +1 :-) I hope you succeed where I failed! :-) Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15164] New: - NullPointerException when JDBCRealm not configured properly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15164. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15164 NullPointerException when JDBCRealm not configured properly Summary: NullPointerException when JDBCRealm not configured properly Product: Tomcat 4 Version: 4.0.6 Final Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] if you omit the userCredCol attribute from the Realm tag when using JDBCRealm (for example, if you specify it as userCredColumn instead) you end up getting a NullPointerException from JDBCRealm.authenticate (line 389). The misconfiguration does not directly trigger an error. The JDBCRealm issues this SQL query: SELECT null FROM user_table WHERE username_col = ? since this is a valid query, there is no SQLException thrown; but rs.getString (1) returns null instead of the user password column. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/conf server.xml
billbarker2002/12/07 23:14:16 Modified:catalina/src/conf server.xml Log: Adding a comment to document how to configure custom-Valves for MBeans. Revision ChangesPath 1.66 +7 -1 jakarta-tomcat-4.0/catalina/src/conf/server.xml Index: server.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/conf/server.xml,v retrieving revision 1.65 retrieving revision 1.66 diff -u -r1.65 -r1.66 --- server.xml21 Nov 2002 09:42:36 - 1.65 +++ server.xml8 Dec 2002 07:14:16 - 1.66 @@ -13,7 +13,13 @@ Server port=8005 shutdown=SHUTDOWN debug=0 - !-- Uncomment these entries to enable JMX MBeans support -- + !-- Comment these entries out to disable JMX MBeans support -- + !-- You may also configure custom components (e.g. Valves/Realms) by + including your own mbean-descriptor file(s), and setting the + descriptors attribute to point to a ';' seperated list of paths + (in the ClassLoader sense) of files to add to the default list. + e.g. descriptors=/com/myfirm/mypackage/mbean-descriptor.xml + -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/conf server.xml
billbarker2002/12/07 23:23:05 Modified:catalina/src/conf server.xml Log: Porting from TC 4. Revision ChangesPath 1.13 +7 -1 jakarta-tomcat-catalina/catalina/src/conf/server.xml Index: server.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/server.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- server.xml5 Dec 2002 16:02:54 - 1.12 +++ server.xml8 Dec 2002 07:23:05 - 1.13 @@ -13,7 +13,13 @@ Server port=8005 shutdown=SHUTDOWN debug=0 - !-- Uncomment these entries to enable JMX MBeans support -- + !-- Comment these entries out to disable JMX MBeans support -- + !-- You may also configure custom components (e.g. Valves/Realms) by + including your own mbean-descriptor file(s), and setting the + descriptors attribute to point to a ';' seperated list of paths + (in the ClassLoader sense) of files to add to the default list. + e.g. descriptors=/com/myfirm/mypackage/mbean-descriptor.xml + -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Jason Hunter wrote: It seems Jon is more interested in a release without jsp then in a release that includes velocity. Too bad. I think that's to Jon's credit. It shows the goal isn't to put Velocity and JSP on even footing, but just to provide what users want, which is often a more secure server without JSP. So you're saying Jon is not proposing that because of his hatred for JSPs, but because users keep asking him for that ? Disabling JSPs in a server is quite easy - and has been possible for a long time. Almost 1/2 of the tomcat community is working on jasper, and is the piece of tomcat that has probably the biggest distribution ( if we include Jetty and all other servers that use jasper ). And most people in the tomcat community are using JSPs. I very much doubt a tomcat without jasper is best for the users or community. Most developers will test and work on the distribution that includes jasper. Anyway - Jon, Bill and Glenn voted +1 - and so far only Remy is -1. Even if I change my vote to -1, the vote would still pass. It doesn't look like a consensus, but it is a majority at this moment. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
