[~mschipperheyn], you can try 4.4.2-SNAPSHOT which I deployed. It would be interesting to see whether it fixes your problem.
[~gsmet], {quote}
I'm not sure our fix is the right one. I think it's part of the fix
{quote}
+1
{quote}
but I'm wondering if we shouldn't also introduce a way to reset the per class ParseContext information when we work on a new root entity.
{quote}
AFAIK it is. {{AnnotationMetadataProver#getTypeMetadataFor}} creates a new {{ParseContext}} for each requested class (provided I understood correctly what you are after). I am comparing the pre 4.4 (and new metamodel) code with the current one. I tried to take this code over as much intact as possible, but it seems I still introduced a bug. Problem is, this bit of code was and is hard to understand. I am open for all suggestions of improvements. It it turns out that the current proposed fix, will at least bring back the old behaviour, I think we should go for it and address potential improvements in a follow up issue. WDYT?
This way, even if there is an error in the parse logic, it will be limited to the current entity.
{quote}
P.S. The logic used to be part of {{AbstractDocumentBuilder}}
|
HSEARCH-1442
