Bug 53065

Summary: event message lookup field part fails to perform lookup
Product: Fop - Now in Jira Reporter: Glenn Adams <gadams>
Component: generalAssignee: fop-dev
Status: RESOLVED FIXED    
Severity: normal    
Priority: P3    
Version: trunk   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Glenn Adams 2012-04-11 18:34:33 UTC
in revision 932481, the functionality to perform a lookup on a LookupFieldPart was removed [1] due to lack of a default bundle

[1] http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/java/org/apache/fop/events/EventFormatter.java?r1=932481&r2=932480&pathrev=932481

this change resulted in certain event messages no longer containing the intended information;

for example, the following message appeared

org.apache.fop.fo.ValidationException: "fo:retrieve-marker" is not a valid child of "fo:block"! (See position 23:62)

instead of the desired message:

org.apache.fop.fo.ValidationException: "fo:retrieve-marker" is not a valid child of "fo:block"! An fo:retrieve-marker is permitted only as the descendant of an fo:static-content. (See position 23:62)

in particular, the "[ {ruleViolated,lookup}]" part of the message

<message key="invalidChild">"{offendingNode}" is not a valid child of "{elementName}"![ {ruleViolated,lookup}]{{locator}}</message>

is being elided to the empty string
Comment 1 Glenn Adams 2012-04-11 18:44:54 UTC
http://svn.apache.org/viewvc?rev=1324913&view=rev