Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production
Very cool. Bob Vawter and I (and I think a couple more people) worked on this a long time ago, and there's definitely a lot of room for improvement. Nice to see someone tackle this! On Wednesday, July 17, 2013 4:56:40 PM UTC-4, Alex Epshteyn wrote: > > Dear fellow GWT users, > > I would like to announce that I have finally solved what I always thought > to be GWT's greatest weakness: its lack of debugging information for > client-side exceptions in production. > > With my patch, your deployed app will be able to report stack traces like > this: > > com.google.gwt.core.client.JavaScriptException: (TypeError) : a is null > > com.google.gwt.dom.client.DOMImplMozilla.$getBodyOffsetLeft(DOMImplMozilla.java:145) > > > com.google.gwt.user.client.ui.PopupPanel.$setPopupPosition(Document.java:1287) > > com.google.gwt.user.client.ui.PopupPanel.setPopupPosition(PopupPanel.java:884) > com.google.gwt.user.client.ui.PopupPanel.PopupPanel(PopupPanel.java:453) > > com.typeracer.commons.client.widgets.EnhancedPopup.EnhancedPopup(EnhancedPopup.java:32) > > com.typeracer.commons.client.widgets.PopupWithIcon.PopupWithIcon(PopupWithFocusableTextBox.java:28) > > > com.typeracer.main.client.controller.TyperacerUncaughtExceptionHandler$1.execute(TyperacerUncaughtExceptionHandler.java:55) > > > com.google.gwt.core.client.impl.SchedulerImpl.runScheduledTasks(SchedulerImpl.java:50) > > etc... :-) > > > instead of the current state of affairs that looks like this: > > lineNumber: 3190 columnNumber: 15354: a is null; (TypeError) fileName: > http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html > stack: @ > http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:2422 > Rub@http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:2423 > > dSb@http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:3190 > > tA@http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:2810 > Xmb@http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:2289 > > etc... :-( > > > I am asking the community to support me in finishing this effort and > integrating my patch into GWT. Please take a look and what I've done, and > consider making a donation: > > http://igg.me/at/gwt-stack-traces/x/3494291 > > I am an indie developer and I just need some funding to continue this > work. I'm looking for both grassroots and corporate sponsorship for my > quest of improving GWT's error reporting and debugging support. > > I've written a detailed white paper ( http://goo.gl/YGsrQ ) that > describes how my solution works and why it is necessary. I welcome your > feedback! > > Thanks! > Alex > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: GWT 2.2.0 broke binary compatibility for code generation
I bet you could do something like this:
class FooGenerator extends Generator {
private static final Generator impl;
static {
try {
Class jTypeClass =
Class.forName("com.google.gwt.core.ext.typeinfo.JType");
Class generatorClass;
if (jTypeClass.isInterface()) {
generatorClass =
Class.forName("com.example.foo.rebind.impl.FooGenerator");
} else {
generatorClass =
Class.forName("com.example.foo.rebind.legacyimpl.FooGenerator");
}
impl = (Generator) generatorClass.newInstance();
} catch (Exception e) {
if (e instanceof RuntimeException) {
throw (RuntimeException) e;
}
throw new RuntimeException(e);
}
}
@Override
public String generate(TreeLogger logger, GeneratorContext context,
String typeName) throws UnableToCompleteException {
return impl.generate(logger, context, typeName);
}
}
On Tue, Feb 22, 2011 at 6:06 PM, Brian Reilly wrote:
> I'll have to look into maven to see if that can be done, but I'm not
>
> too optimistic that it would work very well.
>
>
> Is there a gwt.version property that we can check inside the
>
> generate-with tag of the library's module XML? Theoretically, a
>
> library could then provide two classes in a single jar... one compiled
>
> against 2.1.1 and the other compiled against 2.2.
>
>
> I'd even take a property that is new or that the default value changed
>
> in 2.2... really anything to take the burden of worrying about this
>
> off of the end developer.
>
>
> -Brian
>
> --
> 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.
>
--
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: Second try: app works on Linux, but not on Windows (1.6.4 hosted mode)
That would probably explain it. $wnd.event is a special field I think, and
if you're manually setting it to a String where someone else expects it to
be an Event Object, that could definite explain the cast problem.
On Tue, May 12, 2009 at 2:50 PM, mlgm wrote:
>
> Scott,
>
> thanks for the answer, I was giving up my hope!
>
> I did the debugging you asked for and from what I found, I was able to
> find the problem and a workaround myself :-). I'm not sure though if
> it should work as it was before. At least with Firefox on Linux it
> did, but I'm no browser and JavaScript expert.
>
> What happened is this: I'm trying to build an application, where the
> GWT module should react on an outside parameter. As a possibility for
> doing this, I had found the following solution on the Internet. First,
> I created a little JavaScript inside the host page (i.e. a host
> servlet) with a variable for the parameter:
>
>
> var event="aa00aa00aa00aa00aa01";
>
>
> Then this variable is read from inside the GWT module by using a small
> native JavaScript method:
>
>public native String getEventRID()/*-{
>return $wnd.event;
>}-*/;
>
> The problem now seems to be, that I called my variable "event" (as in
> performance). If I change the variable name to something else, it
> works. As I said, I'm more of a Java expert and have nearly no
> JavaScript knowledge and don't know if I'm not allowed to create a
> variable named "event", at least in Internet Explorer. BTW, I tested
> it with IE6 and IE7, but not IE8.
>
> In case you might want to analyze this further, here are the debugging
> values:
>
> In IDispatchImpl.callMethod()
>
> cl = com.google.gwt.dev.shell.compilingclassloa...@ea5140
> jthis = null
> params = [VT_BSTR{aa00aa00aa00aa00aa01}]
> method = static boolean com.google.gwt.user.client.DOM.previewEvent
> (com.google.gwt.user.client.Event)
>
> In SwtOleGlue.convertVariantsToObjects()
>
> i = 0
>
> Thanks again and GWT rocks!
>
> Best wishes
>
> Michael
>
> >
>
--~--~-~--~~~---~--~~
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: Second try: app works on Linux, but not on Windows (1.6.4 hosted mode)
Michael, I'll need you to help debug this. Can you put a break point where the exception is getting thrown and see what Java method is being called? If you're using Eclipse, you can use the Debug menu while debugging to set a "Java exception breakpoint" for ClassCastException (caught and uncaught), and optionally restrict it to just JsValueGlue. Once you're at the break point, you should be able to click on the debugger's stack view to highlight IDispatchImpl.callMethod(). The automatic locals and params should allow you to explore exactly which Java method is getting called. It would also be helpful to find out which argument the error is happening on-- this will be the current value of "i" on that SwtOleGlue.convertVariantsToObjects() stack frame. Lemme know if you need more detailed instructions. Also, are you running IE8 on that machine? Thanks, Scott --~--~-~--~~~---~--~~ 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: Packaging error in gwt-user 1.6.4 with javax servlet classes and java files
I don't see this in 1.6.4. As far as I can tell, all of the .java files in javax/servlet have a timestamp of: Tue Jul 22 02:00:00 EDT 2008 All of the .class files have: Tue Jul 22 02:00:30 EDT 2008 The class files are 30 seconds newer than the source files. --~--~-~--~~~---~--~~ 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: Announcing GWT 1.6 RC2
It should be possible to run the compiler in a 64-bit VM, so that should solve the problem of compiling huge apps. On Thu, Apr 2, 2009 at 11:14 AM, Alexandros Papadakis wrote: > > I am talking about HUGE GWT applications that would require more than > 1.5 gigs of memory. > > -Xmx1512M is the max I can have using a 32bit java. > > > > On Thu, Apr 2, 2009 at 4:58 PM, Miles T. wrote: > > > > Use the native browser to its full power ? What are you talking > > about ? > > > > On Apr 2, 11:15 am, Vitali Lovich wrote: > >> For me, the bigger benefit is the ability to utilize the native browser > to > >> its full-power. For instance, Firebug + Firefox. > >> > >> 2009/4/2 Alexandros Papadakis > >> > >> > >> > >> > Great > >> > >> > 1.5.3 (which I am using) in Hosted mode can not run under 64bit java. > >> > The compiler can, which is nice. > >> > >> > As bigger and bigger projects are going to be developed, this will > >> > be an issue, since 32bit java can only address 1.5 gigs of > >> > memory (or... am I wrong???) > >> > >> > Regards, > >> > >> > On Thu, Apr 2, 2009 at 10:47 AM, Vitali Lovich > wrote: > >> > > With GWT 2.0 (I believe that's the version after 1.6 & the current > trunk) > >> > > has OOPHM scheduled for it, which removes the platform dependancy > pretty > >> > > much, I'm running it right now on 64-bit Ubuntu with my native > Firefox. > >> > >> > > On Thu, Apr 2, 2009 at 3:18 AM, Alexandros Papadakis < > alpa...@gmail.com> > >> > > wrote: > >> > >> > >> Hi, > >> > >> > >> Will there be a 64bit version? > >> > >> > >> Best regards, > >> > >> Alex > >> > >> > >> On Tue, Mar 31, 2009 at 5:51 AM, Scott Blum > wrote: > >> > >> > The GWT team is happy to announce the availability of Google Web > >> > Toolkit > >> > >> > 1.6 > >> > >> > RC2. Download it here: > >> > >> > >> > > http://code.google.com/p/google-web-toolkit/downloads/list?q=1.6.3 > >> > >> > >> > For an overview of the new features in 1.6, please see the > >> > announcement: > >> > >> >http://googlewebtoolkit.blogspot.com/2009/03/google-web-toolkit-16-rc. > .. > >> > >> > >> > The only real difference from RC1 should be some fixes I made for > the > >> > >> > hosted > >> > >> > mode Jetty configuration issues that were reported with RC1: > >> > >> >http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=miles. > .. > >> > >> > >> > --Scott, on behalf of the GWT team > > > > > > > > > --~--~-~--~~~---~--~~ 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: Announcing GWT 1.6 RC2
2009/4/1 Дмитрий Николаев > $ ant build > Buildfile: build.xml > > libs: > > javac: >[javac] Compiling 8 source files to > /home/dima/bin/gwt/gwt-linux-1.6.3/samples/DynaTable/war/WEB-INF/classes Compiling 8 source files? Can you do an "ant clean" and see if that fixes it? --~--~-~--~~~---~--~~ 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: Announcing GWT 1.6 RC2
We also cache the results of an earlier phase in the compile, so even if you're running a single thread, it should be marginally faster than 1.5. On Wed, Apr 1, 2009 at 4:50 AM, Thomas Broyer wrote: > > On 1 avr, 05:52, "C.H." wrote: > > >New Features > > >...faster compilation... > > > > How much faster compilation compare to 1.5? > > AFAICT, compiling a given permutation isn't faster than in 1.5 but > permutations are now compiled in parallel threads. > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Announcing GWT 1.6 RC2
The GWT team is happy to announce the availability of Google Web Toolkit 1.6 RC2. Download it here: http://code.google.com/p/google-web-toolkit/downloads/list?q=1.6.3 For an overview of the new features in 1.6, please see the announcement: http://googlewebtoolkit.blogspot.com/2009/03/google-web-toolkit-16-rc2-now-available.html The only real difference from RC1 should be some fixes I made for the hosted mode Jetty configuration issues that were reported with RC1: http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=milestone:1_6_RC2+status:Fixed,FixedNotReleased --Scott, on behalf of the GWT team --~--~-~--~~~---~--~~ 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: Announcing GWT 1.6 Release Candidate
hi googelybear, We don't preannounce release dates (mostly because we're never sure ourselves... you never know what issues people might run into using the RC). Unofficially, it looks like things are in pretty good shape, so I would be surprised if we haven't shipped within the next month or so-- just don't hold me to that. :) Scott On Fri, Mar 27, 2009 at 11:21 AM, googelybear wrote: > > Is there an approximate release date for 1.6? Like "in April" or "not > before christmas". I was unable to find such a page... > > On 18 Mrz., 21:32, Bruce Johnson wrote: > > Good news! Google Web Toolkit 1.6 RC is ready for you to download and try > > out: > > > > http://code.google.com/p/google-web-toolkit/downloads/list?q=1.6.2 > > > > For background on what's new in GWT 1.6, please see the still-in-progress > > doc: > > > > http://code.google.com/docreader/?p=google-web-toolkit-doc-1-6&s=goog... > > > > as well as previous 1.6-related announcements: > > > > "Announcing GWT 1.6 Milestone 1" > http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... > > > > and > > > > "Announcing GWT 1.6 Milestone 2" > http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... > > > > For complete details, the GWT issue tracker has the full list of changes: > > > > http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=miles... > > > > We expect this to be a short RC cycle, so a more comprehensive blog post > > with an overview of the features in GWT 1.6 should be just around the > > corner. > > > > -- Bruce, on behalf of the GWT team > > > --~--~-~--~~~---~--~~ 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: Spring and GWT 1.6RC
Hey, can you guys do me a favor and try out a fix? Just take the attached jar and put it on your classpath ahead of gwt-dev-.jar. See if it fixes the "not and instance of Servlet" problem (and doesn't cause other problems). Lemme know if that works, thanks, Scott PS: The Jsp compilation problem is unrelated, I think. By default, Eclipse does NOT put Sun's tools.jar on your classpath, even if you're using a JDK. The fix is to explicitly add the JDK's tools.jar to your classpath. On Mon, Mar 23, 2009 at 2:11 PM, Flemming Boller wrote: > Hi > > I have created an issuse, number 3496. > > /Flemming > > > On Mon, Mar 23, 2009 at 4:13 PM, Flemming Boller < > flemming.bol...@gmail.com> wrote: > >> Yes I can, that is the way I use spring and gwt. >> >> /FLemming >> >> >> On Mon, Mar 23, 2009 at 12:37 PM, Alejandro D. Garin wrote: >> >>> Hi, >>> >>> anyone can use Spring context listener in web.xml ? >>> >>> Example: >>> >>> >>> contextConfigLocation >>> /WEB-INF/applicationContext.xml >>> >>> >>> >>> >>> org.springframework.web.context.ContextLoaderListener >>> >>> >>> >>> On Mon, Mar 23, 2009 at 5:45 AM, Ed wrote: >>> Shouldn't this be reported as an "issue" ? I thought these issues would be solved now with the usage of Jetty instead Tomcat as mentioned here: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/7254dfe963f479ae?hl=en# -- Ed >>> >>> >>> >> > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~--- gwt-dev-patch.jar Description: application/java-archive
Re: Exception when add spring.jar in project GWT 1.6
Hey, can you guys do me a favor and try out a fix?
Just take the attached jar and put it on your classpath ahead of
gwt-dev-.jar. See if it fixes the "not and instance of Servlet"
problem (and doesn't cause other problems).
Lemme know if that works, thanks,
Scott
On Sun, Mar 22, 2009 at 10:14 AM, Gilles B wrote:
>
> I have the same problem with Hibernate. When I check the error line in
> jetty classes sources using Jade I see that my Servlet class is not an
> instance of "javax.servlet.Servlet", but this seems to be false
> looking to my servlet class inheritance.
>
> In fact this problem is due to a duplication of Servlet class in my
> libraries. Inside Eclise I check it using Ctl-Shift-T to find class
> Servlet locations, This class appears in "servlet-api.jar" but also
> inside GWT libraries. Il solve it removing "servlet-api.jar", I
> presume the Servlet class version doesn't match between jetty and the
> class version my compiler generate. May be you have something close to
> this with your servlet. May be an upgraded jar version, a change in
> libraries order or removeing duplicate (if it's not necessary) help to
> solve.
>
> On 19 mar, 14:03, magbyr wrote:
> > I'm having the same problem. Same project worked well on 1.5.3, but
> > not on 1.6RC.
> >
> > Fails on jsp and default servlet from
> Jetty:javax.servlet.UnavailableException: Servlet class
> > org.apache.jasper.servlet.JspServlet is not a
> javax.servlet.Servletjavax.servlet.UnavailableException: Servlet class
> > org.mortbay.jetty.servlet.DefaultServlet is not a
> > javax.servlet.Servlet
> >
> > Have you found a solution yet?
> >
> > wiltonj skrev:
> >
> >
> >
> > > Hi,
> > > I have a problem (exception) when add "spring.jar" in my project gwt
> > > 1.6 (WEB-INF/lib).
> >
> > > javax.servlet.UnavailableException: Servlet class
> > > org.apache.jasper.servlet.JspServlet is not a javax.servlet.Servlet
> > >at org.mortbay.jetty.servlet.ServletHolder.checkServletType
> > > (ServletHolder.java:377)
> > >at
> org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:
> > > 234)
> > >at org.mortbay.component.AbstractLifeCycle.start
> > > (AbstractLifeCycle.java:39)
> > >at org.mortbay.jetty.servlet.ServletHandler.initialize
> > > (ServletHandler.java:616)
> > >at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> > >at org.mortbay.jetty.webapp.WebAppContext.startContext
> > > (WebAppContext.java:1220)
> > >at org.mortbay.jetty.handler.ContextHandler.doStart
> > > (ContextHandler.java:513)
> > >at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
> > > 448)
> > >at br.gov.senado.lib.util.jetty.CustomJettyLauncher
> > > $WebAppContextWithReload.doStart(CustomJettyLauncher.java:387)
> > >at org.mortbay.component.AbstractLifeCycle.start
> > > (AbstractLifeCycle.java:39)
> > >at org.mortbay.jetty.handler.HandlerWrapper.doStart
> > > (HandlerWrapper.java:130)
> > >at org.mortbay.jetty.handler.RequestLogHandler.doStart
> > > (RequestLogHandler.java:115)
> > >at org.mortbay.component.AbstractLifeCycle.start
> > > (AbstractLifeCycle.java:39)
> > >at org.mortbay.jetty.handler.HandlerWrapper.doStart
> > > (HandlerWrapper.java:130)
> > >at org.mortbay.jetty.Server.doStart(Server.java:222)
> > >at org.mortbay.component.AbstractLifeCycle.start
> > > (AbstractLifeCycle.java:39)
> > >at br.gov.senado.lib.util.jetty.CustomJettyLauncher.start
> > > (CustomJettyLauncher.java:437)
> > >at
> com.google.gwt.dev.HostedMode.doStartUpServer(HostedMode.java:367)
> > >at
> com.google.gwt.dev.HostedModeBase.startUp(HostedModeBase.java:590)
> > >at com.google.gwt.dev.HostedModeBase.run(HostedModeBase.java:397)
> > >at com.google.gwt.dev.HostedMode.main(HostedMode.java:232)
> > >
> --
> > > [WARN] Failed startup of context
> > > br.gov.senado.lib.util.jetty.CustomJettyLauncher
> > > $webappcontextwithrel...@1f5b5fd{/,D:\Prodasen\ADMU\admu\war}
> > > org.mortbay.util.MultiException: Multiple exceptions
> > >at org.mortbay.jetty.servlet.ServletHandler.initialize
> > > (ServletHandler.java:587)
> > >at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> > >at org.mortbay.jetty.webapp.WebAppContext.startContext
> > > (WebAppContext.java:1220)
> > >at org.mortbay.jetty.handler.ContextHandler.doStart
> > > (ContextHandler.java:513)
> > >at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
> > > 448)
> > >at br.gov.senado.lib.util.jetty.CustomJettyLauncher
> > > $WebAppContextWithReload.doStart(CustomJettyLauncher.java:387)
> > >at org.mortbay.component.AbstractLifeCycle.start
> > > (AbstractLifeCycle.java:39)
> > >
> ---
> > > Spring WebApplictation initialization completed... But, the
> > > application not start...
> >
> > > INFO: Using context cla
Re: Announcing GWT 1.6 Milestone 1
On Fri, Feb 20, 2009 at 8:29 AM, Arthur Kalmenson wrote: > > 1) Backwards compatibility. If we updated JUnitShell to use HostedMode, > it > > seems like old test cases would probably break. The idea of a > > JUnitHostedMode is a good one... but how would we be able to tell which > one > > the user meant, since the JUnit framework is in control? > > So does this mean that GWTTestCases still spawns off a headless hosted > mode that's using an embedded Tomcat and not an embedded Jetty? > That is correct. It sounds like what I'm hearing though, is that there would be a lot of interest in us providing an explicit upgrade path, so that tests could be transitioned. If we did this, it might even make sense to deprecate the old-style but keep it in for now for backwards compatibility. --~--~-~--~~~---~--~~ 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: Announcing GWT 1.6 Milestone 1
To be honest, we kind of punted on a full JUnitShell port for a couple of reasons: 1) Backwards compatibility. If we updated JUnitShell to use HostedMode, it seems like old test cases would probably break. The idea of a JUnitHostedMode is a good one... but how would we be able to tell which one the user meant, since the JUnit framework is in control? 2) It should work okay for pure client-side testing. I take it from your message that you're doing something more sophisticated, that involves server-side code also? On Thu, Feb 19, 2009 at 4:15 AM, Netsurfer wrote: > > Hi, > I was using GWT 1.5 since some weeks ago, now I moved my application > to GWT1.6M1 in order to use the new war structure with a Spring server > application context. > Everything works fine with HostedMode: this version simplifies a lot > web frameworks integration. > > Now the problem: > I want to test my application with GwtTestCase but it uses JUnitShell > that extends GwtShell and there isn't any implementation like a > JUnitHostedMode that use the new war structure or, more in general, > the possibility to use HostedMode instead of GwtShell in a > GwtTestCase. > The consequence is that I'm not able to test my GWT Spring application > because every file inside the new war structure isn't reachable on a > GwtShell and the Spring context isn't loaded. > > Is there any solution? > > Thanks in advanced, > Marco > > On 6 Feb, 16:26, Scott Blum wrote: > > Greetings GWT developers, > > > > The GWT team is happy to announce the availability of 1.6 Milestone 1! > > Binary distributions are available for download directly from GWT's > Google > > Code project. > > > > http://code.google.com/p/google-web-toolkit/downloads/list?can=1&q=1.6.0 > > > > As always, milestone builds like this are use-at-your-own-risk. There are > > known bugs, and it definitely isn't ready for production use. Please > expect > > some trial and error getting everything to work. The javadoc that comes > > bundled with the distribution should be up-to-date, but the online > Developer > > Guide (http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) > is > > still very much a work in progress. We will be updating it over the next > > several weeks. In lieu of an up-to-date Developer Guide and release > notes, > > below are the major highlights relative to GWT 1.5.3. > > > > *** New Project Structure in GWT 1.6 *** > > > > One of the biggest changes to GWT 1.6 is a new project structure. The old > > output format has been replaced by the standard Java web app expanded > "war" > > format, and the actual directory name does default to "/war". Note that > the > > war directory is not only for compiler output; it is also intended to > > contain handwritten static resources that you want to be included in your > > webapp alongside GWT modules (that is, things you'd want to version > > control). Please also note that the "GWTShell" and "GWTCompiler" tools > will > > maintain their legacy behavior, but they have been deprecated in favor of > > new "HostedMode" and "Compiler" tools which use the new war output. When > 1.6 > > is officially released, we will be encouraging existing projects to > update > > to the new directory format and to use the new tools to take advantage of > > new features and for compatibility with future GWT releases. > > > > The sample projects provided in the GWT distribution provide an example > of > > correct new project configurations. For more details on the specifics of > the > > new project format, please see GWT 1.6 WAR design document ( > http://code.google.com/p/google-web-toolkit/wiki/WAR_Design_1_6). > > > > A couple of important changes we should highlight here: > > > > - Projects with server-side code (GWT RPC) must configure a "web.xml" > file > > at "/war/WEB-INF/web.xml". This web.xml file must define and publish any > > servlets associated with the web application. See the included DynaTable > > sample. Additionally, server-side library dependencies must be copied > into > > "/war/WEB-INF/lib". For example, any GWT RPC servlets must have a copy of > > gwt-servlet.jar in this folder. > > > > - HTML host pages will no longer typically be located in a GWT module's > > public path. Instead, we'll be recommending that people take advantage of > > the natural web app behavior for serving static files by placing host > pages > > anywhere in the war structure that makes sense.
Re: Announcing GWT 1.6 Milestone 1
What happens if you use a Java 1.5 VM?
On Wed, Feb 18, 2009 at 2:52 PM, Jim Tomlinson wrote:
>
> Is com.google.gwt.dev.Compiler with this release supposed to run on
> the Mac? Looks like library(s) are being shipped for it, but with OS X
> 10.5.6 and java 6 ("Java(TM) SE Runtime Environment (build 1.6.0_07-
> b06-153)") I'm getting:
>
> ...
> [INFO] Unpacking /Users/jimt/.m2/repository/com/google/gwt/gwt-dev/
> 1.6.0/gwt-dev-1.6.0-mac-libs.zipto
> /Users/jimt/.m2/repository/com/google/gwt/gwt-dev/1.6.0
> with Includes null and excludes:null
> [INFO] [gwt:compile {execution: default}]
> [INFO] establishing classpath list (buildClaspathList - scope =
> COMPILE)
> [INFO] google.webtoolkit.home (gwtHome) *not* set, using project POM
> for GWT dependencies
> Compiling module org.kuali.student.core.organization.ui.OrgEntry
> Invalid memory access of location rip=01160767
>
> /Users/jimt/src/kuali/student/ks-core/branches/ks-core-dev/core-ui/
> target/compile.sh: line 5: 6139 Segmentation fault "/System/
> Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/java" -
> XstartOnFirstThread -Xmx512m -cp $CLASSPATH
> com.google.gwt.dev.Compiler -gen /Users/jimt/src/kuali/student/ks-core/
> branches/ks-core-dev/core-ui/target/.generated -logLevel INFO -style
> OBF -war /Users/jimt/src/kuali/student/ks-core/branches/ks-core-dev/
> core-ui/target/ks-core-ui-0.0.1-SNAPSHOT
> org.kuali.student.core.organization.ui.OrgEntry
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Exception attempting to run script - compile.sh
>
> I saw this same issue on Ubuntu with 1.6.0_07. Upgrading to _12 fixed
> the problem there, but there's no such upgrade avenue (yet) on OS X.
> Known issue? Thanks.
>
> - Jim Tomlinson
>
> On Feb 6, 7:26 am, Scott Blum wrote:
> > Greetings GWT developers,
> >
> > The GWT team is happy to announce the availability of 1.6 Milestone 1!
> > Binary distributions are available for download directly from GWT's
> Google
> > Code project.
> >
> > http://code.google.com/p/google-web-toolkit/downloads/list?can=1&q=1.6.0
> ...
>
> >
>
--~--~-~--~~~---~--~~
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: Announcing GWT 1.6 Milestone 1
Would people be happier if we called this the "official community-supported GWT/Maven integration"? :) On Fri, Feb 13, 2009 at 10:08 AM, Arthur Kalmenson wrote: > I think you'll note that GWT is in the central Maven repository > (http://repo1.maven.org/maven2/com/google/gwt/) and there are > currently at least two Maven plugins (being merged), the gwt-maven > plugin: http://code.google.com/p/gwt-maven/ and the Codehaus GWT > plugin: http://mojo.codehaus.org/gwt-maven-plugin/. I and a number of > other people use Maven every day, and it works OK. I'm sure it could > be better, but it does work. > --~--~-~--~~~---~--~~ 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: Announcing GWT 1.6 Milestone 1
On Wed, Feb 11, 2009 at 4:29 AM, Alex dP (Violet UML Editor, WebVNC...) < alexandre.de.pelleg...@gmail.com> wrote: > > Congratulation for this release. > > Unfortunately, there's still nothing about Maven support. No official > repository, no official plugin I hope this will arrive this > Milestone 2. > > Regards, > Alexandre de Pellegrin This is not likely for 1.6... we simply don't have any Maven users (much less experts) among the contributors. If this is something a lot of people would find valuable, it would be great if someone in the community could step up. I will note that we made some changes in 1.6 regarding ClassLoaders that should remove barriers to running GWT hosted mode (and unit tests) from within Maven. Scott --~--~-~--~~~---~--~~ 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: Announcing GWT 1.6 Milestone 1
On Mon, Feb 9, 2009 at 9:47 AM, logicpeters wrote: > > "Note that the > war directory is not only for compiler output; it is also intended to > contain handwritten static resources that you want to be included in > your > webapp alongside GWT modules (that is, things you'd want to version > control)." > > I'm not following... Do you mean for us to include these static > resources in the compiler output directory and maintain this directory > under source control (with generated code alongside static source, > such as index.html and css files)? That seems like a bad idea to me. > Not exactly... the compiler output directory is considered to be "/war/" NOT "/war" itself really. In other words, you can put whatever resources you want into the top-level war directory, the compiler generated files will always be put into the moduleName subdirectory under this, so as not to conflict. Why not enforce the standard J2EE project path (see Sun's blueprints), > and maintain these files under /src/conf. > We might have to look into this. Scott --~--~-~--~~~---~--~~ 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: Announcing GWT 1.6 Milestone 1
Hi Sebastien, It's actually fairly compatible, the difference is more in attitude and expectation. You would provide the WEB-INF directory yourself, GWT no longer tries to control everything. The model is more that GWT can plug in easily to existing web apps. For example, you would also want to setup build rules to compile your server-side code into WEB-INF/classes. Scott On Mon, Feb 9, 2009 at 1:35 AM, Sebastien wrote: > > Hi, > > I take a look on the build.xml of samples. I didn't see any special > difference. > Here is a part of my build.xml : > fork="true" failonerror="true" taskName="gwtc"> > > > > name="**/*.jar"/> > > > => > [gwtc] Compiling module com.raisepartner.prism.PRISM > [gwtc]Compiling 10 > permutations > [gwtc] Permutation compile > succeeded > [gwtc]Linking into > war > [gwtc] Link > succeeded > [gwtc]Compilation succeeded -- > 483,002s > > The output is 'war' directory at the root of my project. This > directory contains only the module directory. There is no WEB-INF > directory created. Is it the expected behavior ? > By looking the samples I understand that my main html page (the one > calling the nocache.js) must me copied manually at the root of the war > directory. The content of the .public is copied into war/ > . I expected the content would be copied at the root of the > 'war' directory. > > So my conclusion is that there is no change compared to the > 1.5.3 ... :-( > > Regards, > Seb > On 8 fév, 23:45, Dop Sun wrote: > > I guess in the sample projects (included in the M1 build), there is > > build file for each and every of them, and within that, there build > > tasks for the project. Maybe, you can have a try what there? > > > > On Feb 9, 2:49 am, Sebastien wrote: > > > > > Hi, > > > > > I am interested to migrate from the 1.5.3 to the 1.6.0 M1. When I use > > > this M1 with -war option, the the compiler output is not like an > > > expanded war. I tried to specify all parameters (-war, -gen, - > > > extra ..) without success. The output of the compiler is always > > > similar to the output of the 1.5.3 compiler. The compiler indicates > > > the 1.6.0 version, so I am sure to use the 1.6. I am under linux > > > (ubuntu). > > > > > Do you have any idea why the compiler output is not like an expanded > > > war ? > > > > > Regards, > > > Seb > > > > > On 6 fév, 16:26, Scott Blum wrote: > > > > > > Greetings GWT developers, > > > > > > The GWT team is happy to announce the availability of 1.6 Milestone > 1! > > > > Binary distributions are available for download directly from GWT's > Google > > > > Code project. > > > > > > > http://code.google.com/p/google-web-toolkit/downloads/list?can=1&q=1.6.0 > > > > > > As always, milestone builds like this are use-at-your-own-risk. There > are > > > > known bugs, and it definitely isn't ready for production use. Please > expect > > > > some trial and error getting everything to work. The javadoc that > comes > > > > bundled with the distribution should be up-to-date, but the online > Developer > > > > Guide ( > http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) is > > > > still very much a work in progress. We will be updating it over the > next > > > > several weeks. In lieu of an up-to-date Developer Guide and release > notes, > > > > below are the major highlights relative to GWT 1.5.3. > > > > > > *** New Project Structure in GWT 1.6 *** > > > > > > One of the biggest changes to GWT 1.6 is a new project structure. The > old > > > > output format has been replaced by the standard Java web app expanded > "war" > > > > format, and the actual directory name does default to "/war". Note > that the > > > > war directory is not only for compiler output; it is also intended to > > > > contain handwritten static resources that you want to be included in > your > > > > webapp alongside GWT modules (that is, things you'd want to version > > > > control). Please also note that the "GWTShell" and "GWTCompiler" > tools will > > > > maintain their legacy behavior, but they have been deprecated in > favor of > > > > new "HostedMode" and "
Re: Announcing GWT 1.6 Milestone 1
On Sun, Feb 8, 2009 at 12:11 PM, Itamar Ravid wrote:
> The difficulty arises when using Hosted Mode. First, I have to copy a
> modified web.xml to ${project}/tomcat/webapps/ROOT. This web.xml routes all
> requests to /services/* to my springDispatcher. This web.xml is different
> than the one I distribute with my WAR, since it also includes mapping for
> the GWTShellServlet. Also, in order for serialization to work, I have to
> compile my project once (using GWTCompiler) and copy all resulting *.gwt.rpc
> files to ${project}/tomcat/webapps/ROOT/${module}/. This occurs because the
> GWTShellServlet generates these dynamically as GWT-RPC requests arrive.
>
> I've semi-automated the whole process using Ant tasks, and I'm aware of the
> gwt-maven plugin which provides some of this functionality, but I'd like to
> know whether the situation has been fully or partly addressed with the 1.6
> release.
>
Itamar,
I think you should find 1.6 much easier once you've switched over from
GWTShell to HostedMode. Just use your real web.xml in hosted mode to map in
your springDispatcher; you no longer need to use GWTShellServlet at all.
Scott
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
Announcing GWT 1.6 Milestone 1
Greetings GWT developers, The GWT team is happy to announce the availability of 1.6 Milestone 1! Binary distributions are available for download directly from GWT's Google Code project. http://code.google.com/p/google-web-toolkit/downloads/list?can=1&q=1.6.0 As always, milestone builds like this are use-at-your-own-risk. There are known bugs, and it definitely isn't ready for production use. Please expect some trial and error getting everything to work. The javadoc that comes bundled with the distribution should be up-to-date, but the online Developer Guide (http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) is still very much a work in progress. We will be updating it over the next several weeks. In lieu of an up-to-date Developer Guide and release notes, below are the major highlights relative to GWT 1.5.3. *** New Project Structure in GWT 1.6 *** One of the biggest changes to GWT 1.6 is a new project structure. The old output format has been replaced by the standard Java web app expanded "war" format, and the actual directory name does default to "/war". Note that the war directory is not only for compiler output; it is also intended to contain handwritten static resources that you want to be included in your webapp alongside GWT modules (that is, things you'd want to version control). Please also note that the "GWTShell" and "GWTCompiler" tools will maintain their legacy behavior, but they have been deprecated in favor of new "HostedMode" and "Compiler" tools which use the new war output. When 1.6 is officially released, we will be encouraging existing projects to update to the new directory format and to use the new tools to take advantage of new features and for compatibility with future GWT releases. The sample projects provided in the GWT distribution provide an example of correct new project configurations. For more details on the specifics of the new project format, please see GWT 1.6 WAR design document ( http://code.google.com/p/google-web-toolkit/wiki/WAR_Design_1_6). A couple of important changes we should highlight here: - Projects with server-side code (GWT RPC) must configure a "web.xml" file at "/war/WEB-INF/web.xml". This web.xml file must define and publish any servlets associated with the web application. See the included DynaTable sample. Additionally, server-side library dependencies must be copied into "/war/WEB-INF/lib". For example, any GWT RPC servlets must have a copy of gwt-servlet.jar in this folder. - HTML host pages will no longer typically be located in a GWT module's public path. Instead, we'll be recommending that people take advantage of the natural web app behavior for serving static files by placing host pages anywhere in the war structure that makes sense. For exmaple, you might want to load a GWT module from a JSP page located in the root of your web app. To keep such handwritten static files separate from those produced by the GWT compiler, the latter will be placed into module-specific subdirectories. Any page that wishes to include a GWT module can do so via a script tag by referencing the GWT-produced ".nocache.js script" within that module's subdirectory. As of 1.6, we'll be recommending that only module-specific resources used directly by GWT code, such as image files needed by widgets, should remain on the public path. See the included Showcase sample for some examples of this distinction. - When you do need to load resources from a module's public path, always construct an absolute URL by prepending GWT.getModuleBaseURL(). For example, 'GWT.getModuleBaseURL() + "dir/file.ext"'. This advice has not changed, but in the past it was easy to be sloppy with this, because the host page and GWT module typically lived in the same directory, so using a relative URL would usually do the right thing. Now that GWT modules live in a subdirectory, you must reference public resources through GWT.getModuleBaseURL(). *** Hosted Mode Enhancements *** Although the legacy GWTShell still uses an embedded Tomcat server, the new HostedMode runs Jetty instead. There is also a new "Restart Server" button on the main hosted mode window. Clicking this button restarts the internal Jetty server, which allows Java code changes to take effect on the server without having to completely exit and restart hosted mode. This is useful when making code changes to RPC servlets, or when serializable RPC types are modified and the server and client are out of sync. *** New EventHandler System *** Event handlers have been added to replace the old event listeners used by Widgets, History, and various other classes. The new system has a few differences from the old system: - EventHandler methods always take a single parameter: the GwtEvent that the Widget fired. For example, ClickHandler has a single method onClick(ClickEvent). - Each GwtEvent contains accessors relevant to the event, such as the key that was pressed on KeyEvents. Native events provide access to the underlyi
Re: PropertyUtils usage?
It's part of the embedded Tomcat. This should go away in the future as Tomcat is deprecated in 1.6. On Mon, Feb 2, 2009 at 5:28 AM, Ed wrote: > > Hellu all, > > Why is GWT using his own version of the > org.apache.commons.beanutils.PropertyUtils class in the gwt-dev jar ? > (probably there are more of these classes). > > This can cause nasty conflicts, which I just had :( > For example: Dozer also uses this apache class but because the gwt-dev > jar was included (t's shouldn't which I changed now) and appeared > first on the classpath, Dozer used the PropertyUtils class in de gwt- > dev jar which caused out of memory errors :(... > > -- Ed > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Call for critical 1.6 bugs
Hi all, We've narrowed down the set of bugs we'd like to fix for GWT 1.6. Our plan is for a very short release cycle this time, which forces us to fix only a small set of bugs. Of course, we don't want to miss anything critical. Here is the current set of Critical 1.6 bugs we intend to fix: http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=milestone:1_6_RC+-status:FixedNotReleased+priority:Critical If you know of some burning issue that we've missed, please use this thread to suggest bugs to add to this list, and explain why it's critically important. The kinds of issues we consider to be critical include bugs that affect a large number of users, possible security issues, or bugs that cannot be worked around easily (such as GWT compiler crashes). Please DO NOT use this thread to debate whether any particular issue should be in our out. We just want to collect a list of critical issues, and we will consider each suggestion individually. Thanks! Scott --~--~-~--~~~---~--~~ 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: Possible bug? UnsupportedOperationException: TreeSet not implemented
TreeSet wasn't implemented in milestone 2. You should upgrade to 1.5.2 (GA); TreeSet is implemented there. On Wed, May 21, 2008 at 8:55 PM, Mark Renouf <[EMAIL PROTECTED]> wrote: > > I've been using source builds of GWT because of other issues I've run > into with 1.5M2, and I just hit this one. This is not a showstopper, > but I wanted to post it because it violates the general contract of > "if it works in hosted mode, it works in web mode". > > GWT Release: 0.0.2856 (trunk) > Description: Use of java.util.TreeSet, works in hosted mode, error in > web mode > Browser: Firefox (3.0b5) > > Error console message: >Error: uncaught exception: > java.lang.UnsupportedOperationException: TreeSet not implemented > > > Workaround if you have one: > > Rewrite code to avoid use of TreeSet... :-( > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
