Re: Storing MaverickContext in request causing issues with portal processes

+1

When I started using Maverick I had similar problems/ questions as Eric did. I think it is a good idea to have the behavior documented (other than on this list). Adding the parameter and a single line of documentation would do it.

Eelco
  ----- Original Message ----- 
  From: Schnitzer, Jeff 
  To: [email protected] 
  Sent: Wednesday, May 07, 2003 8:32 PM
  Subject: RE: [Mav-user] Storing MaverickContext in request causing issues with portal processes


  Take it easy folks, this is just the law of unintended consequences working against us :-)



  Clearly this behavior is going to have to be configurable.  I propose an init-param for the Dispatcher servlet called "reuseMaverickContext".  Given the confusion that might result, I believe the default should be "false".



  Thoughts?



  J2FF



  -----Original Message-----
  From: Eric Kreiser [mailto:[email protected]] 
  Sent: Wednesday, May 07, 2003 11:10 AM
  To: [email protected]
  Subject: RE: [Mav-user] Storing MaverickContext in request causing issues with portal processes



  so what you are saying is that you made a design decision to preclude the use of your product in a portal environment

    -----Original Message-----
    From: Doug Kirk [mailto:[email protected]]
    Sent: Wednesday, May 07, 2003 1:42 PM
    To: [email protected]
    Subject: Re: [Mav-user] Storing MaverickContext in request causing issues with portal processes

    On Wednesday, May 7, 2003, at 10:24 AM, Eric Kreiser wrote: 



    The issue is not efficiency in chaining or not chaining - the issue is is it correct to assume that if two controllers are processed using the same under lying httpservletrequest that they are being chained - and the answer is no. 



    While you may consider it incorrect and an assumption, it is not. It is a design decision. Personally, I like this decision better than having to manually chain.