On Mon, 26 Jun 2006, Dave Rolsky wrote: > On Mon, 26 Jun 2006, John Williams wrote: > > > I'll get the fix committed. > > Before you commit, is this new behavior or did Mason do this correctly in > the past? In other words, how is this documented? If we documented it as > being the way it is now, we probably can't change it right now, mid-stable > cycle.
The ability to use $m->call_next from a helper component is at least assumed, since we have tests for it. I'm not sure if it is formally documented anywhere, since it is not done very often. It probably never worked correctly in the past. Using call_next from a helper component is tested for in t/11-inherit.t (see the call_next_helper component in there). However the effect on the request component is _not_ tested, since the <& variants &> component is only called from /subdir/autohandler, and not from /subdir/normal. If you add the call to <& variants &> to /subdir/normal, the problem is pretty obvious, since the attributes and methods get invoked all wrong. ~ John Williams Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
