Tuesday, August 22, 2023

Re: com.ait.toolkit.core.Core not found in Gwt-tour

Here is mine: It uses JsInterop. I always wanted to make this available on github but I never found the time...

Αnyway the story of 3rd party jsinterop libs in GWT is not so great:
  1. Most of the js libs expect to be loaded in the page while the GWT code lives in an iframe.
  2. You need code to load the js, css and possibly dynamically adjust the paths of assets such as sprites.
  3. The loader code should protect the page from multiple inclusion.
  4. and probably more that I can't remember
If you are interested I could probably unearth the instructions on how to properly load HopScotch and how to use it.

The howto use it should be obvious though since it is jsinterop which means that you can rely on the js documentation.

Vassilis

package com.yourcompany.lib.gwt.client.js;

import elemental2.core.JsArray;
import jsinterop.annotations.JsFunction;
import jsinterop.annotations.JsOverlay;
import jsinterop.annotations.JsPackage;
import jsinterop.annotations.JsType;

@JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "hopscotch")
public class Hopscotch {
    public static class Event {
        public static final String start = "start";
        public static final String end = "end";
        public static final String next = "next";
        public static final String prev = "prev";
        public static final String show = "show";
        public static final String close = "close";
        public static final String error = "error";
    }

    public static class Placement {
        public static final String top = "top";
        public static final String left = "left";
        public static final String bottom = "bottom";
        public static final String right = "right";
    }

    @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
    public static class Step {
        // Mandatory
        /**
         * target [STRING/ELEMENT/ARRAY] - id of the target DOM element or DOM element itself. It is also possible to
         * define an array of several targets. If an array is provided, Hopscotch will use the first target that exists
         * on the page and disregard the rest.
         *
         */
        public Object target;
        public String placement;

        // Optional
        public String title;
        public String content;
        public int width;
        public int padding;
        public int xOffset;
        public int yOffset;
        public int arrowOffset;
        public int delay;
        public int zindex;
        public boolean showNextButton;
        public boolean showPrevButton;
        public boolean showCTAButton;
        public String ctaLabel;
        public boolean multipage;
        public boolean showSkip;
        public boolean fixedElement;
        public boolean nextOnTargetClick;
        public Callback onPrev;
        public Callback onNext;
        public Callback onShow;
        public Callback onCTA;

        @JsOverlay
        public static Step create(String placement, String target) {
            final Step step = new Step();
            step.placement = placement;
            step.target = target;
            return step;
        }
    }

    @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
    public static class Tour {
        // Mandatory
        public String id;
        public JsArray<Step> steps;
        // Optional
        public int bubbleWidth;
        public int bubblePadding;
        public boolean smoothScroll;
        public int scrollDuration;
        public int scrollTopMargin;
        public boolean showCloseButton;
        public boolean showPrevButton;
        public boolean showNextButton;
        public int arrowWidth;
        public boolean skipIfNoElement;
        public boolean nextOnTargetClick;
        public Object container;
        public boolean fixedContainer;

        // These are objects so they could accept strings / arrays for the
        // helper
        // registration interface to work.
        public Object onNext;
        public Object onPrev;
        public Object onStart;
        public Object onEnd;
        public Object onClose;
        public Object onError;

        // i18n
        @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
        public static class I18N {
            public String nextBtn;
            public String prevBtn;
            public String doneBtn;
            public String skipBtn;
            public String closeTooltip;
            public String[] stepNums;
        }

        public I18N i18n;

        @JsOverlay
        public static void initTour(Tour tour) {
            tour.i18n = new Tour.I18N();
            tour.steps = new JsArray<Step>();
        }

        @JsOverlay
        public static Tour createTour() {
            final Tour tour = new Tour();
            initTour(tour);
            return tour;
        }
    }

    @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
    public static class Callout extends Step {
        // Mandatory
        public String id;
    }

