On Apr 24, 2007, at 9:37 AM, Jose Galvez wrote:
If I understand you correctly I should be able to add a new controller
to a running pylons service (assuming there is a route to handle
it) is
that correct?, because that has not been my experience. When I've
added
a new controller I've always had to restart the service otherwise I
get
a 404 error
As I mentioned, you have to set the map attribute to false, to have
Routes re-scan the controller dir and become aware of controllers.
Then a generic route like:
map.connect(':controller/:action/:id')
will recognize the new controller. This will work on a live system
without a restart. To grab the mapper instance anywhere:
from routes import request_config
map = request_config().mapper
map._created_regs = False
On the next request, :controller will be able to match the new
controller.
Cheers,
Ben
10 messages in com.googlegroups.pylons-discussRe: adding controllers to an existing...