Cocoon
  1. Cocoon
  2. COCOON-1602

Only one flow node per sitemap allowed in mounted sitemap with pass-through=true

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Incomplete
    • Affects Version/s: 2.1.8
    • Fix Version/s: None
    • Component/s: * Cocoon Core
    • Labels:
      None
    • Environment:
      Operating System: other
      Platform: Other

      Description

      When using in a sitemap containing a flow script definition : map:mount
      src="xxx.xmap" pass-through="true"
      And when the xxx.xmap sitemap contains a flow script definition i have the
      following error : Only one flow node per sitemap allowed

      Note : it was working with cocoon-2.1.7

      It is broken since the svn revision :
      http://svn.apache.org/viewcvs.cgi?diff_format=h&rev=190154&view=rev
      1. ASF.LICENSE.NOT.GRANTED--aze
        13 kB
        Jean-Baptiste Quenot

        Activity

        Hide
        Carsten Ziegeler added a comment -
        This exception has been introduced to catch several "map:flow" statements in a
        sitemap which didn't work before as only the last one was used anyway.
        So, I guess the pass through is not resetting the flow information.
        Can you give a complete test case?
        Show
        Carsten Ziegeler added a comment - This exception has been introduced to catch several "map:flow" statements in a sitemap which didn't work before as only the last one was used anyway. So, I guess the pass through is not resetting the flow information. Can you give a complete test case?
        Hide
        Jean-Baptiste Quenot added a comment -
        Created an attachment (id=16455)
        Full stack trace
        Show
        Jean-Baptiste Quenot added a comment - Created an attachment (id=16455) Full stack trace
        Hide
        Sylvain Wallez added a comment -
        Weird... if there's effectively only one <map:flow> in the sitemap, this means
        the DefaultTreeBuilder isn't properly recycled, which _should_ happen when it is
        released in the finally block in TreeProcessor.buildConcreteProcessor()...
        Show
        Sylvain Wallez added a comment - Weird... if there's effectively only one <map:flow> in the sitemap, this means the DefaultTreeBuilder isn't properly recycled, which _should_ happen when it is released in the finally block in TreeProcessor.buildConcreteProcessor()...
        Hide
        Sylvain Wallez added a comment -
        There were actually two <map:flow> in a sitemap, which was difficult to track
        down among the several dozen that exist in the project.

        I added location info to the exception.
        Show
        Sylvain Wallez added a comment - There were actually two <map:flow> in a sitemap, which was difficult to track down among the several dozen that exist in the project. I added location info to the exception.

          People

          • Assignee:
            Unassigned
            Reporter:
            Philippe Gassmann
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development