    /* this may be step ? should we delete this */
    @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "HopscotchBubble")
    public static class Bubble {
    }

    @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "HopscotchCalloutManager")
    public static class CalloutManager {
        public static native Bubble createCallout(Callout callout);

        public static native Bubble getCallout(String id);

        public static native void removeCallout(String id);

        public static native void removeAllCallouts();
    }

    @JsFunction
    public static interface Callback {
        public void execute();
    }

    public static native Hopscotch startTour(Tour tour, int stepNum);

    public static native Hopscotch startTour(Tour tour);

    public static native Hopscotch showStep(int idx);

    public static native Hopscotch prevStep();

    public static native Hopscotch nextStep();

    public static native Hopscotch endTour();

    public static native Hopscotch endTour(boolean clearCookie);

    public static native Hopscotch configure(Tour options);

    public static native Tour getCurrTour();

    public static native int getCurrStepNum();

    public static native String getState();

    public static native Hopscotch listen(String eventName, Callback callback);

    public static native Hopscotch unlisten(String eventName, Callback callback);

    public static native Hopscotch removeCallbacks(String eventName, boolean tourOnly);

    public static native Hopscotch removeCallbacks(String eventName);

    public static native Hopscotch removeCallbacks();

    public static native void registerHelper(String id, Callback helper);

    public static native void unregisterHelper(String id);

    public static native Hopscotch resetDefaultI18N();

    public static native Hopscotch resetDefaultOptions();

    public static native CalloutManager getCalloutManager();
}


On Tue, Aug 22, 2023 at 5:05 PM Frank <frank.wynants@gmail.com> wrote:
Looking at my code.

It seems that I also had troubles getting this to work. I actually copied code from the GWT-tour project in my own project.
Also looking at the code I see this is using JSNI. If this is a new project, you probably want to avoid using JSNI in favor of JsInterop.

I could not found any JsInterop library for hopscotch, so best bet is to create it yourself, or look for another library which does the same thing. Or create your own pure GWT library doing this...

Op dinsdag 22 augustus 2023 om 15:58:54 UTC+2 schreef Frank:
I think gwt-tour is part of Ahome as far as I know.


Have you had this working in the past and if so what change broke it?
What version of GWT are you using? I have this working in GWT2.9.0...





Op donderdag 17 augustus 2023 om 14:45:22 UTC+2 schreef Colin Alworth:
I'm broadly aware that gwt-tour exists (though it hasnt had an update in 8 years), but I don't see any com.ait packages or references in it. On the other hand, I think com.ait.toolkit.core refers to https://github.com/dikalo/ahome-core/, which is a different thing entirely. It appears that ahome-core shadows a few GWT classes, which likely makes it incompatible with newer GWT versions - did you recently update GWT version and then start having this issue?

On Thursday, August 17, 2023 at 7:11:43 AM UTC-5 prasenji...@altizon.com wrote:
GWT Module com.ait.toolkit.core.Core not found in project sources or resources

in Gwt-Tour library HopScotch.gwt.xml has inherited com.ait.toolkit.core.Core which is not found bye goal org.codehaus.mojo:gwt-maven-plugin

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6c238278-9295-46bd-ab8a-b520cd4cedefn%40googlegroups.com.


--
Vassilis Virvilis

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAKbOjExx534f72JZoV3qOuq78n%3D27Ox%3DDzZjLJnYrkT-CeLN2w%40mail.gmail.com.

Re: com.ait.toolkit.core.Core not found in Gwt-tour

Looking at my code.

It seems that I also had troubles getting this to work. I actually copied code from the GWT-tour project in my own project.
Also looking at the code I see this is using JSNI. If this is a new project, you probably want to avoid using JSNI in favor of JsInterop.

I could not found any JsInterop library for hopscotch, so best bet is to create it yourself, or look for another library which does the same thing. Or create your own pure GWT library doing this...

Op dinsdag 22 augustus 2023 om 15:58:54 UTC+2 schreef Frank:
I think gwt-tour is part of Ahome as far as I know.


Have you had this working in the past and if so what change broke it?
What version of GWT are you using? I have this working in GWT2.9.0...





Op donderdag 17 augustus 2023 om 14:45:22 UTC+2 schreef Colin Alworth:
I'm broadly aware that gwt-tour exists (though it hasnt had an update in 8 years), but I don't see any com.ait packages or references in it. On the other hand, I think com.ait.toolkit.core refers to https://github.com/dikalo/ahome-core/, which is a different thing entirely. It appears that ahome-core shadows a few GWT classes, which likely makes it incompatible with newer GWT versions - did you recently update GWT version and then start having this issue?

On Thursday, August 17, 2023 at 7:11:43 AM UTC-5 prasenji...@altizon.com wrote:
GWT Module com.ait.toolkit.core.Core not found in project sources or resources

in Gwt-Tour library HopScotch.gwt.xml has inherited com.ait.toolkit.core.Core which is not found bye goal org.codehaus.mojo:gwt-maven-plugin

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6c238278-9295-46bd-ab8a-b520cd4cedefn%40googlegroups.com.

Re: com.ait.toolkit.core.Core not found in Gwt-tour

I think gwt-tour is part of Ahome as far as I know.


