Hi, Just a small word of warning for those users using the error controller to take appropriate action.
Previously (1.9.7) either EXCEPTION_NO_CONTROLLER or EXCEPTION_NO_ACTION was thrown when no route existed, but I'm now seeing the EXCEPTION_NO_ROUTE. For me this bit me on upgrade due to my use of an error controller to fall back to legacy (pre-ZF) code (e.g. my only app entry point is via my ZF bootstrap and dispatch loop). I have an error controller that catches this case and ultimately falls back to a "legacy includer" affair (it's not necessarily beatiful but it gives a clean code path for new stuff even if old stuff is a bit convoluted!) So just thought I'd send out a "gotcha" style email to let folks upgrading know this change in behaviour. Cheers and KUTGW! Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
