It looks the SAXParseException doesn’t has the location information. Did you change the runtime of your production environment recently? BTW, it could useful if you can tell us the Java version and Camel version of your application.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On March 15, 2015 at 1:28:04 AM, akhilesh2u (akhiles...@gmail.com) wrote: > Hi All, We are facing a serious problem in production where we are > using the apache camel xsd validator in the routes. When ever the > input xml is validated with the respective xsd and there are any errors to > it we are catching the error message and based on the line number ,column > number and message content we are dynamically generating our custom error > message. Suddenly now in production we are facing a issue where if > there any xml validation failures then those error messages line and column > numbers are with -1 and -1. Basically camel validator is not giving the > exact line and column numbers rather it is showing a SaxParserException with > *Line -1 and Column -1* We really couldn't figure out the problem.If > someone faced this problem could you please suggest us so that we can take > your inputs and get this issue sorted. Thanks in Advance. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Validator-issue-a-show-stopper-in-production-tp5764148.html > > Sent from the Camel Development mailing list archive at Nabble.com.