Have you had this working in the past and if so what change broke it?
What version of GWT are you using? I have this working in GWT2.9.0...





Op donderdag 17 augustus 2023 om 14:45:22 UTC+2 schreef Colin Alworth:
I'm broadly aware that gwt-tour exists (though it hasnt had an update in 8 years), but I don't see any com.ait packages or references in it. On the other hand, I think com.ait.toolkit.core refers to https://github.com/dikalo/ahome-core/, which is a different thing entirely. It appears that ahome-core shadows a few GWT classes, which likely makes it incompatible with newer GWT versions - did you recently update GWT version and then start having this issue?

On Thursday, August 17, 2023 at 7:11:43 AM UTC-5 prasenji...@altizon.com wrote:
GWT Module com.ait.toolkit.core.Core not found in project sources or resources

in Gwt-Tour library HopScotch.gwt.xml has inherited com.ait.toolkit.core.Core which is not found bye goal org.codehaus.mojo:gwt-maven-plugin

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/36f3ef10-bc50-4f6a-a3e5-8b6186d48309n%40googlegroups.com.

Thursday, August 17, 2023

Updating our Google Account inactivity policy

Every day Google works hard to keep you and your private information safe and secure by preventing unauthorized access to your Google Account with our built-in security protections. And keeping you safe means having strong privacy practices across our products that minimize how long we store your personal files and any data associated with them. We want to protect your private information and prevent any unauthorized access to your account even if you're no longer using our services.

Therefore, we are updating the inactivity period for a Google Account to two years across all our products and services. This change starts rolling out today and will apply to any Google Account that's been inactive, meaning it has not been signed into or used within a two-year period. An inactive account and any content in it will be eligible for deletion from December 1, 2023.

What this means for you:

  • These changes do not impact you unless you have been inactive in your Google Account for two years or have not used your account to sign in to any Google service for over two years.
  • While the changes go into effect today, the earliest we would enforce any account deletion would be December 2023.
  • If your account is considered inactive, we will send several reminder emails to both you and your recovery emails (if any have been provided) before we take any action or delete any account content. These reminder emails will go out at least 8 months before any action is taken on your account.
  • After a Google Account is deleted, the Gmail address for the deleted account cannot be used again when creating a new Google Account.

How to keep your account active?

The simplest way to keep a Google Account active is to sign in to the account at least once every two years. If you have signed in to your Google Account recently in the past two years, your account is considered active and will not be deleted.

Other ways to keep your account active include:

  • Reading or sending an email
  • Using Google Drive
  • Watching a YouTube video
  • Sharing a photo
  • Downloading an app
  • Using Google Search
  • Using Sign in with Google to sign in to a third-party app or service

There are some exceptions to this policy. Examples include: a Google Account with YouTube channels, videos or comments; an account that has a gift card with a monetary balance; or an account that has a published application, for example, one that hosts an app on the Google Play store. Other exceptions to this policy are available here.

Google also offers tools to help manage your Google Account and provide options to back up your data, including the ability to download your data using Google Takeout, and allowing you to plan for what happens to your data if you're inactive for a specific period of time with the Inactive Account Manager.

Our priority is to make it as easy as possible for you to keep your account active, if you want to, and we'll ensure you have adequate notice before any account is impacted by this change. So before an account is deleted, Google will send email notifications to the Google Account and its recovery email (if one has been provided). You should verify that your recovery email is up to date.

Learn more

Thank you,
The Google Account team

You have received this email to update you about important changes to your Google Account and services.

© 2023 Google Ireland Ltd, Gordon House, Barrow Street, Dublin 4, Ireland.



Re: com.ait.toolkit.core.Core not found in Gwt-tour

I'm broadly aware that gwt-tour exists (though it hasnt had an update in 8 years), but I don't see any com.ait packages or references in it. On the other hand, I think com.ait.toolkit.core refers to https://github.com/dikalo/ahome-core/, which is a different thing entirely. It appears that ahome-core shadows a few GWT classes, which likely makes it incompatible with newer GWT versions - did you recently update GWT version and then start having this issue?

On Thursday, August 17, 2023 at 7:11:43 AM UTC-5 prasenji...@altizon.com wrote:
GWT Module com.ait.toolkit.core.Core not found in project sources or resources

in Gwt-Tour library HopScotch.gwt.xml has inherited com.ait.toolkit.core.Core which is not found bye goal org.codehaus.mojo:gwt-maven-plugin

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f0da1697-ff10-4351-8f0c-a5eb2cef163an%40googlegroups.com.

Re: gwt-tour not working

