Re: GWT 1.6 with Maven and build system questions/survey...
I totally agree on the fact that gwt team should not provide the maven plugin, the codehaus one can do the job. They should just take care of beeing able to integrate with any build system. My problems with the current google eclipse plugin : * If you enable gwt support on your project, GWT SDK library is automatically added to the project, event if you already manage your dependencies with maven. You should be able to configure if you want the sdk to be included or not. * The plugin complains about output directory not set to "war/WEB-INF/ classes". We should be able to configure this in order to work in a standard maven way. Johann On 16 avr, 08:50, Murray Waters wrote: > It is in the snapshots repository. > > http://snapshots.repository.codehaus.org/org/codehaus/mojo/gwt-maven-... > > You will need to add the repository > ashttp://snapshots.repository.codehaus.org/ > I believe. > > On Apr 16, 12:33 pm, Keith Willard wrote: > > > Where is the snapshot respository where the versions 1.1-SNAPSHOT > > codehaus gwt-maven-plugin lives? only the 1.0 is in the central > > repository. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.6 with Maven and build system questions/survey...
Hi, I just tried to enable maven dependencies management with google eclipse plugin and m2eclipse. The plugin complains about project output folder not set to war/WEB-INF/classes. I know I can switch my maven project output, but is there any chance the plugin can be set up to adapt to my project layout in a near future ? I want to stick to standard maven project layout. GWT should really take care of beeing well integrated with existing build tools and plugins. We can not always bend our projects just to keep GWT tooling happy... Regards, Johann On Apr 10, 7:40 am, maku wrote: > Currently we usemavenandhttp://code.google.com/p/gwt-maven/for our > build process. > > When we upgrade to GWT 1.6 we will check the codehauspluginand how > the newGoogleEclipseplugin+ new app structure can be used in a > more comfortable way. > > Regards, > Martin > > On Apr 9, 5:03 pm, Benju wrote: > > > I am curious if anybody usingMaven+GWT has tried moving to GWT 1.6 > > yet. I noticed there is no public repository containing the 1.6 > > realease only RC, Beta, and Milestones. I can always manually deploy > > GWT to our internal repository but it's a bit of a pain. > > > Also, if anybody is using GWT+Mavenwho prefers the Codehausplugin > > and who theGoogleCode GWT-Mavenplugin? From what I understand > > these twoMavenplugins are merging in the long term so that only the > > Codehauspluginwill be actively developed. > > > Finally I would also like to post the following question to the GWT > > community. What do you use for setting up your builds? I've always > > been of the opinion that a good build system is of cardinal > > importance, especially on larger projects. At this time I have seen > > the following options... > > > Hand written Ant file > > -Calling the GWT compiler directly > > -Maven > > -with the codehausplugin(http://mojo.codehaus.org/gwt-maven- > >plugin/) > > -with theGoogleCode GWT-Mavenplugin(http://code.google.com/p/ > > gwt-maven/) > > -Intellij Idea's built in GWT support > > -eclipsewith special GWT support (I believe some plugins exist > > including the recently releasedGoogleone) > > -Netbeans gwt4NB (https://gwt4nb.dev.java.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 Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Client did not send nnn bytes as expected
Hi, The issue is about how IE manage xmlHttpRequest over SSL : IE seems to randomly close the connection before request is completed. Some links about this issue and how to solve it : http://jnylund.typepad.com/joels_blog/2007/09/ie6-ajax-httpss.html http://www.perkiset.org/forum/ajax/ie_6_ajax_over_ssl-t29.0.html http://forum.mootools.net/viewtopic.php?pid=11200 In our case, it solved the issue. Johann On Dec 3, 7:48 pm, markmccall <[EMAIL PROTECTED]> wrote: > Johann, > > That solution seems somewhat obscure...how did you arrive at that > solution? > > Thanks, > Mark > > On Dec 3, 11:31 am, johann_fr <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Just in case : we had quite the same problem one year ago, but only > > with IE over https. We finally found the following solution (Apache > > configuration) : > > > SetEnvIf User-Agent ".*MSIE.*" \ > > nokeepalive ssl-unclean-shutdown \ > > downgrade-1.0 force-response-1.0 > > > It seems that this solution has a small impact on performances, but > > that's the only way we found to fix this issue. > > > Hope it helps. > > > Johann > > > On Dec 3, 5:06 pm, marcelstoer <[EMAIL PROTECTED]> wrote: > > > > On Dec 2, 10:13 am, Amit Kasher <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > Does anyone has any new insights about this issue? We've been > > > > investigating for over a year(!), and we seem to not be the only > > > > ones... > > > > >http://tinyurl.com/5rqfp5 > > > > I was recently confronted with the very same exception but in a > > > slightly different context. > > > I implemented a Servlet listener that parsed the request before it was > > > being forwarded through the filter chain to the GWT RPC Servlet. At > > > the beginning I wasn't careful enough and tinkered with the request a > > > bit too much, GWT doesn't like that. I now use the GWT RPC and > > > RPCServletUtils classes to parse the request instead of doing it > > > myself. > > > > HTH, > > > Marcel --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Client did not send nnn bytes as expected
Hi, Just in case : we had quite the same problem one year ago, but only with IE over https. We finally found the following solution (Apache configuration) : SetEnvIf User-Agent ".*MSIE.*" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 It seems that this solution has a small impact on performances, but that's the only way we found to fix this issue. Hope it helps. Johann On Dec 3, 5:06 pm, marcelstoer <[EMAIL PROTECTED]> wrote: > On Dec 2, 10:13 am, Amit Kasher <[EMAIL PROTECTED]> wrote: > > > Hi, > > Does anyone has any new insights about this issue? We've been > > investigating for over a year(!), and we seem to not be the only > > ones... > > >http://tinyurl.com/5rqfp5 > > I was recently confronted with the very same exception but in a > slightly different context. > I implemented a Servlet listener that parsed the request before it was > being forwarded through the filter chain to the GWT RPC Servlet. At > the beginning I wasn't careful enough and tinkered with the request a > bit too much, GWT doesn't like that. I now use the GWT RPC and > RPCServletUtils classes to parse the request instead of doing it > myself. > > HTH, > Marcel --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
