Hi again :) The getWrappedCall() method has been changed to "protected" in order to provide a stricter encapsulation. It's like preventing some client code to manually access to the members of an object without going through the proper method.
However, I don't want to sound too dogmatic: if there is a blocking reason forcing you to have a shortcut path to the wrapped call, then I'll switch the modifier back to "public". IMHO, you don't need to use this approach anymore to access to the HTTP headers (see my other reply). Best regards, Jerome > -----Message d'origine----- > De : Lars Heuer [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 14 septembre 2006 15:26 > À : Lars Heuer > Objet : Re: b19 - Call converters > > Hi again, > > one follow-up: > > ((HttpServerRestletCall) > call).getConnectorCall().getRequestHeaders() > > only works with "unwrapped" calls. That's why I suggested to make > > WrapperCall#getWrappedCall() > > "public". > > If it is public I could do something like this: > > if (call instanceof WrapperCall) { > Call unwrappedCall = call.getWrappedCall(); > doSomthing(((HttpServerRestletCall) unwrappedCall) > .getConnectorCall() > .getRequestHeaders()); > } > > Since getWrappedCall() is not public I have to derive every MyCall > instance from MyWrapperCall where the modifier is "public". Arrrg. :/ > > Would it do any harm to make getWrappedCall() public? It would be > easier to write utilities that work with either Call or WrapperCall > instances without the need to derive from a custom MyWrapperCall > class. > > Best regards, > Lars > -- > http://www.semagia.com > >
