DO NOT REPLY [Bug 37591] New: - wrong typing in the doc

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

SVN oddities with "current" link

Hi, I like checking out the current link ( https://svn.apache.org/repos/asf/tomcat/current/tc5.5.x) which uses svn externals to grab the container, build, connectors, etc. It's nice and convenient. But for committing and updating, it kind of sucks. Doing an "svn commit" or "svn update" at the top-

DO NOT REPLY [Bug 37483] - NPE in JspDocumentParser when processing characters in a tag file

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

DO NOT REPLY [Bug 37485] - I'd like to run init SQL after JDBC Connection creation in DBCP

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

Re: How to turn the Digester off?

Yes, currently Geronimo does that for its other web-container. I am trying to do the same for Tomcat. Thanks Anita --- Remy Maucherat <[EMAIL PROTECTED]> wrote: > anita kulshreshtha wrote: > > Since there was no reply, I am assuming that > > turning off the digester is not straightforw

Re: How to turn the Digester off?

--- anita kulshreshtha <[EMAIL PROTECTED]> wrote: > Yes, currently Geronimo does that for its other > web-container. I am trying to do the same for Tomcat. > When a web.xml is digested, a lot of objects internal to Tomcat are created. There's stuff liek servlet mapping, initialization of

Re: SVN oddities with "current" link

Well, can't stop myself: The right solution is to stop playing SVN tricks, and just reorganize the code as a single codebase instead of 4 (or 5). So my question remains: can we _move_ build, connectors, etc as subdirs in a single svn tree, while preserving some file history ? Costin On 11/22/0

Re: How to turn the Digester off?

You need to create your Context without creating the associated ContextConfig. This rules out using Embedded.createContext and JMX embedding. Tomcat usually doesn't run very well without ContextConfig, so Geronimo will have to duplicate much of the functionality that is there. - Original Mes

APR link in index of docs

a spelling fix also :) Index: C:/workspace/container/webapps/docs/index.xml === --- C:/workspace/container/webapps/docs/index.xml (revision 348249) +++ C:/workspace/container/webapps/docs/index.xml (working copy) @@ -100,8 +100,9 @@ M

Re: APR link in index of docs

Sorry. Use this instead. Index: C:/workspace/container/webapps/docs/index.xml === --- C:/workspace/container/webapps/docs/index.xml (revision 348250) +++ C:/workspace/container/webapps/docs/index.xml (working copy) @@ -100,8 +100,9 @@

Re: SVN oddities with "current" link

Yoav Shapira wrote: Hi, I like checking out the current link ( https://svn.apache.org/repos/asf/tomcat/current/tc5.5.x) which uses svn externals to grab the container, build, connectors, etc. It's nice and convenient. But for committing and updating, it kind of sucks. Doing an "svn commit" or "s

Re: SVN oddities with "current" link

Costin Manolache wrote: Well, can't stop myself: The right solution is to stop playing SVN tricks, and just reorganize the code as a single codebase instead of 4 (or 5). So my question remains: can we _move_ build, connectors, etc as subdirs in a single svn tree, while preserving some file hist

Re: SVN oddities with "current" link

What problems ? I think it would be cleaner and more consistent with what we do - i.e. label/branch all components at the same time and same way. Well, maybe 6.x would be the right time to reorg the code to a single tree, I'll ask again when we get there ( BTW - what are the plans for 6.x ? ) Cos

Re: SVN oddities with "current" link

Hi, I also think a re-org into a single codebase for build, container, jasper is in order. Connectors and servletapi are a bit different because they have their own releases (and release cycles). I think from the users' perspective, a single SVN repository is cleaner and makes building easier. Y

Re: SVN oddities with "current" link

Container, jasper and build are a good start. I think connectors should be included too. Servletapi is obviously different, and even in the current build it's downloaded as a jar AFAIK. You can still have separate releases and release cycles for different components - even if they reside in the s