Found the solution to the ParseException! In Windows command prompt, I used the command:
type myCndFile.cnd ...which showed me that at the start of the cnd file there was a byte order mark (added as the file had been saved in UTF-8 format). Obviously the culprit that was causing the cnd parser issues! I resolved by saving the cnd file in ANSI format. Should the cnd parser expect a byte order mark - is it a bug? -- View this message in context: http://jackrabbit.510166.n4.nabble.com/Node-Type-Registration-in-JCR-2-0-tp2532652p2532735.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
