Ok, that's a shame, but thanks for letting me know. I had some vague
memory of Emmanuel tidying something up in this area a long while
back, but my understanding must have been incomplete.
On Fri, Sep 5, 2008 at 6:31 PM, Stefan Seelmann <[EMAIL PROTECTED]> wrote:
> Norval Hope wrote:
>> required (
Norval Hope wrote:
> required (for instance I originally had lots of probs requiring
> explicit use of LdapDN.getUpName() which I understand / hope I may now
> be able to replace with humble .toString()s). While I'm doing this
> port over I'll try to disentangle changes which might be interesting
>
Hi Again,
Just wanted to report that I successfully back-ported the new
FilterParser to my mongrel hybrid patched version of AD < 1.5-ish. In
the process I ran into a number of UTF8 encoding issues when dealing
with characters with >2 char encodings and patched a number of files
(part / most of th
Hi Emanuel,
Thanks for the feedback; I knew I was trying my luck a bit but thought
I'd better check if anyone happened to remember any relevant history.
I'm getting reasonably hopeful that I can backport the new
FilterParser with a bit of creative reactive refactoring ...
Once I get this current
Hi Norval,
the thing is that the antlr based filter parser has been totally
rewritten in 1.5, and replaced by a hand crafted parser, so it's
difficult to say if the previous version correctly handle UTF-8 chars in
any case, but a blind guess is that it may be buggy.
Now, to be frank, I don't
Hi All,
I'm using a customized version of ApacheDS 1.5 and have run into a
problem with the filter parser. I know this has been much improved in
more recent versions of AD but I'm not able to ugrade at this moment
(however, it seems I'll be able to start embarking on the process of
resyncing with
