Okay, I've found a work-around for this, which is basically to put A.jar in the /war/lib dir and B.jar on the system path. (Seemingly, the -Dorg.mortbay.jetty.webapp.parentLoaderPriority=true is being ignored, or perhaps I'm just not using it properly)
-M On Apr 10, 2:19 pm, mike <[email protected]> wrote: > Hi all, > > In trying to upgrade to 1.6, I've run into some problems with hosted > mode (I'm guessing due to the change to jetty). I'll describe the > situation generically: > > I have two jars: A.jar and B.jar which both include class Foo. My > classpath is set to A.jar:B.jar since I'd prefer to use the > implementation of Foo in A.jar if it exists and fall back to B.jar > otherwise. If I run in hosted mode, however, there doesn't seem to be > any way to get it to prefer A.jar. (This worked fine in 1.5). When I > deploy this application, everything works fine (as before), but I'd > like to be able to continue to use hosted mode. > > Just to confirm the proper classpath, I print the system classpath on > startup, which lists the proper order. I thought it might be related > to the issue re: jetty described > here:http://docs.codehaus.org/display/JETTY/Classloading > But, setting -Dorg.mortbay.jetty.webapp.parentLoaderPriority=true (the > suggested workaround) doesn't seem to have any effect. > > Any tips would be appreciated. Thanks! > > -M --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
