[FOP-2040] event message lookup field part fails to perform lookup

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: 2.5
• Component/s: unqualified
• Environment: Operating System: All; Platform: All
• External issue ID: 53065
• Assignee: fop-dev
• Reporter: Glenn Adams
• Created: 11/Apr/12 18:34
• Updated: 11/Apr/12 18:44
• Resolved: 11/Apr/12 18:44

Description

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