Possible unintended behaviour with registering function name conventions routes on a class heirarchy

[Noel Kennedy]

I think I have discovered a 'bug' with registering routes via function name convention routes.  It doesn't register method routes on super classes of your controllers.  This is I suspect why using mixins on your controllers at instantiation time doesn't work either, because by creating your controllers like this, you are creating an anonymous subclass of your controller.

The actual bug is outside of bowler and inside ClassSignature in recursivity.commons.  Bowler's POSORouteMapper calls to ClassSignature.apply and this returns no super class methods.

Please advise as to whether this is by design or a bug!

Cheers,

Noel

[Wille Faler]

I'd qualify it as a bug, thanks for pinpointing where the issue lies!

[Wille Faler]

This is now fixed in Recursivity Commons, and the dependency will be updated shortly in the 0.5-SNAPSHOT of Bowler, so should be in both Github and repo's within the hour.

[Noel Kennedy]

Thanks! Super quick as ever, Enjoy your weekend :)

On Aug 26, 5:00 pm, Wille Faler <wille.fa...@gmail.com> wrote:
> This is now fixed in Recursivity Commons, and the dependency will be updated
> shortly in the 0.5-SNAPSHOT of Bowler, so should be in both Github and
> repo's within the hour.
>

> On 24 August 2011 11:40, Wille Faler <wille.fa...@gmail.com> wrote:
>
>
>
>
>
>
>
> > I'd qualify it as a bug, thanks for pinpointing where the issue lies!
>

> > On 24 August 2011 11:30, Noel Kennedy <nk.ag...@googlemail.com> wrote:
>
> >> I think I have discovered a 'bug' with registering routes via function
> >> name convention routes.  It doesn't register method routes on super classes
> >> of your controllers.  This is I suspect why using mixins on your

> >> controllers at instantiation time<https://groups.google.com/group/bowler-users/browse_thread/thread/c84...>doesn't work either, because by creating your controllers like this, you are