directory-api mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Seelmann <m...@stefan-seelmann.de>
Subject Re: Client API Schema support
Date Sat, 07 Feb 2015 13:48:14 GMT
Resending

On 02/06/2015 10:35 PM, Stefan Seelmann wrote:
> On 02/06/2015 04:17 PM, Radovan Semancik wrote:
>> Hi,
>>
>> After some delay I finally found a time to work on this. After few
>> simple fixes I got to this:
>>
>> java.text.ParseException: ERR_04243 Parser failure on matching rule
>> description:
>>         ( 1.3.6.1.4.1.26027.1.4.6 NAME ( 'relativeTimeLTOrderingMatch'
>> 'relativeTimeOrderingMatch.lt' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 )
>> Antlr message: unexpected token:
>> Antlr column: 33
>>
>>  I'm quite new to antlr and I'm still tring to find my way around. But
>> I'm sure that there is someone on the list that can save me a huge
>> amount of time. I do not expect anyone to fix this for me ... but ...
>> the grammar is not trivial and it is difficult to figure out what
>> exactly is wrong. How do you usually debug the antlr rule? Is there any
>> logging mode that can be turned on and which will dump the tokens and
>> rules that antlr encoures? Or some other trick?
> 
> Short answer: for all the schema parsers (in this case
> MatchingRuleDescriptionSchemaParser) enable the quirks mode with
> setQuirksMode(true). The 2nd name contains a dot which is not allowed
> according to RFC 4512, but the quirks mode relaxes that rule.
> 
> I don't think there is a way to dump the antlr state. In general you
> need to debug through the generated AntlrSchemaParser. Please look into
> MatchingRuleDescriptionSchemaParser line 99. There we catch the original
> exception thrown by antlr which contains the detailed stack trace,
> probably it's not good to swallow the original exception and stack trace.
> 
> Kind Regards,
> Stefan
> 


Mime
View raw message