Re: Tomcat Xml parser issue

2017-11-17 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Vicky, On 11/16/17 1:30 PM, Vicky B wrote: > Thanks but the same war works fine is WebSphere and tomcat on > Windows it is just tomcat provided by Redhat which work different > i.e it throws the exception My guess is that something in your

RE: Tomcat Xml parser issue

2017-11-16 Thread Jean Pierre Urkens
List <users@tomcat.apache.org> Subject: Re: Tomcat Xml parser issue Thanks but the same war works fine is WebSphere and tomcat on Windows it is just tomcat provided by Redhat which work different i.e it throws the exception On Nov 16, 2017 11:39 PM, "Christopher Sc

Re: Tomcat Xml parser issue

2017-11-16 Thread Vicky B
Thanks but the same war works fine is WebSphere and tomcat on Windows it is just tomcat provided by Redhat which work different i.e it throws the exception On Nov 16, 2017 11:39 PM, "Christopher Schultz" < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256

Re: Tomcat Xml parser issue

2017-11-16 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Vicky, On 11/16/17 12:24 PM, Vicky B wrote: > It is XML parser (DOM and SAX ) from oracle (doc > ) > > . Why do you need a custom XML parser? Why not simply use the one

Re: Tomcat Xml parser issue

2017-11-16 Thread Vicky B
It is XML parser (DOM and SAX ) from oracle (doc ) . Why is tomcat using XMLparserv2 , tomcat we have in linux machine is from redhat . Why does tomcat downloaded from apache tomcat site work different form the one

Re: Tomcat Xml parser issue

2017-11-16 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Vicky, On 11/16/17 6:53 AM, Vicky B wrote: > Hi All, > > I have application which is using spring , ESAPI and oracle > xmlparserv2.jar , this application works fine in my local tomcat on > windows but when i deployed in linux server with linux