Re: Disable auto scanning for EJBs in a NON-EJB web application in Tomee 7.1.0

2019-02-01 Thread Mark Thomas
On 01/02/2019 12:20, Priyadarshini Krishna wrote: > Request help. Try asking the TomEE project rather than the Tomcat project.] Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands,

Re: distinction between resource charset and format octet decoding

2019-02-01 Thread Garret Wilson
Good morning, I'm just getting to the editing. I'm going to list some thoughts I have as I go through this, so you can verify things: * The servlet spec links are way out of date. I'll update them. * "There /is no default encoding for URIs/ specified anywhere, which is why there is a lot

Disable auto scanning for EJBs in a NON-EJB web application in Tomee 7.1.0

2019-02-01 Thread Priyadarshini Krishna
Hi, I am working on migrating a web-app for my organisation. We have started using Spring 5, which needs the latest Tomee and hence the migration process. Our application works fine on Tomee 1.7.5. We do not have any EJBs in our web application, but Tomee 7.1.0 seems to scan for one. I have

Re: distinction between resource charset and format octet decoding

2019-02-01 Thread Garret Wilson
On 2/1/2019 7:23 AM, Garret Wilson wrote: …  * "There /is no default encoding for URIs/ specified anywhere, which    is why there is a lot of confusion when it comes to decoding these    values." Sheesh, this is is ancient. I'll correct it as per   

Re: distinction between resource charset and format octet decoding

2019-02-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Garret, On 2/1/19 11:08, Garret Wilson wrote: > On 2/1/2019 7:23 AM, Garret Wilson wrote: >> … * "There /is no default encoding for URIs/ specified anywhere, >> which is why there is a lot of confusion when it comes to >> decoding these values."

Re: distinction between resource charset and format octet decoding

2019-02-01 Thread Garret Wilson
On 2/1/2019 9:38 AM, Christopher Schultz wrote: Amazing. A close reading of RFC 3986 reveals that there is no clear mandate for UTF-8 in existing URI schemes, even though recommended for new schemes. Anyway, everyone seems to have settled on UTF-8 (Tomcat included), so I'll try to indicate that.

Re: distinction between resource charset and format octet decoding

2019-02-01 Thread Garret Wilson
OK, Mark, I've made my initial edits to the https://wiki.apache.org/tomcat/FAQ/CharacterEncoding page. _Please check them over!_ This is my first edit to the wiki. That page has a lot of legacy information, some of which had to do with internal Tomcat stuff, and some of which had to do with

recommendations for using multiple CRLs

2019-02-01 Thread Joseph Dornisch
Does this group have any recommendations for merging multiple external CRLs into one CRL for use with Tomcat, or just making Tomcat aware of multiple CRLs?

Re: distinction between resource charset and format octet decoding

2019-02-01 Thread Mark Thomas
On 01/02/2019 17:58, Garret Wilson wrote: > OK, Mark, I've made my initial edits to the > https://wiki.apache.org/tomcat/FAQ/CharacterEncoding page. _Please check > them over!_ This is my first edit to the wiki. > > That page has a lot of legacy information, some of which had to do with >