On Mon, Oct 19, 2009 at 11:26 AM, Toby Reyelts <[email protected]> wrote:
> Hey Marc, > We're not aware of this being a problem. As far as we know, we're > conforming to the standard by preferring classes in WEB-INF/lib. > Sorry, that should be "preferring classes in WEB-INF/classes". > Can you reproduce this definitively? For example, check the value of > TheHtmlUnitClassThatYouAreShadowing.class.getCodeSource().getProtectionDomain().getLocation(). > If you can provide a sample app that shows this behavior, that would be > great. > > > On Mon, Oct 19, 2009 at 11:02 AM, Marc Guillemot <[email protected]>wrote: > >> >> Hi, >> >> my application encounters occasionally strange errors that I can only >> explain by an incorrect load order (Servlet spec specifies that the >> webapp class loader must load first from WEB-INF/classes and then from >> WEB-INF/lib/*.jar). Is it possible? >> >> For the details: to allow HtmlUnit to work with AppEngine, I've hacked 2 >> classes and I've put my hacked version of these classes in >> WEB-INF/classes whereas the normal jar resides in WEB-INF/lib. This >> means that these two classes exist twice in the classpath what should >> not be a problem as WEB-INF/classes has priority but some error messages >> show that the original version in WEB-INF/lib/htmlunit-x.x.jar is used >> from time to time. >> >> Cheers, >> Marc. >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
