On Jul 21, 2010, at 8:12 PM, Mike Schrag wrote: > Or your deployment needs fixing to not assume jar frameworks :) > > On Jul 21, 2010, at 12:29 AM, Lachlan Deck wrote: > >> You'll find that the implementation for this needs fixing so that it doesn't >> assume *.framework resources. :-/
I found: > We only accept 5.4 fixes now, not issues. None of the comitters use or > condone the use of 5.4 and thus we can't really test or debug problems with > it. > > Anyway: this request handler is only enabled when you use the direct connect, > using which is a bad idea in the first place. You can get back to use he > normal WO request handler by setRequestHandlerForKey(new > WOStaticResourceRequestHandler(), "_wr_") in your app. > > http://issues.objectstyle.org/jira/browse/WONDER-86?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel So public class ERXStaticResourceRequestHandler extends WORequestHandler , but you can just drop back to vanilla WORequestHandler? I think this issue was marked fixed, by going back to WORequestHandler? There needs to be a list of webobjects 5.3 vs 5.4 and the Wonder issues. I know Chuck as some 5.4 vs 5.3 differences. I also know that wocheckboxes need a work around in 5.4. Is anybody using 5.4? It is too bad that Wonder doesn't work so well with the jar frameworks; sometimes it does, sometimes it doesn't...
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
