>>>>> On Mon, 11 Mar 2013 16:39:20 -0400, Andy Schwartz <andy.schwartz_at_oracle.com> said:
AS> Looking at the new APIs in ViewHandler below... why do we expose
AS> addProtectedView()/removeProtectedView() methods instead of simply
AS> allowing the the protected view Set to be modified directly?
Because it would be odd to have both getProtectedViews() and
getProtectedViewsUnmodifiable().
AS> On a related note: what's the rationale for allowing protected views
AS> to be added and removed at runtime rather than requiring that this
AS> configuration be defined once up front? (Are there some lazy
AS> loading cases that we need to support, perhaps related to flows?)
There was not a specific use case. Would you rather we drop
removeProtectedView() and specify that addProtectedView() may only be
called at startup time?
Ed