On 26 avr, 08:34, Jake <[email protected]> wrote:
> Thomas and Vitali, thank you for the expert advice. I believe I'm
> beginning to put this problem into perspective. Here is the
> OutputStream implementation bundled with this project:
>
> http://dev.eclipse.org/viewcvs/index.cgi/e4/org.eclipse.e4.swt/bundle...
>
> Here's the top-level module file I'm attempting to compile:
>
> http://dev.eclipse.org/viewcvs/index.cgi/e4/org.eclipse.e4.swt/exampl...
>
> Finally, here's the module file which should pull in
> OutputStream.java:
>
> http://dev.eclipse.org/viewcvs/index.cgi/e4/org.eclipse.e4.swt/exampl...
>
> My theory right now is that for some reason, our project's custom
> OutputStream.java is not being found or used, and is therefore being
> replace by GWT's built-in OutputStream class. But I'm not sure how
> that could occur, as I know that GWT errors out if I specify a module
> that it cannot find. So it seems that it must have found the module,
> but is for some reason not using it in favor of its built-in
> OutputStream class. Very strange.
If you re-define/emulate Java Runtime classes, you have to put them in
a <super-source/>
http://code.google.com/webtoolkit/doc/1.6/DevGuideOrganizingProjects.html#DevGuideModuleXml
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
