Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jieryn, On 8/7/13 9:48 AM, jieryn wrote: > On Wed, Aug 7, 2013 at 9:41 AM, Caldarale, Charles R > wrote: >> Sorry, that's just wrong. There is no requirement for an >> individual webapp to have a WEB-INF/web.xml, but if you want to >> run Tomcat

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jieryn, On 8/7/13 10:00 AM, jieryn wrote: > On Wed, Aug 7, 2013 at 9:54 AM, Martin Grigorov > wrote: >> Which you will delete too, I suppose ? :-) > > I have not modified the shipped Apache Tomcat applications > themselves. I suspect that most use

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-07 Thread jieryn
Greetings, On Wed, Aug 7, 2013 at 9:54 AM, Martin Grigorov wrote: > Which you will delete too, I suppose ? :-) I have not modified the shipped Apache Tomcat applications themselves. I suspect that most users are very accustomed to modifying contents under conf/* but leave the shipped application

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-07 Thread Martin Grigorov
On Wed, Aug 7, 2013 at 3:48 PM, jieryn wrote: > Greetings, > > On Wed, Aug 7, 2013 at 9:41 AM, Caldarale, Charles R > wrote: > > Sorry, that's just wrong. There is no requirement for an individual > webapp to have a WEB-INF/web.xml, but if you want to run Tomcat with the > required servlet spec

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-07 Thread jieryn
Greetings, On Wed, Aug 7, 2013 at 9:41 AM, Caldarale, Charles R wrote: > Sorry, that's just wrong. There is no requirement for an individual webapp > to have a WEB-INF/web.xml, but if you want to run Tomcat with the required > servlet spec capabilities, you must leave Tomcat's conf/web.xml in

RE: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-07 Thread Caldarale, Charles R
> From: jieryn [mailto:jie...@gmail.com] > Subject: Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE > I'll answer more completely in the other no-web.xml NPE thread, but > quickly: there's no actual requirement for web.xml Sorry, that's just wrong. The

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-07 Thread jieryn
Greetings, On Tue, Aug 6, 2013 at 11:30 PM, Christopher Schultz wrote: > Tomcat also has a serious bug in that if you delete conf/server.xml, > it won't start up properly. I sense I'm being mocked.. :-) I'll answer more completely in the other no-web.xml NPE thread, but quickly: there's no actu

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-06 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 8/6/13 4:56 PM, Mark Thomas wrote: > On 06/08/2013 21:53, jieryn wrote: >> Greetings, >> >> On Tue, Aug 6, 2013 at 2:56 PM, Mark Thomas >> wrote: >>> On 06/08/2013 20:31, jieryn wrote: When clicking the 'SSL connector configuration d

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-06 Thread Mark Thomas
On 06/08/2013 21:53, jieryn wrote: > Greetings, > > On Tue, Aug 6, 2013 at 2:56 PM, Mark Thomas wrote: >> On 06/08/2013 20:31, jieryn wrote: >>> When clicking the 'SSL connector configuration diagnostics' >>> 'Connection ciphers' button, the following NPE ends up in the log and >>> a similar stac

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-06 Thread jieryn
Greetings, On Tue, Aug 6, 2013 at 2:56 PM, Mark Thomas wrote: > On 06/08/2013 20:31, jieryn wrote: >> When clicking the 'SSL connector configuration diagnostics' >> 'Connection ciphers' button, the following NPE ends up in the log and >> a similar stack trace is sent to the browser: > > I can't r

Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE

2013-08-06 Thread Mark Thomas
On 06/08/2013 20:31, jieryn wrote: > When clicking the 'SSL connector configuration diagnostics' > 'Connection ciphers' button, the following NPE ends up in the log and > a similar stack trace is sent to the browser: I can't repeat this with a clean installation. Please provide the steps to reprod