2 Replies Latest reply on Feb 6, 2014 9:21 PM by Graeme Collis

    UberFire Tutorial

    Graeme Collis Newbie

      I have a couple of issues with the UberFire tutorial. Evenutally I can get it working but I don't understand why?

       

      If you clone the git repository "https://github.com/uberfire/uberfire-tutorial.git" and

      1. Modify the pom.xml element "errai.jboss.home" to point to my JBoss EAP 6.2 root folder

      2. mvn clean install gwt:run

       

      Then maven compiles all clean, creates the war, starts the gwt dev environment(which starts JBoss standalone and copies in the war).

      It all then settles after the GWT generate/compiles and gives me a launch URL.

      When I launch the URL the UberFire tutorial login screen starts (Yahoo!)

      When I log in as admin then the next screen(the perspectives) gets a web error.

       

      GWT Development Mode URL

      http://127.0.0.1:8888/uberfire-tutorial?gwt.codesvr=127.0.0.1:9997

       

      ERROR

      JBWEB000065: HTTP Status 404 - /uberfire-tutorial/

       

      If I use the following workaround URL then the Perspectives appear and I can play with the mood screen, perspectives, drag and drop etc.

       

      Workaround URL

      http://127.0.0.1:8888/uberfire-tutorial/UberFireTutorial/UberFire.html?gwt.codesvr=127.0.0.1:9997

       

      What is the correct URL to use?

       

      Other small issues:-

      . images don't display for the login screen or the loading icon.

      . The tutorial needs a logout as the jsessionid gets cached so you cannot get back to the login screen and you see only the perspectives on the next and subsequent runs.

        • 1. Re: UberFire Tutorial
          Jonathan Fuerth Master

          Hi Graeme,

          I have a couple of issues with the UberFire tutorial. Evenutally I can get it working but I don't understand why?

           

          The main reason is that the tutorial isn't done yet. We've got the new www.uberfireframework.org website staged, but we haven't actually published any links to it yet. I'll add a note to the tutorial so people know it isn't 100% working yet. Sorry about misleading you.

           

          If you clone the git repository "https://github.com/uberfire/uberfire-tutorial.git" and

          1. Modify the pom.xml element "errai.jboss.home" to point to my JBoss EAP 6.2 root folder

          2. mvn clean install gwt:run

           

          Then maven compiles all clean, creates the war, starts the gwt dev environment(which starts JBoss standalone and copies in the war).

          It all then settles after the GWT generate/compiles and gives me a launch URL.

          When I launch the URL the UberFire tutorial login screen starts (Yahoo!)

          When I log in as admin then the next screen(the perspectives) gets a web error.

           

          GWT Development Mode URL

          http://127.0.0.1:8888/uberfire-tutorial?gwt.codesvr=127.0.0.1:9997

           

          ERROR

          JBWEB000065: HTTP Status 404 - /uberfire-tutorial/

           

          If I use the following workaround URL then the Perspectives appear and I can play with the mood screen, perspectives, drag and drop etc.

           

          Workaround URL

          http://127.0.0.1:8888/uberfire-tutorial/UberFireTutorial/UberFire.html?gwt.codesvr=127.0.0.1:9997

           

          What is the correct URL to use?

           

          This is a bug in UberFire's current FormAuthenticationProvider: it only ever worked on Jetty. I've just managed to fix this, and I've pushed the fix up to github. The snapshots should update eventually, but in the mean time, it's quite easy to rebuild uberfire locally:

           

          % git clone https://github.com/uberfire/uberfire.git

          % cd uberfire

          % mvn install

           

          Also, pull down a new copy of the tutorial and update to the new checkpoint-5 tag: I've added a parameter to the web.xml that specifies the location of the host page.

           

          Other small issues:-

          . images don't display for the login screen or the loading icon.

          . The tutorial needs a logout as the jsessionid gets cached so you cannot get back to the login screen and you see only the perspectives on the next and subsequent runs.

           

          Thanks for this feedback; those things are on the to-do list!

           

          Happy coding,

          Jonathan

           

          PS: something else that isn't set up yet is the UberFire community forum. Out of curiosity, how did your question find its way to this Errai forum?  Is there a link somewhere that we should know about? If so, we'll ask for it to be updated once the UberFire forum is in place.

          • 2. Re: UberFire Tutorial
            Graeme Collis Newbie

            Hi Jonathan,

             

            there is no link to Errai. As you point out there also is no community forum for UberFire. So I just went to where I thought the UberFire developers may be lurking!

             

            I will pull the source changes and give it a go. I'm working from the source via a git clone and maven in both Errai and UberFire so I will get the changes you have mentioned and give it a try.

             

            The Errai/UberFire mix is the sort of application architecture I am looking for. Errai by itself gives most things. UberFire adds ways to handle extra framework type thinks like security and and in my case *panel* management(Perspectives). So together, Errai/UberFire, seem to cover a lot of my requirements. (Our application is more like a Desktop app than a traditional WebApp).

             

            The style and layout of the UberFire tutorial I think is very instructive and it got me to a point of being able to use things pretty quickly. I knew from some of the "todo" notes in the tutorial that it wasn't quite finished. Thanks for your efforts for that and to the team(Errai and UberFire) in general, for in my opinion, this is the closest to a desktop replacement framework in a Web app I have seen.

             

            thanks,

             

            Graeme