Alex, Yes and no. Joachim Grueneis could explain things in more detail, and I leave it up to him to do so.
But let's try to get yourself going first. Can you please rewrite your code as follows: XMLContext context = new XMLContext(); context.setProperty(XMLConfiguration.LENIENT_ID_VALIDATION, true); Unmarshaller u = context.createUnmarshaller(); u.setRoot(aClass); That definitely should work. Werner Alex Porras wrote: > Werner Guttmann wrote: > >> Which is odd, as the stack trace in the first email indicates that this >> is a problem with strict order of sequence, and the property turns this >> feature off. I guess I will need a Jira issue where you attach all >> relevant files for me, incl. builder properties, etc. But please try to >> keep things am minimal as possible. > > Werner, > > I'm preparing a simple test case to illustrate this behavior, but before > I create the Jira issue, can I verify that this is an acceptable > alternate way to set the "lenient" property in the unmarshaller? Jeffrey > tried with the properties method, but I'm not sure if it's actually > getting read correctly, so I wanted to try setting it programatically > for this testing. > > Unmarshaller u = new Unmarshaller(aClass); > // what is it set to now? > boolean liv = u.getInternalContext().getLenientIdValidation(); > > // set it > u.getInternalContext().setProperty(XMLConfiguration.LENIENT_ID_VALIDATION, > true); > > // check value again > liv = u.getInternalContext().getLenientIdValidation(); > > Cheers, > > Alex > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
