Same reason version 1 is still there, no? There are A LOT of talks about "backwards compatibility", etc. so I thought to leave v2 in there in case someone, somewhere would require it, or v3 (default) would break some clients, etc., so this would be an easy "escape route" to plug views for older versions back in.


Same reason the "protocols" directory structure exists for views in the first place, so multiple "protocols" could be used. No? Have I misunderstood?


If not, then i suggest to remove ALL the older protocols and keep the only one, latest protocol view. 


Cheers,
D. 
—
Sent from Mailbox for iPhone

On Tue, Apr 9, 2013 at 6:12 AM, LELEU Jérôme <notifications@github.com>
wrote:

>> @@ -25,11 +25,18 @@ cas1ServiceSuccessView.(class)=org.jasig.cas.web.view.Cas10ResponseView
>>  cas1ServiceSuccessView.successResponse=true
>>  
>>  ### CAS 2.0 Response Protocol Views
>> +cas2ServiceSuccessView.(class)=org.springframework.web.servlet.view.JstlView
>> +cas2ServiceSuccessView.url=/WEB-INF/view/jsp/protocol/2.0/casServiceValidationSuccess.jsp
>> +
>> +cas2ServiceFailureView.(class)=org.springframework.web.servlet.view.JstlView
>> +cas2ServiceFailureView.url=/WEB-INF/view/jsp/protocol/2.0/casServiceValidationFailure.jsp
> Why do we keep the old responses ? Are they used somewhere ?
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/Jasig/cas/pull/224/files#r3710659