On 10/28/07, James M Snell <[EMAIL PROTECTED]> wrote: > I don't have any strong opinions about this other than really wanting to > make sure things stay fairly simple.
same. > Dan Diephouse wrote: > > 3. Add a RequestContext variable to most/all of the CollectionProvider > > methods: > > > > public abstract Iterable<T> getEntries(RequestContext ctx) throws > > ResponseContextException; > > public abstract <T> T getEntryFromId(String id, RequestContext ctx) > > throws ResponseContextException > > > > +1 +1 > > For the session/tx use case, the Session can be set inside the > > RequestContext and pulled out via ctx.getAttribute(). The thing I don't > > like about this option is that it adds clutter. does this call for an HttpRequestContext subtype that has a getSession method? still kind of annoying to cast, but less clutter than using an attribute.
