On Tue, Apr 24, 2012 at 4:21 PM, zzkozak <[email protected]> wrote: > After cleaning up my pom.xml, where I referenced our global parent pom, the > server is starting without any problems. So it seems there is a conflict > with other jars. >
Ah yeah when upgrading make sure you dont have different versions of Camel on the classpath. > Thank you Claus! > > -- > View this message in context: > http://camel.465427.n5.nabble.com/After-update-from-2-5-0-2-9-2-I-got-org-xml-sax-SAXParseException-cos-all-limited-1-2-tp5661890p5662177.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
