I originally thought that I was trying to use the built-in OutputStream, because I believed that it implemented OutputStream.write and the other methods that GWT was having trouble with, but now I understand that the built-in OutputStream does not implement those methods, and thus a custom OutputStream must be written. This is coherent with what I have found already existing in the project, e.g. a custom OutputStream. So I believe that the problem lies in that GWT is for some reason not using the custom OutputStream.
I'm fairly certain the package name is correct, as src/gwt/extended/ common is a source folder, and not a package (also, Eclipse complains when I change the package name). Do you have any ideas as to why GWT might not be using the custom OutputStream? Please let me know. Thanks, Jake On Apr 26, 5:21 pm, Vitali Lovich <[email protected]> wrote: > I thought you were trying to use the built-in OutputStream. Are you sure > the package name on your class is right? Shouldn't it be > gwt.extended.common.java.io? > > On Sun, Apr 26, 2009 at 2:34 AM, 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 have any idea as to why this might be occurring, or how to > > correct it, I would greatly appreciate it if you would let me know. > > Thanks, > > > Jake > > > On Apr 25, 6:07 pm, Thomas Broyer <[email protected]> wrote: > > > On 25 avr, 16:54, otakuj462 <[email protected]> wrote: > > > > > Hi, > > > > > I'm quite new to GWT, and I'm trying to diagnose the source of some > > > > compilation errors for an existing open source project that leverages > > > > GWT (incidentally, for my Google Summer of Code project). Without > > > > going into the details of the purpose of the application, I was hoping > > > > someone could offer some general guidance as to why these particular > > > > errors might be occuring. > > > > > The errors occur when attempting to compile certain method calls on > > > > instances of class OutputStream. So, for example: > > > > > [java] [ERROR] Errors in 'file:/C:/workspace-gsoc/ > > > > org.eclipse.swt.e4.jcl/src/gwt/extended/javascript/java/io/ > > > > OutputStreamWriter.java' > > > > [java] [ERROR] Line 31: The method close() is undefined > > > > for the type OutputStream > > > > [java] [ERROR] Line 42: The method flush() is undefined > > > > for the type OutputStream > > > > [java] [ERROR] Line 56: The method write(byte[], int, > > > > int) is undefined for the type OutputStream > > > > > This is on GWT 1.5. I also tried it on GWT 1.6, and I believe it threw > > > > the same error. I know that on GWT 1.6, OutputStream is emulated > > > > [http://code.google.com/webtoolkit/doc/1.6/RefJreEmulation.html], but > > > > I'm not sure about 1.5. > > > > As the doc says, no method is emulated on OutputStream, only the > > > (default) constructor: > >http://code.google.com/p/google-web-toolkit/source/browse/releases/1.... > > > > Actually OutputStream is only there to support System.out.print()/ > > > println(), so that you could use it in your code and get it compiled > > > to a no-op in JavaScript, without compile error. > > > > > I'd appreciate any guidance anyone can offer. > > > > Provide your own OutputStream emulation (and make sure it is picked in > > > place of the one packaged within GWT) > > > > For instance, this is the emulated OutputStream for an Adobe AIR > > > environment: > >http://code.google.com/p/gwt-in-the-air/source/browse/trunk/super/net... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
