From: Anjo K. <kr...@lo...> - 2007-01-30 14:46:37
|
The problem is the difference between eclipse and ant builds. A solution would be either: - make the std Wonder build scripts flatten the WS resources. (Easy enough to do, it's only two tasks) - move the sources out of their folders (a lot more work, and leaves a mess of empty dirs around) - fix WOLips to not flatten by default (or provide some setting to control it) - add a hack that checks if it runs under WOLips and adapt the path accordingly (also easy, but a hack) I'm open to suggestions :) Cheers, Anjo Am 23.01.2007 um 11:09 schrieb Clark Mueller: > Is anyone using YUI in a deployed environment? It appears that the > references to the nested WS resources are not correct, so they > can't be found in a deployed split install. When it makes the call > up to > > YUIUtils.addScriptResourceInHead(context, response, "yahoo-min.js"); > > for example, it gets passed up by way of AjaxUtils to > WOResourceManager, and constructs a path that doesn't refer to its > actual location in WebServerResources/yahoo (which is how > WOResourceManager works, AFAIK). Am I doing something wrong, or is > this in fact a framework bug? > > I am a bit unclear about how these need to work. In Xcode, I was > just using project groups to keep these organized (meaning they > were all flattened at build time), rather than using real > directories. That's caused me a few problems, but now that I see > YUI doing it as well, I want to make sure I understand the way it's > intended to be done. This is my last big deployment issue with > WOLips to resolve, so I'm anxious to knock it off my to-do list. :-) |