Hi Lex,
The first solution seems interesting... could you please provide a code
snippet just to get me started...
Did you mean something like
Thread.currentThread().setContextClassLoader(urlClassloader);
List<String> moduleNames = new ArrayList<String>();
moduleNames.add("com.hypersimple.HyperSimple");
File workDir = new File("uncompressed\\work");
final CompilePermsOptions options = new CompilePermsOptionsImpl();
options.setModuleNames(moduleNames);
options.setWorkDir(workDir);
int perms[] = { 0 };
options.setPermsToCompile(perms);
Thread.currentThread().setContextClassLoader(prevUrlClassloader);
/Marko
On Tue, May 4, 2010 at 6:06 PM, Lex Spoon <[email protected]> wrote:
> On Mon, May 3, 2010 at 7:36 AM, Marko Vuksanovic <
> [email protected]> wrote:
>
>> I solved the problem... This had nothing to do with the GWT. The
>> problem was with adding a folder to java class path dynamically.
>> Although at first I thought I had done it correctly, it turned out
>> that that's a little tricky...
>>
>> For anyone else with the same problem - here's a gist on how to solve
>> it...
>> http://gist.github.com/387972
>>
>> As you can see, a call to protected method is required in order to add
>> a folder to class path.
>>
>>
> It would also be possible to create a new class loader and set that as the
> "context class loader". Then GWT should use the new one.
>
> Alternatively, when the JVM is launched on the remote machine, pass the
> extra directories in using the -classpath option.
>
> -Lex
>
>
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