I'm getting following error GWT Module com.ait.toolkit.core.Core not found in project sources or resources


On Monday, April 6, 2015 at 7:31:48 PM UTC+5:30 marian lux wrote:
Thank you for further tests and that info. It helped me to test in other directions:
I did some tests and found a hint.
I assume you tested it with gwt 2.6.1?
When I compile the showcase with gwt 2.6.1 it works. With 2.7. I get the error as described above.

So it seems the gwt-tour lib is not compatible with (mgwt 2.0 in combination with) gwt 2.7?!



Am Sonntag, 5. April 2015 22:19:13 UTC+2 schrieb Alain:
Tested. 
I could not reproduced the issue. 
Looks like something is wrong with your  settings.

On 4 April 2015 at 23:06, marian lux <mlu...@gmail.com> wrote:
Hmm. 
With mgwt-showcase (https://github.com/mgwt/mgwt.showcase) it is not working for me as you can see above. Could please you try to check out the mgwt-showcase and test it if it is compileable by only adding the gwt-tour dependency in the pom.xml? Maybe there is a widget/panel which causes a problem (I get some errors in dependence  with the Appearance Pattern)? Sorry I am not into detail with this. But I think testing with the showcase makes sense because it displays most possible widgets in mgwt and so if it works there, it should work in every project/setup.
But if the showcase works on your machine, it must be an issue on my side (setup) and then I can dig deeper there and post a solution if I find one.
THX Marian


Am Samstag, 4. April 2015 21:41:53 UTC+2 schrieb Alain:
This code seems to work for me here

package com.ait.ti4j.playground.client;


import com.ait.toolkit.hopscotch.client.HopScotch;

import com.ait.toolkit.hopscotch.client.Placement;

import com.ait.toolkit.hopscotch.client.Tour;

import com.ait.toolkit.hopscotch.client.TourStep;

import com.google.gwt.core.client.EntryPoint;

import com.google.gwt.user.client.ui.RootPanel;

import com.googlecode.mgwt.ui.client.MGWT;

import com.googlecode.mgwt.ui.client.MGWTSettings;

import com.googlecode.mgwt.ui.client.animation.AnimationHelper;

import com.googlecode.mgwt.ui.client.widget.animation.Animations;

import com.googlecode.mgwt.ui.client.widget.button.Button;

import com.googlecode.mgwt.ui.client.widget.panel.flex.RootFlexPanel;


public class MgwtTest implements EntryPoint {


    @Override

    public void onModuleLoad() {


        // set viewport and other settings for mobile

        MGWT.applySettings( MGWTSettings.getAppSetting() );


        // build animation helper and attach it

        AnimationHelper animationHelper = new AnimationHelper();

        RootPanel.get().add( animationHelper );


        // build some UI

        RootFlexPanel rootFlexPanel = new RootFlexPanel();

        Button button = new Button( "Hello mgwt" );

        rootFlexPanel.add( button );


        // animate

        animationHelper.goTo( rootFlexPanel, Animations.SLIDE );


        Tour tour = new Tour( "myTour" );


        TourStep step = new TourStep( Placement.BOTTOM, button );

        step.setContent( "This is the Button" );

        step.setTitle( "Button" );

        tour.addStep( step );


        HopScotch.startTour( tour );


    }


}



On 4 April 2015 at 20:12, marian lux <mlu...@gmail.com> wrote:
I tested it with the current mgwt showcase (checked out from - https://github.com/mgwt/mgwt.showcase) by adding in pom.xml the dependency
                <dependency>
    <groupId>com.ahome-it</groupId>
<artifactId>gwt-tour</artifactId>
<version>2.0.0-SNAPSHOT</version>   
</dependency>
Before adding the dependency the showcase compiles and works.
After adding the dependency, I get also an error as on my mgwt project.
Runing CodeServer with parameters: [-noprecompile, -port, 9876, -sourceLevel, 1.7, -bindAddress, 127.0.0.1, -launcherDir, /home/marian/workspace_oha_mgwt2/mgwt-showcase/target/mgwt-showcase-2.0.0-SNAPSHOT, -logLevel, INFO, com.googlecode.mgwt.examples.showcase.ShowCase]
Super Dev Mode starting up
   workDir: /tmp/gwt-codeserver-883274298781880589.tmp
   Loading Java files in com.googlecode.mgwt.examples.showcase.ShowCase.
   Module setup completed in 17954 ms

The code server is ready at http://127.0.0.1:9876/
Code server started in 18040 ms
waited 12176 ms for code server to finish
GET /recompile/showcase
   Job com.googlecode.mgwt.examples.showcase.ShowCase_1_0
      starting job: com.googlecode.mgwt.examples.showcase.ShowCase_1_0
      binding: mgwt.density=mid
      binding: mgwt.formfactor=desktop
      Compiling module com.googlecode.mgwt.examples.showcase.ShowCase
         [ERROR] An internal compiler exception occurred
com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during visit.
at com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:121)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:296)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128)
at com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:67)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128)
at com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:49)
at com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:95)
at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:351)
at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:149)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:145)
at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:600)
at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:569)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1505)
at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:870)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1305)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1038)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.precompile(JavaToJavaScriptCompiler.java:954)
at com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptCompiler.precompile(MonolithicJavaToJavaScriptCompiler.java:303)
at com.google.gwt.dev.jjs.JavaScriptCompiler.precompile(JavaScriptCompiler.java:38)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:286)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:229)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:145)
at com.google.gwt.dev.Compiler.run(Compiler.java:206)
at com.google.gwt.dev.codeserver.Recompiler.doCompile(Recompiler.java:333)
at com.google.gwt.dev.codeserver.Recompiler.compile(Recompiler.java:161)
at com.google.gwt.dev.codeserver.Recompiler.recompile(Recompiler.java:119)
at com.google.gwt.dev.codeserver.Outbox.recompile(Outbox.java:128)
at com.google.gwt.dev.codeserver.JobRunner.recompile(JobRunner.java:81)
at com.google.gwt.dev.codeserver.JobRunner.access$100(JobRunner.java:34)
at com.google.gwt.dev.codeserver.JobRunner$2.run(JobRunner.java:73)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodError: com.google.gwt.uibinder.rebind.UiBinderWriter.<init>(Lcom/google/gwt/core/ext/typeinfo/JClassType;Ljava/lang/String;Ljava/lang/String;Lcom/google/gwt/core/ext/typeinfo/TypeOracle;Lcom/google/gwt/uibinder/rebind/MortalLogger;Lcom/google/gwt/uibinder/rebind/FieldManager;Lcom/google/gwt/uibinder/rebind/messages/MessagesWriter;Lcom/google/gwt/uibinder/rebind/DesignTimeUtils;Lcom/google/gwt/uibinder/rebind/UiBinderContext;ZZLjava/lang/String;)V
at com.google.gwt.uibinder.rebind.UiBinderGenerator.generateOnce(UiBinderGenerator.java:172)
at com.google.gwt.uibinder.rebind.UiBinderGenerator.generate(UiBinderGenerator.java:130)
at com.google.gwt.core.ext.IncrementalGenerator.generateNonIncrementally(IncrementalGenerator.java:40)
at com.google.gwt.dev.javac.StandardGeneratorContext.runGeneratorIncrementally(StandardGeneratorContext.java:760)
at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java:160)
at com.google.gwt.dev.shell.StandardRebindOracle$Rebinder.rebind(StandardRebindOracle.java:79)
at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:276)
at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:265)
at com.google.gwt.dev.DistillerRebindPermutationOracle.getAllPossibleRebindAnswers(DistillerRebindPermutationOracle.java:87)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createStaticRebindExpression(UnifyAst.java:485)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createRebindExpression(UnifyAst.java:443)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.handleMagicMethodCall(UnifyAst.java:576)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.endVisit(UnifyAst.java:306)
at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:248)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
... 47 more
            [ERROR] at FlexPanelDefaultAppearance.java(39): GWT.create(FlexPanelDefaultAppearance$Binder.class)
               com.google.gwt.dev.jjs.ast.JMethodCall
            [ERROR] at FlexPanelDefaultAppearance.java(39): (FlexPanelDefaultAppearance$Binder) GWT.create(FlexPanelDefaultAppearance$Binder.class)
               com.google.gwt.dev.jjs.ast.JCastOperation
            [ERROR] at FlexPanelDefaultAppearance.java(39): final static FlexPanelDefaultAppearance$Binder UI_BINDER = (FlexPanelDefaultAppearance$Binder) GWT.create(FlexPanelDefaultAppearance$Binder.class)
               com.google.gwt.dev.jjs.ast.JDeclarationStatement
            [ERROR] at FlexPanelDefaultAppearance.java(22): {
  Object.$clinit();
  {
    FlexPanelDefaultAppearance$Resources.INSTANCE.css().ensureInjected();
  }
  final static FlexPanelDefaultAppearance$Binder UI_BINDER = (FlexPanelDefaultAppearance$Binder) GWT.create(FlexPanelDefaultAppearance$Binder.class);
}
               com.google.gwt.dev.jjs.ast.JBlock
            [ERROR] at FlexPanelDefaultAppearance.java(22): {
  Object.$clinit();
  {
    FlexPanelDefaultAppearance$Resources.INSTANCE.css().ensureInjected();
  }
  final static FlexPanelDefaultAppearance$Binder UI_BINDER = (FlexPanelDefaultAppearance$Binder) GWT.create(FlexPanelDefaultAppearance$Binder.class);
}
               com.google.gwt.dev.jjs.ast.JMethodBody
            [ERROR] at FlexPanelDefaultAppearance.java(22): private static final void $clinit();

               com.google.gwt.dev.jjs.ast.JMethod
      [ERROR] Compiler returned false
      [WARN] recompile failed
      [WARN] continuing to serve previous version


