Action extension handling in parent classes

[GoogleCodeExporter]

Action extension handling isn't working correctly when extension methods
are implemented in parent classes.

example:

public abstract class Foo {

  public String info() { 
    // should handle <actionName>.info requests
  }

}

@Action
public class Bar extends Foo {
  // .... concrete action
  public String get() {
    // handles get requests
  }
}

The above action diagram depicts the situation that should be handled by
the JCatapult MVC Action Workflows

If I make a request for 'bar.info' the parent class method 'Foo.info()'
should be invoked to do work.  Currently, this is not the case.  In order
for this to work properly you have to implement the 'extension method' in
the concrete class.

Original issue reported on code.google.com by leafkn...@gmail.com on 13 Jan 2009 at 10:22

[GoogleCodeExporter]

Original comment by leafkn...@gmail.com on 13 Jan 2009 at 10:22

• Added labels: Milestone-1.0

[GoogleCodeExporter]

This was either fixed or was already working fine. I added test case for it 
into the MVC and verified that it works 
as described. If you find that it still isn't working, re-open and attach the 
source code in question.

Original comment by bpontare...@gmail.com on 19 Mar 2009 at 2:28

• Changed state: Verified
• Added labels: Component-MVC, OpSys-All