Comment 1 Richard Kulp 2005-01-31 11:07:45 EST

The problem here is that ProxyPlugin.urllocalize... also looks into fragments to
get the jars. We need to evaluate which ones REALLY need to look into fragments.
Those that don't can be created without requiring I/O. Those that do will need
to look into fragments and so require I/O to find them in the correct fragment.
If it is in fragment, we don't know which fragment it would be because those
would be Locale or OS dependent and may change. Most are actually not fragment
dependent.

Need to refactor the API on ProxyPlugin.urllocalize... so that we can
distinquish between the two of them.

Comment 2 Gili Mendel 2005-01-31 12:45:34 EST

Peter, can you drive our finger out of "the I/O jar"

Comment 3 Peter Walker 2005-02-03 13:54:34 EST

Made lots of API changes to ProxyPlugin.java to handle lookups to jars via
fragments and just looking into the bundle directly. This should reduce the
Platform.find searches that were always done for all lookups. For 90% of the
lookups should be through getting it from the bundle only.
Three main APIs are available for this capability:
 localizeAllFromBundleAndFragments(Bundle bundle, String filenameWithinBundle)
 localizeFromBundleAndFragments(Bundle bundle, String filenameWithinBundle)
 localizeFromBundleOnly(Bundle bundle, String filenameWithinBundle)

Changes released into VE 1.1 stream (HEAD). This is available for iteration 3.

Comment 4 Richard Kulp 2005-06-10 11:12:26 EDT

These were missed originally as being done for 1.1M1