Re: [deegree-devel] OGCFrontController singleton!?

[Markus S. <sch...@la...>]

Hi Falko,

Falko Bräutigam wrote:

>>> Moreover, OGCFrontController binds request the the current thread. It seems that 
>>> a lot of places all over the code are depending on this to find a proper 
>>> GET/POST URL for the current request. This stops me from swapping the entire 
>>> front-controller, which in turn stops me from having different sub-controllers 
>>> for different servlets/URLs. Right so far?
>> Besides the URL aspect, the main motivation for the thread binding is security. We augment the ThreadLocal with the user
>> credentials, so they can be accessed from any service / code level (provided the thread originated in a request).
>>
>> Still, I guess it should be possible to exchange the OGCFrontController with a different implementation as long as it
>> provides the access to the request parameter / credentials...
> 
> Hmmm... well, still new to the deegree3 codebase I don't see how to swap the 
> OGCFrontController. A lot of code all over depends on exactly the call to the 
> static(!) method OGCFrontController.getHttpPostURL(). No chance to overwrite or 
> provide another impl. At least I don't see how.

Well, I just thought of the rather drastic approach of exchanging the class (keeping the name and the static methods).
But you're right that it is not really pluggable. If you got any suggestions on achieving this, please go ahead.

Best regards,
Markus

-- 
Markus Schneider

l a t / l o n  GmbH
Aennchenstrasse 19           53177 Bonn, Germany
phone ++49 +228 184960       fax ++49 +228 1849629
http://www.lat-lon.de        http://www.deegree.org