Fop
  1. Fop
  2. FOP-2040

event message lookup field part fails to perform lookup

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: None
    • Component/s: general
    • Labels:
      None
    • Environment:
      Operating System: All
      Platform: All
    • External issue ID:
      53065

      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

        Activity

        Show
        Glenn Adams added a comment - http://svn.apache.org/viewvc?rev=1324913&view=rev

          People

          • Assignee:
            fop-dev
            Reporter:
            Glenn Adams
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development