Jukka Zitting wrote: > >> Is there a way to deal with this issue? I wasn't able to find >> much clarification on what the correct behavior should >> be from the spec (String properties are supposed to >> be like java.lang.Strings, but Sec 6.4.4 doesn't mention >> ways to escape non-XML characters). > > It's a known issue with JSR-170, invalid XML characters in string > properties break the XML imports. See the JSR-170 maintenance draft > for the proposed solution (use Base64 encoding for such string > properties) to this issue. > > Note that Jackrabbit does not yet implement this solution, so for now > the only workaround is to either avoid such characters in string > properties or to use custom import/export mechanisms. >
Aha, I see. Thanks, Jukka. Roughly, is there an expected time frame for such maintenance draft features to get finalized and implemented? Regards, Joshua -- View this message in context: http://www.nabble.com/Invalid-XML-characters-in-export-tf2809830.html#a7842936 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
