Re: [MO-java-users] setting attributes in a mock request

[Steve F. <st...@m3...>]

I guess someone was trying to make a clear distinction between the two 
concepts. After all, sometimes you just don't care what the request 
parameters are, you just want the value returned. The risk is of 
overspecifying the test so that it breaks when unimportant things 
change. In practice, this is probably too subtle.

Roll on the dynamic libraries (at least servlets are defined using 
interfaces).

S.

Ext...@no... wrote:
>>The idea is that you should preload your attributes in the order in 
>>which they are requested, and then they'll just be returned 
>>as the code 
>>runs. It's not actually doing a lookup. Checking which attributes are 
>>asked for is actually a separate concept and handled by a different 
>>expectation. There are some arguments for doing this but it 
>>does look a 
>>little clumsy.
> 
> 
> What are the arguments for this approach?  I encountered the same problem a while back and I'm still scratching my head :-)