>
> or the resource oracle, which is essentially an optimized way of checking
> the context class loader).
Does this mean that if context class loader is checked, then it is not
necessary to check resource oracle? And vice versa.
On Tue, Jun 1, 2010 at 7:00 PM, Scott Blum <sco...@google.com> wrote:
> On Tue, Jun 1, 2010 at 12:33 PM, Ray Ryan <rj...@google.com> wrote:
>
>> On Tue, Jun 1, 2010 at 9:25 AM, Lex Spoon <sp...@google.com> wrote:
>>
>>> On Tue, Jun 1, 2010 at 11:56 AM, Ray Ryan <rj...@google.com> wrote:
>>>
>>>> Yup. Is the fix to make it use the resource oracle?
>>>
>>>
>>> To play it safe:
>>>
>>> First check resource oracle.
>>> Next check the context class loader, as in Marko's email.
>>> Then check wherever it looks now (the system class loader?).
>>>
>>
>> IIRC, that's what Bob has ClientBundle doing in general. Should the
>> resource oracle itself be doing this?
>>
>
> Yeah, this is correct. Although, I'm not sure if the last one is strictly
> necessary.
>
> The exception to the rule is when you're trying to look up things that you
>> are confident are bundled *with* the generator. For example, when looking
>> up a resource you bundled into the same jar as a generator, you can do
>> something like
>> "this.getClass().getResource("some-bundled-resource-in-this-package"). But
>> anything that a USER might provide has to be looked up through the context
>> class loader (or the resource oracle, which is essentially an optimized way
>> of checking the context class loader).
>
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