It seems there is a problem with mgwt or something else (dependencies). The pom.xml from mgwt showcase with the dependency of gwt-tour is also in attachment.


Am Samstag, 4. April 2015 12:27:29 UTC+2 schrieb Alain:

Having a look. Should work with mgwt.

On 4 Apr 2015 12:20, "marian lux" <mlu...@gmail.com> wrote:
Thank you! But a compilation problem still remains.

I figured out the following:
When I only add in my pom.xml
                <dependency>
    <groupId>com.ahome-it</groupId>
<artifactId>gwt-tour</artifactId>
<version>2.0.0-SNAPSHOT</version>   
</dependency>
and try to compile the project with the news resources from the dependency,
I get the following console output (error) in super dev mode (without the dependency the project works - It is a mgwt project and there seems to be a conflict with PullPanel)
The code server is ready at http://127.0.0.1:9876/
Code server started in 11272 ms
waited 659 ms for code server to finish
2015-04-04 12:13:42 INFO  ManageThreadTwitter:37 - ThreadTwitter started
2015-04-04 12:13:42 INFO  ManageThreadTwitter:37 - ThreadTwitter started
2015-04-04 12:13:42 INFO  ManageThreadTwitter:126 - updated TwitterFeedData for DailyPost
2015-04-04 12:13:44 INFO  ManageThreadTwitter:136 - updated TwitterFeedData for RegionalNews
GET /recompile-requester/oha
   [WARN] Deactivated PrecompressLinker
