#441: Put product request handlers in the right context
-------------------------+-------------------------------------------------
Reporter: olemis | Owner: olemis
Type: task | Status: accepted
Priority: critical | Milestone: Release 6
Component: | Version:
multiproduct | Keywords: product environment request handler
Resolution: | bep-0003
-------------------------+-------------------------------------------------
Comment (by olemis):
I've finally put all the pieces together to submit a candidate patch for
[#item-3 item 3] . It merely consists in a straightforward refactoring of
what's been working since a while (e.g. environment and request factories)
in request dispatching entry point , since the goal is just to illustrate
what will it look like . Please review . I kindly request for your
feedback so that , if the approach is well understood and accepted I'll be
able to continue that way , write test cases , etc ... and get all that
done asap .
Patch details :
{{{
#!sh
$ hg qapplied
t441/t441_r1468583_trac_bootstrap_handler.diff
$ hg log -r qparent --template="[{svnrev}] - {desc}\n"
[1468583] - add a warning if a ticket is assigned to non-existant user
(other than the default one)
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/441#comment:19>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
