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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.1
• Fix Version/s: 1.0.2
• Component/s: NetUI
• Assignee: Julie Zhuo
• Reporter: Howard Carlin Rogers
• Created: 01/Apr/06 02:46
• Updated: 01/Apr/06 04:14
• Resolved: 01/Apr/06 04:14

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.