GET /recompile/oha
   Job at.mlux.oha_1_0
      starting job: at.mlux.oha_1_0
      binding: locale=de
      binding: mgwt.density=mid
      binding: mgwt.formfactor=desktop
      binding: user.agent=safari
      Compiling module at.mlux.oha
         [ERROR] An internal compiler exception occurred
com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during visit.
at com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:121)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:296)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128)
at com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:67)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128)
at com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:49)
at com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:95)
at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:351)
at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:149)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:145)
at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:600)
at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:569)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1505)
at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:870)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1305)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1038)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.precompile(JavaToJavaScriptCompiler.java:954)
at com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptCompiler.precompile(MonolithicJavaToJavaScriptCompiler.java:303)
at com.google.gwt.dev.jjs.JavaScriptCompiler.precompile(JavaScriptCompiler.java:38)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:286)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:229)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:145)
at com.google.gwt.dev.Compiler.run(Compiler.java:206)
at com.google.gwt.dev.codeserver.Recompiler.doCompile(Recompiler.java:333)
at com.google.gwt.dev.codeserver.Recompiler.compile(Recompiler.java:161)
at com.google.gwt.dev.codeserver.Recompiler.recompile(Recompiler.java:119)
at com.google.gwt.dev.codeserver.Outbox.recompile(Outbox.java:128)
at com.google.gwt.dev.codeserver.JobRunner.recompile(JobRunner.java:81)
at com.google.gwt.dev.codeserver.JobRunner.access$100(JobRunner.java:34)
at com.google.gwt.dev.codeserver.JobRunner$2.run(JobRunner.java:73)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodError: com.google.gwt.uibinder.rebind.UiBinderWriter.<init>(Lcom/google/gwt/core/ext/typeinfo/JClassType;Ljava/lang/String;Ljava/lang/String;Lcom/google/gwt/core/ext/typeinfo/TypeOracle;Lcom/google/gwt/uibinder/rebind/MortalLogger;Lcom/google/gwt/uibinder/rebind/FieldManager;Lcom/google/gwt/uibinder/rebind/messages/MessagesWriter;Lcom/google/gwt/uibinder/rebind/DesignTimeUtils;Lcom/google/gwt/uibinder/rebind/UiBinderContext;ZZLjava/lang/String;)V
at com.google.gwt.uibinder.rebind.UiBinderGenerator.generateOnce(UiBinderGenerator.java:172)
at com.google.gwt.uibinder.rebind.UiBinderGenerator.generate(UiBinderGenerator.java:130)
at com.google.gwt.core.ext.IncrementalGenerator.generateNonIncrementally(IncrementalGenerator.java:40)
at com.google.gwt.dev.javac.StandardGeneratorContext.runGeneratorIncrementally(StandardGeneratorContext.java:760)
at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java:160)
at com.google.gwt.dev.shell.StandardRebindOracle$Rebinder.rebind(StandardRebindOracle.java:79)
at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:276)
at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:265)
at com.google.gwt.dev.DistillerRebindPermutationOracle.getAllPossibleRebindAnswers(DistillerRebindPermutationOracle.java:87)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createStaticRebindExpression(UnifyAst.java:485)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createRebindExpression(UnifyAst.java:443)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.handleMagicMethodCall(UnifyAst.java:576)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.endVisit(UnifyAst.java:306)
at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:248)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
... 47 more
            [ERROR] at PullPanelAbstractAppearance.java(29): GWT.create(PullPanelAbstractAppearance$Binder.class)
             
