>> The problem here is that it requires the use of the codebase, which John is >> trying to avoid (there are some unfortunate side effects of the >way the JDK >> performs service lookups when running in an applet that doesn't disable >> codebase lookup - I filed a bug on it, but Sun/Oracle >never responded).
> With the codebase method you can compute an url for example > "/pivotapp/applet-log4j.xml": I know. :-) Unfortunately, because of how the JDK implements service lookups, using the codebase imposes a performance penalty. From the Pivot README: "NOTE Pivot uses the StAX API to load and process WTKX source files. Like many APIs in the JDK, StAX uses a service discovery mechanism to locate and instantiate an appropriate parser. When deploying Pivot applications in a web browser, this may incur unnecessary requests to the web server. The service resolution process looks on the classpath for an appropriate service descriptor file; since an applet's classpath also contains its codebase, the JRE will look for this file on the web server if it is not found in an archive JAR. Such requests can have a noticeable impact on runtime performance, especially for slow or unresponsive web servers. As a result, it is recommended that all Pivot applications deployed via the web set the codebase_lookup applet parameter to false." I did file a bug to Sun about this. As I recall, I had suggested a relatively simple fix. However, they never responded and I can't find the bug report now. :-(
