Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    SmartGWT-EE 1.2.1 vs. GWT 2.0

    When I try to run the SmartGWT EE showcase with GWT 2.0 (from Eclipse), the server side does not start properly:

    ------------------------------------------------------

    === 2009-12-15 17:54:06,563 [main] INFO PreCache - Isomorphic PreCache complete (507ms)
    [WARN] Configuration problem at <mime-mapping>
    <extension>csv</extension>
    <mime-type>text/csv</mime-type>
    </mime-mapping>
    java.lang.NullPointerException
    at org.mortbay.jetty.webapp.WebXmlConfiguration.initMimeConfig(WebXmlConfiguration.java:680)
    at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:340)
    at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289)
    at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222)
    at com.google.gwt.dev.ServletValidator.create(ServletValidator.java:69)
    at com.google.gwt.dev.ServletValidator.create(ServletValidator.java:52)
    at com.google.gwt.dev.DevMode.doSlowStartup(DevMode.java:332)
    at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:953)
    at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:690)
    at com.google.gwt.dev.DevMode.main(DevMode.java:251)
    [WARN] Unable to process 'file:/mnt/user_data/home/csillag/EclipseWorkspace.nolme/ShowcaseEE/war/WEB-INF/web.xml' for servlet validation
    javax.servlet.UnavailableException: Configuration problem
    at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:298)
    at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222)
    at com.google.gwt.dev.ServletValidator.create(ServletValidator.java:69)
    at com.google.gwt.dev.ServletValidator.create(ServletValidator.java:52)
    at com.google.gwt.dev.DevMode.doSlowStartup(DevMode.java:332)
    at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:953)
    at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:690)
    at com.google.gwt.dev.DevMode.main(DevMode.java:251)

    ------------------------------------------------------

    This is new; it used to work with GWT 1.7.1.
    It looks like the configuration of the embedded Jetty server has changed in GWT 2.0.

    Is this going to be fixed in SmartGWT-EE?

    #2
    My own SmartGWT-EE test project also crashes with GWT-2.0:

    -----------------------------------------------------------------

    === 2009-12-15 17:57:09,846 [l0-2] DEBUG PoolableSQLConnectionFactory - Initializing SQL config for 'Szolorg' via JNDI
    === 2009-12-15 17:57:09,847 [l0-2] DEBUG JNDI - No configuration for JNDI context - assuming default initialContext
    === 2009-12-15 17:57:09,849 [l0-2] ERROR SQLConnectionManager - Caught exception
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at com.isomorphic.sql.PoolableSQLConnectionFactory.makeUnpooledObject(PoolableSQLConnectionFactory.java:229)
    at com.isomorphic.sql.PoolableSQLConnectionFactory.makeObject(PoolableSQLConnectionFactory.java:297)
    at com.isomorphic.pool.PoolManager.borrowObject(PoolManager.java:74)
    at com.isomorphic.sql.SQLConnectionManager.getConnection(SQLConnectionManager.java:148)
    at com.isomorphic.sql.SQLDriver.implementerClassForDB(SQLDriver.java:198)
    at com.isomorphic.sql.SQLDriver.instance(SQLDriver.java:160)
    at com.isomorphic.sql.SQLDataSource.init(SQLDataSource.java:124)
    at com.isomorphic.datasource.BasicDataSource.fromConfig(BasicDataSource.java:126)
    at com.isomorphic.datasource.DataSource.fromConfig(DataSource.java:224)
    at com.isomorphic.datasource.DataSource.forName(DataSource.java:198)
    at com.isomorphic.datasource.PoolableDataSourceFactory.makeUnpooledObject(PoolableDataSourceFactory.java:89)
    at com.isomorphic.datasource.PoolableDataSourceFactory.makeObject(PoolableDataSourceFactory.java:96)
    at com.isomorphic.pool.PoolManager.borrowObject(PoolManager.java:76)
    at com.isomorphic.datasource.DataSourceManager.getDataSource(DataSourceManager.java:56)
    at com.isomorphic.servlet.DataSourceLoader.processRequest(DataSourceLoader.java:80)
    at com.isomorphic.servlet.DataSourceLoader.doGet(DataSourceLoader.java:64)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at com.isomorphic.servlet.BaseServlet.service(BaseServlet.java:152)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:829)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)

    -----------------------------------------------------------------

    It looks like the JNDI configuration has changed, too.

    Comment


      #3
      availability of SmartGWT-EE (and SmartGWT-Pro ans SmartGWT-Power) 2.0

      It has been posted that the new commercial SmartGWT-EE 2.0 builds will be uploaded soon.

      I would like a raw estimate: how soon? (Hours, days, weeks?)

      I do not mean to press you, I would just like to factor this in into my own schedule.

      Comment


        #4
        blocked by errors on all sides

        Right now, it seems that this developer (and anyone else who was inconsiderate enough to install the new version if the google eclipse plugin without saving the eclipse directory first) is stuck with GWT 2.0. (The old version of the plugin can no longer be installed, and the new version of the plugin does not seem to be able to run applications with gwt 1.7.1 any more.)

        Therefore, I can not revert to GWT 1.7.1.

        On the other part, SmartGWT-EE and SmartGWT-Pro does not seem to work with GWT 2.0 (See the errors above.)

        Currently, I do not see any way out of this.

        Do you have any advice?

        Comment


          #5
          Wait for S'GWT PRO/EE 2.0. Everything else is waste of time, resources and nerves.

          Ekki

          * GWT Rocks! * SmartGWT Rocks Even Harder! * SmartGWT PRO 1.2/LGPL 1.3,
          GWT 1.7.1, GAE 1.2.6, Jetty 7.0.0, Eclipse 3.5.1, JRE 1.6.0_16

          CI-CUBE.BIZ feat. CubeBrowser.AppSpot.com www.EasternGraphics.com/X-4GPL

          Comment


            #6
            Originally posted by CI-CUBE
            Wait for S'GWT PRO/EE 2.0. Everything else is waste of time, resources and nerves.
            I have two problems with this:

            1. I do not have any idea about the estimated arrival of SmartGWT-Pro 2.0. "Soon" can mean anything.

            2. Right now, my project can not really afford waiting. I have deadlines to keep.

            Comment


              #7
              switch back to GWT 1.7.1. The good news about Eclipse is that multiple Eclipses can run in parallel. Setup a new Eclipse import GWT 1.7.1 and continue with your project.

              Switch to GWT 2.0 after S'GWT PRO/EE 2.0 is out or even later on.

              Comment


                #8
                Originally posted by CI-CUBE
                switch back to GWT 1.7.1.
                The problem is, this does not seem to work.

                Even if I completely remove GWT 2.0 from eclipse, the new version of the Google Eclipse Plugin tries to run the project partly the new way (dev mode), instead of the old way (hosted mode).

                To properly revert, I should also revert the Google Eclipse Plugin, but this is not supported. (Only the latest version is available at Google's Eclipse install site.)

                Comment


                  #9
                  thats bad news. What about trying to download and install an explicit GWT 1.7.1 SDK - ignoring the official google link that obviously points to 2.0?

                  Comment


                    #10
                    Originally posted by CI-CUBE
                    thats bad news. What about trying to download and install an explicit GWT 1.7.1 SDK - ignoring the official google link that obviously points to 2.0?
                    There are two different components provided by google:

                    1. The GWT SDK.
                    2. The Eclipse Goolge Plugin

                    The GWT SDK is OK: I can download and install it manually, whatever version I want (even multiple versions in parallel), and just point Eclipse to use it. For each project, I can select which version to use.

                    However, the Eclipse Plugin is problematic: this can only be installed from within Eclipse, with the eclipse plugin installer. Currently, only the latest version is available, and it does not seem to support older GWT versions.

                    This effectively makes the google-enhanced eclipse unusable for SmartGWT-EE (and Pro and Power) development, until they start supporting GWT 2.0.

                    Comment


                      #11
                      Too bad, and good to know (avoiding to run into the same issue). So they support 3 Eclipse versions, but not 2 of their own stuff. That's hard. So one side (google) forces you to switch to 2.0 if you want or not, the other side (Isomorphic) doesn't let you go this way right now (just a fact, no criticism at all). Crazy times, aren't they?! Sorry for not having another hint for you at this moment :-(

                      Comment


                        #12
                        maybe I'm stupid... but what about if I dump my Eclipse 3.5 feat. GWT 1.7.1 and corresponding google Eclipse plugin into a ZIP and provide that to you? Would that be helpful to you?

                        If anyone out there has an idea how to address (and install) google eclipse plugin for GWT 1.7.1 please let us know anyway...

                        Ekki

                        * GWT Rocks! * SmartGWT Rocks Even Harder! * SmartGWT PRO 1.2/LGPL 1.3,
                        GWT 1.7.1, GAE 1.2.6, Jetty 7.0.0, Eclipse 3.5.1, JRE 1.6.0_16

                        CI-CUBE.BIZ feat. CubeBrowser.AppSpot.com www.EasternGraphics.com/X-4GPL

                        Comment


                          #13
                          Originally posted by CI-CUBE
                          Too bad, and good to know (avoiding to run into the same issue). So they support 3 Eclipse versions, but not 2 of their own stuff. That's hard. So one side (google) forces you to switch to 2.0 if you want or not, the other side (Isomorphic) doesn't let you go this way right now (just a fact, no criticism at all).
                          Yes, this is exactly the way it seems to be right now.

                          Originally posted by CI-CUBE
                          Crazy times, aren't they?! Sorry for not having another hint for you at this moment :-(
                          The only way out would have been to refrain for refreshing anything (hard to do for the kid inside me), or at least take a full backup of my eclipse directory before doing so.
                          (The problem is that I still tend to trust the technology I use. Strangely, I do not seem to be able to learn not to...)

                          * * *

                          Let's just hope that SmartGWT-Pro 2.0 is out really-really soon (like, 12 hours), so I can go on with development.

                          Comment


                            #14
                            my Eclipse 3.5.1 is uncompressed 500 MB, no workspaces included, no idea how big after compression. If you are going into trouble, give me a hint and I will provide a link where you can download it. This could be done tomorrow morning.

                            Ekki

                            Comment


                              #15
                              Originally posted by CI-CUBE
                              maybe I'm stupid... but what about if I dump my Eclipse 3.5 feat. GWT 1.7.1 and corresponding google Eclipse plugin into a ZIP and provide that to you? Would that be helpful to you?
                              I plan to look for developer machines with the required configuration in my vicinity first, but if this fails, I might accept your offer, thank you... (However, this only works if you are also using the 64-bit linux version of Eclipse. If not, then I can't use yours.)

                              Comment

                              Working...
                              X