...

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f5a44d4c-ea40-4440-913a-350ca8ff14a9n%40googlegroups.com.

com.ait.toolkit.core.Core not found in Gwt-tour

GWT Module com.ait.toolkit.core.Core not found in project sources or resources

in Gwt-Tour library HopScotch.gwt.xml has inherited com.ait.toolkit.core.Core which is not found bye goal org.codehaus.mojo:gwt-maven-plugin

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/40f89a8c-1449-47e7-ad11-3d6749b1a73bn%40googlegroups.com.

Monday, August 14, 2023

Re: [GWT] [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core'

Thanks Colin! Indeed the Ant classpath was using the old GWT 2.8.1... My bad, sorry.

Tiberiu

On Mon, Aug 14, 2023 at 4:33 PM Colin Alworth <colin@colinalworth.com> wrote:
Tiberiu, the fact that it works in Eclipse strongly suggests to me that the ant classpath is different from the eclipse project classpath. That different configuration will lead to different results. This error is typically indicative of some other error happening (typically classpath related) - double check that, and add the "-strict" argument to the Compiler invocation to make sure you see any earlier errors as well (if any).

On Tuesday, August 8, 2023 at 4:48:56 PM UTC-5 tiberiu...@gmail.com wrote:
Hello everyone,

I just upgraded to GWT 2.10.0 from 2.8.1 and I receive the same error when compiling through an Ant build.

The code and scripts are identical and is compiling just fine with Java 1.8, GWT 2.8.1 and Eclipse 4.17. However with Java 13 or 17, GWT 2.10.0 and Eclipse 4.28 gives the error. Although in the second configuration it compiles successfully through the Eclipse GWT plugin it does not compile using the Ant build. But the GWT module is the same...

What am I missing?

Thanks you,
Tiberiu

On Friday, October 7, 2022 at 4:14:31 PM UTC+3 Thomas Broyer wrote:
See https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
GWT *runs* on JDKs from 8 to 17; you can however only compile Java 11 –at most– source files (depending on -sourceLevel).

When facing that kind of error, make sure you run with -failOnError (or its older name: -strict), and possibly use a more verbose -logLevel.


On Friday, October 7, 2022 at 2:51:17 PM UTC+2 ngf.ch...@gmail.com wrote:
Hello here.
I would like to react for this threat. Would at this time (2022) gwt supports java 12?
For I am experiencing the error mentioned above.
Thanks in advance.


On Monday, May 20, 2019 at 12:59:25 AM UTC ma...@craig-mitchell.com wrote:
I don't believe GWT supports Java 12 yet.  I'd recommend just using Java 8.

And you might want to use the latest GWT version (2.8.2).

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f80c2b1a-4d88-4b5c-9bb2-46ed557d0565n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CALMvfNA5MR0L%3DLDxbaO%2BAhYpkfrQMozvbvDiH22TRZP0cf_-Bw%40mail.gmail.com.

Re: [GWT] [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core'

Tiberiu, the fact that it works in Eclipse strongly suggests to me that the ant classpath is different from the eclipse project classpath. That different configuration will lead to different results. This error is typically indicative of some other error happening (typically classpath related) - double check that, and add the "-strict" argument to the Compiler invocation to make sure you see any earlier errors as well (if any).

On Tuesday, August 8, 2023 at 4:48:56 PM UTC-5 tiberiu...@gmail.com wrote:
Hello everyone,

I just upgraded to GWT 2.10.0 from 2.8.1 and I receive the same error when compiling through an Ant build.

The code and scripts are identical and is compiling just fine with Java 1.8, GWT 2.8.1 and Eclipse 4.17. However with Java 13 or 17, GWT 2.10.0 and Eclipse 4.28 gives the error. Although in the second configuration it compiles successfully through the Eclipse GWT plugin it does not compile using the Ant build. But the GWT module is the same...

What am I missing?

Thanks you,
Tiberiu

On Friday, October 7, 2022 at 4:14:31 PM UTC+3 Thomas Broyer wrote:
See https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
GWT *runs* on JDKs from 8 to 17; you can however only compile Java 11 –at most– source files (depending on -sourceLevel).

When facing that kind of error, make sure you run with -failOnError (or its older name: -strict), and possibly use a more verbose -logLevel.


On Friday, October 7, 2022 at 2:51:17 PM UTC+2 ngf.ch...@gmail.com wrote:
Hello here.
I would like to react for this threat. Would at this time (2022) gwt supports java 12?
For I am experiencing the error mentioned above.
Thanks in advance.


On Monday, May 20, 2019 at 12:59:25 AM UTC ma...@craig-mitchell.com wrote:
I don't believe GWT supports Java 12 yet.  I'd recommend just using Java 8.

And you might want to use the latest GWT version (2.8.2).

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f80c2b1a-4d88-4b5c-9bb2-46ed557d0565n%40googlegroups.com.

Friday, August 11, 2023

GWT-Liberty Issue

Hi Team,

I have upgraded the Open liberty server version (v 23.0.0_601)  for my application.  However when we have deployed with the following combination of JDK : "version: 8.0.372_01" and OPEN LIBERTY: "version: 23.0.0_0601" we encountered the following error : 

Uncaught TypeError: Cannot read properties of null (reading 'L') at YKc (cockpit-0.js:5701:31) at ZKc.$Kc [as Mg] (cockpit-0.js:10459:24086) at qVb.sVb [as Te] (cockpit-0.js:10455:10065) at Pw (cockpit-0.js:6863:79) at ax.bx [as Re] (cockpit-0.js:10454:7250) at XMLHttpRequest.eval (cockpit-0.js:6343:65) at Uj (cockpit-0.js:4445:29) at Xj (cockpit-0.js:6053:44) at XMLHttpRequest.eval (cockpit-0.js:6369:46) YKc @ cockpit-0.js:5701 $Kc @ c

I have tried below combination of jdk and open liberty, both conbinations are not working.
JDK version = 8.0.372_01 
Liberty Version = 23.0.0_0601 

JDK version = 11.0.19_701 
Liberty Version = 23.0.0_0601  

FYI the application is developed with GWT 2.10 version .  

Regards,
Ujwal Chaudhari

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/9a425120-9270-495e-9547-d10c13d6d2een%40googlegroups.com.

Tuesday, August 8, 2023

Re: [GWT] [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core'

Hello everyone,

I just upgraded to GWT 2.10.0 from 2.8.1 and I receive the same error when compiling through an Ant build.

The code and scripts are identical and is compiling just fine with Java 1.8, GWT 2.8.1 and Eclipse 4.17. However with Java 13 or 17, GWT 2.10.0 and Eclipse 4.28 gives the error. Although in the second configuration it compiles successfully through the Eclipse GWT plugin it does not compile using the Ant build. But the GWT module is the same...

What am I missing?

Thanks you,
Tiberiu

On Friday, October 7, 2022 at 4:14:31 PM UTC+3 Thomas Broyer wrote:
See https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
GWT *runs* on JDKs from 8 to 17; you can however only compile Java 11 –at most– source files (depending on -sourceLevel).

When facing that kind of error, make sure you run with -failOnError (or its older name: -strict), and possibly use a more verbose -logLevel.


On Friday, October 7, 2022 at 2:51:17 PM UTC+2 ngf.ch...@gmail.com wrote:
Hello here.
I would like to react for this threat. Would at this time (2022) gwt supports java 12?
For I am experiencing the error mentioned above.
Thanks in advance.


On Monday, May 20, 2019 at 12:59:25 AM UTC ma...@craig-mitchell.com wrote:
I don't believe GWT supports Java 12 yet.  I'd recommend just using Java 8.

And you might want to use the latest GWT version (2.8.2).

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f84a53cf-55b5-47ca-8b81-adc25ab384b3n%40googlegroups.com.