migrate GWT 2.1.1 to 2.2 error
Hello, i just try GWT 2.2 on my project, i just change my POM file to use version 2.2 and when i try to compile i have this error : Loading inherited module 'com.google.gwt.user.User' [INFO]Loading inherited module 'com.google.gwt.user.RemoteService' [INFO] [ERROR] Unexpected error while processing XML [INFO] java.lang.NoClassDefFoundError: com/google/gwt/core/ext/GeneratorExt [INFO] at java.lang.ClassLoader.defineClass1(Native Method) [INFO] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) [INFO] at java.lang.ClassLoader.defineClass(ClassLoader.java:616) [INFO] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [INFO] at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) [INFO] at java.net.URLClassLoader.access$000(URLClassLoader.java:58) [INFO] at java.net.URLClassLoader$1.run(URLClassLoader.java:197) [INFO] at java.security.AccessController.doPrivileged(Native Method) [INFO] at java.net.URLClassLoader.findClass(URLClassLoader.java:190) [INFO] at java.lang.ClassLoader.loadClass(ClassLoader.java:307) [INFO] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) [INFO] at java.lang.ClassLoader.loadClass(ClassLoader.java:248) [INFO] at com.google.gwt.dev.cfg.ModuleDefSchema$ClassAttrCvt.convertToArg(ModuleDefSchema.java:778) [INFO] at com.google.gwt.dev.util.xml.HandlerArgs.convertToArg(HandlerArgs.java:64) [INFO] at com.google.gwt.dev.util.xml.HandlerMethod.invokeBegin(HandlerMethod.java:221) [INFO] at com.google.gwt.dev.util.xml.ReflectiveParser$Impl.startElement(ReflectiveParser.java:274) ... Idid'nt have any problem with older version of GWT. -- 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: single-origin error, shouldn't be happening?
Created issue http://code.google.com/p/google-web-toolkit/issues/detail?id=3795 to track ... On Jun 26, 9:29 am, Brice wrote: > I was able to use the "emulate IE7" hack to get IE8 to work, but > that's nasty and I keep hoping there's going to be a way I can upgrade > to a recent release of GWT. > > On Jun 25, 11:20 pm, Brice wrote: > > > > > Good evening, > > > I'm revisiting a project that I worked on a year back that ran into > > trouble when I tried to upgrade to 1.5.3 from 1.5.2. > > > Here's a post that I made at that time: > > >http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... > > > In a nutshell, the project uses GWT to provide a "rich" interface for > > a CD-ROM product, so it runs w/o any backend web-server. However, it > > *does* use RequestBuilder to load XML and JSON data from the CD - but > > the data is all "local" to where the GWT app is initialized from. > > > This works fabulously in Safari, FireFox, and IE7 - yay. But, when I > > tried to upgrade last year to 1.5.3, I found that GWT was throwing an > > exception about violating single-origin-policy. This is *not* hosted > > mode, this is compiled-mode, loading the GWT app from the local file- > > system. I tried upgrading to 1.6.x a month back and found that I still > > get the same problem. > > > With the recent release of IE8, I can't continue to use GWT 1.5.2 and > > hope to stay compatible in new browsers, so what can I do?! I'm > > assuming GWT is using some kind of internal logic to determine if an > > SOP violation would occur, without actually giving the browser the > > request, since the browser seems perfectly happy loading the XML and > > JSON from the local file-system in 1.5.2. Any way to dig into > > something and disable this check? Or change the way I'm loading? > > > Thanks much! > > Brice --~--~-~--~~~---~--~~ 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: single-origin error, shouldn't be happening?
I was able to use the "emulate IE7" hack to get IE8 to work, but that's nasty and I keep hoping there's going to be a way I can upgrade to a recent release of GWT. On Jun 25, 11:20 pm, Brice wrote: > Good evening, > > I'm revisiting a project that I worked on a year back that ran into > trouble when I tried to upgrade to 1.5.3 from 1.5.2. > > Here's a post that I made at that time: > > http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... > > In a nutshell, the project uses GWT to provide a "rich" interface for > a CD-ROM product, so it runs w/o any backend web-server. However, it > *does* use RequestBuilder to load XML and JSON data from the CD - but > the data is all "local" to where the GWT app is initialized from. > > This works fabulously in Safari, FireFox, and IE7 - yay. But, when I > tried to upgrade last year to 1.5.3, I found that GWT was throwing an > exception about violating single-origin-policy. This is *not* hosted > mode, this is compiled-mode, loading the GWT app from the local file- > system. I tried upgrading to 1.6.x a month back and found that I still > get the same problem. > > With the recent release of IE8, I can't continue to use GWT 1.5.2 and > hope to stay compatible in new browsers, so what can I do?! I'm > assuming GWT is using some kind of internal logic to determine if an > SOP violation would occur, without actually giving the browser the > request, since the browser seems perfectly happy loading the XML and > JSON from the local file-system in 1.5.2. Any way to dig into > something and disable this check? Or change the way I'm loading? > > Thanks much! > Brice --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
single-origin error, shouldn't be happening?
Good evening, I'm revisiting a project that I worked on a year back that ran into trouble when I tried to upgrade to 1.5.3 from 1.5.2. Here's a post that I made at that time: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/4fefe354a5182cbb In a nutshell, the project uses GWT to provide a "rich" interface for a CD-ROM product, so it runs w/o any backend web-server. However, it *does* use RequestBuilder to load XML and JSON data from the CD - but the data is all "local" to where the GWT app is initialized from. This works fabulously in Safari, FireFox, and IE7 - yay. But, when I tried to upgrade last year to 1.5.3, I found that GWT was throwing an exception about violating single-origin-policy. This is *not* hosted mode, this is compiled-mode, loading the GWT app from the local file- system. I tried upgrading to 1.6.x a month back and found that I still get the same problem. With the recent release of IE8, I can't continue to use GWT 1.5.2 and hope to stay compatible in new browsers, so what can I do?! I'm assuming GWT is using some kind of internal logic to determine if an SOP violation would occur, without actually giving the browser the request, since the browser seems perfectly happy loading the XML and JSON from the local file-system in 1.5.2. Any way to dig into something and disable this check? Or change the way I'm loading? Thanks much! Brice --~--~-~--~~~---~--~~ 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: SOP, 1.5.3, *not* hosted mode ...
Has anyone else run into this? I am going to be working on a number of similar "client-side only" projects and I would hate to be stuck at 1.5.2 for all eternity ... Is there an open issue for this already? Not for hosted mode, but compiled mode? Thanks! On Jan 29, 11:41 am, Brice wrote: > Good morning, > > I am working on a project that uses GWT in pure client-side mode, i.e. > there's no server. This is an interface for content on a CD/DVD (PDF > files, etc.). GWT provides the interface & search functionality by > loading XML files that contain meta-data about the content. > > I develop in hosted mode, but soon after I get something working, I > compile and load up my static HTML/.js in target browsers (IE, Safari, > Firefox, etc.). With 1.5.3, what I found is that in compiled mode, IE > 6, Safari 3.x, Firefox 3.x all work fine ... they can load the XML > data file, no worries. Worked in hosted mode, too. However, in IE 7, I > got an exception re: SOP. When I flip back to 1.5.2, IE 7 works. > > What's going on here? I saw a number of threads (of very annoyed > developers) with respect to Hosted mode, but the changes there seemed > to be "protections" so that you wouldn't have different behaviour when > you move to compiled mode. I have the opposite. In 1.5.3, hosted mode > works fine, but compiled mode doesn't ... but only on IE 7. On top of > that, it works fine in other browsers - which I would expect (if > anything) to have more strict interpretations of SOP. > > I'd love to move back to 1.5.3, but for now, I'm stuck with 1.5.2. > > Thanks, > Brice --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
SOP, 1.5.3, *not* hosted mode ...
Good morning, I am working on a project that uses GWT in pure client-side mode, i.e. there's no server. This is an interface for content on a CD/DVD (PDF files, etc.). GWT provides the interface & search functionality by loading XML files that contain meta-data about the content. I develop in hosted mode, but soon after I get something working, I compile and load up my static HTML/.js in target browsers (IE, Safari, Firefox, etc.). With 1.5.3, what I found is that in compiled mode, IE 6, Safari 3.x, Firefox 3.x all work fine ... they can load the XML data file, no worries. Worked in hosted mode, too. However, in IE 7, I got an exception re: SOP. When I flip back to 1.5.2, IE 7 works. What's going on here? I saw a number of threads (of very annoyed developers) with respect to Hosted mode, but the changes there seemed to be "protections" so that you wouldn't have different behaviour when you move to compiled mode. I have the opposite. In 1.5.3, hosted mode works fine, but compiled mode doesn't ... but only on IE 7. On top of that, it works fine in other browsers - which I would expect (if anything) to have more strict interpretations of SOP. I'd love to move back to 1.5.3, but for now, I'm stuck with 1.5.2. Thanks, Brice --~--~-~--~~~---~--~~ 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: #token fragment sometimes cause page reload, sometimes not?
Thomas,
Thanks much for the prompt response and no less than three
workarounds! I was not the individual who created this issue, but I
had assumed I wasn't the only one seeing this ;-) Just didn't see any
other threads when I searched the group.
I'll take a whack at this and report back if I have any further
problems.
Thanks,
Brice
On Sep 17, 10:55 am, Thomas Broyer <[EMAIL PROTECTED]> wrote:
> On 17 sep, 06:09, Brice <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > Good evening. I am working on a new GWT app and I noticed a few
> > strange behaviors in IE 7 that I didn't see in FireFox / Safari.
> > Particularly that a link with a #token will cause a page refresh if
> > its in my wrapper HTML, but not if its generated by GWT. This doesn't
> > happen (from what I can see) in FireFox / Safari.
>
> > Here's the scenario: my wrapper HTML has been designed externally, the
> > GWT just renders into the content area of the page. Outside of this
> > area are two "tabs". Instead of linking to different pages, the hrefs
> > are #tabA and #tabB. After the GWT EntryModule has run, this *should*
> > just fire History changed events, right? That's what it does in FF and
> > Safari. In IE, it reloads the page, and since my EntryModule invokes
> > fireCurrentHistoryState(), the right state is initialized.
>
> > Within the GWT module, links are rendered with tokens, too. When these
> > are clicked, the page does not reload. As expected, the History
> > changed event is fired, and the new application state is loaded.
>
> > Am I going about this incorrectly? Is this an IE ideosyncracy?
>
> Yes (search the issue tracker, this has been reported recently –maybe
> it was you?–)
>
> > Is there a workaround?
>
> Attach onclick handlers to your links to call History.newItem and
> Event.preventDefault(). That's what GWT's Hyperlink do to workaround
> this IE "quirk".
>
> To attach the onclick, you could loop through the
> Document.get().getElementsByTagName("a") (before attaching your GWT
> widgets) and call DOM.setEventListener and DOM.sinkEvents.
> However, I'd rather expose the History.newItem method as a global JS
> function through JSNI and attach the onclick handlers in the host page
> HTML:
>
> Another option is to just have placeholders in your HTML host page and
> "inject" GWT Hyperlinks in there (RootPanel.get("tab1link").add(new
> Hyperlink("Tab 1", "tab1"))).
>
> ...if only there were a SimpleHyperlink widget with a static wrap()
> method to wrap an and set the EventListener automatically...- Hide
> quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
#token fragment sometimes cause page reload, sometimes not?
Good evening. I am working on a new GWT app and I noticed a few strange behaviors in IE 7 that I didn't see in FireFox / Safari. Particularly that a link with a #token will cause a page refresh if its in my wrapper HTML, but not if its generated by GWT. This doesn't happen (from what I can see) in FireFox / Safari. Here's the scenario: my wrapper HTML has been designed externally, the GWT just renders into the content area of the page. Outside of this area are two "tabs". Instead of linking to different pages, the hrefs are #tabA and #tabB. After the GWT EntryModule has run, this *should* just fire History changed events, right? That's what it does in FF and Safari. In IE, it reloads the page, and since my EntryModule invokes fireCurrentHistoryState(), the right state is initialized. Within the GWT module, links are rendered with tokens, too. When these are clicked, the page does not reload. As expected, the History changed event is fired, and the new application state is loaded. Am I going about this incorrectly? Is this an IE ideosyncracy? Is there a workaround? The current module only has two tabs, and the "load" that's done by the module isn't horrible, so I could live with it, but I'd rather not! Thanks, Brice --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
