Yes, we need to implement this method in our implementations, but then not actually call the method anywhere ourselves.
On Tue, Dec 9, 2008 at 1:33 PM, Lex Spoon <[EMAIL PROTECTED]> wrote: > On Fri, Dec 5, 2008 at 12:28 PM, BobV <[EMAIL PROTECTED]> wrote: > > - Several classes in user/test/.../server/rpc do not compile against > > Jetty given the difference in the servlet API in Jetty versus Tomcat. > > This is problematic when using an Eclipse project structure that isn't > > hamstrung by linked resources. > > I've noticed this too. An easy solution would be to switch over to > the 1.5 API of servlets throughout the code base. All it should take > is adding one method, I think it is ServletContext.getContextPath, to > all of our implementations of ServletContext. > > The Java verifier should be okay even if these things are used on a > container that uses the 1.4 API, because the verifier check that would > fail does not actually run until the method in question is invoked, > and in this case the method would never be invoked. > > The result would be that our code only compiles against the Servlet > API version 1.5, but the compiled files run against version 1.4. > > -Lex > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
