Which version of Wicket do you use ? In latest 1.4-SNAPSHOT it is "protected". In 1.5 this method does not even exists anymore. The same for SERVLET_PATH_HOLDER. This one is used in WicketFilter#init() and WicketServlet#init(). Do you completely re-write those ?
On Tue, Nov 30, 2010 at 3:45 PM, Steffen Fritzsche <[email protected]>wrote: > Hi, > > Why is the method "getLastModified" in WicketFilter package-protected? > > My problem is that I extend WicketFilter in an OSGi context. I'd like to > delegate all calls to my own "getLastModified" method to the underlying > WicketFilter. Since I am in an OSGi context and the package > "org.apache.wicket.protocol.http" is already exported by the wicket core > osgi bundle I can not simply put my class in the same package, nor can I > place a small wrapper class in this package which increases the method > visibility. > > So, question is if there are any side effects which justify that I can't > delegate to this method. I don't see any. Maybe it makes sense to increase > the visibility of this method. > > The same problem exists with parameter SERVLET_PATH_HOLDER in WicketFilter. > Since this is only a parameter one could easily copy it, but since it is > final already why not make it public? Or at least protected to use it in > Subclasses? > > Regards, > Steffen > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
