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?
--
Radovan Semancik
Software Architect
evolveum.com
On 01/27/2015 11:50 AM, Emmanuel Lécharny wrote:
I have modified the DefaultSchemaLoader constructor to load the schema
from teh rootDSE, even if it's not an ApacheDS server :
http://svn.apache.org/r1655004
There is a try...catch to deal with cases where what's in the rootDSE
fails. This is most certainly the place where we want to add the code to
try other approaches.
At this point, I think we would like to have one module per server - if
needed - when we have to use heavyly different code to read the schema,
so that we can insolate each specific code. To be discussed further.
