Uploaded image for project: 'Beehive'
  1. Beehive
  2. BEEHIVE-1090

NetUI page flow compiler's WebappPathType.checkRelativePath() needs to handle paths to JPF that begin with "./"

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.0.1
    • 1.0.2
    • NetUI
    • None

    Description

      Add an action such as the following to a page flow controller:

      @Jpf.Action(forwards =

      { @Jpf.Forward(name = "success", path = "./subdir/Controller.jpf") }

      )
      protected Forward AddAction()

      { ... }

      As the jpf compiler does its thing, it translates external pageflow paths into type names and then requests those types. Here it is incorrectly translating "./subdir/Controller.jpf" to a type name "..subdir.Controller"
      which may cause an APT implementation to barf when we try to get a TypeDeclaration from this name. With the Sun APT, we get a null type without an error, but then this causes us to write a warning that we cannot find the page flow for the given path.

      The problem is in org.apache.beehive.netui.compiler.grammar.WebappPathType.checkRelativePath(). It does some stuff to look for "../" at the beginning of a path but does not handle "./".

      I'll add a zip file for the repro. The fix is coming shortly.

      Attachments

        1. j1090-repro.zip
          2 kB
          Howard Carlin Rogers

        Activity

          People

            jzhuo Julie Zhuo
            crogers Howard Carlin Rogers
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: