Announcement

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

    Skin 404 in Visual Builder DataSource Editor

    Let's start with the version I am using is SmartGWTPower 3.0 nightly:
    SmartClient Version: SC_SNAPSHOT-2011-12-01/PowerEdition Deployment (built 2011-12-01)

    So I am using the BlackOps theme, successfully I might add in my application.

    I open up Visual Builder and it is skinned with BlackOps as well.

    I want to use it to create and edit some ds.xml files, and thats where everything goes wrong.

    I get 404 errors all over the place as it is looking for images in skins/standard/...
    The only directories in my war under skins are BlackOps/ and ToolSkin/

    The DataSource editor tool is rendered fairly useless at this point as the listgrid for fields is completely broken by 404s.

    ***EDIT****
    I also tried with the official 3.0 release to find the same problem
    Last edited by jpappalardo; 8 Dec 2011, 14:37.

    #2
    We're not seeing this with 3.0. It may be that you've copied configuration files from one project to another without adjusting them properly, for instance, server.properties needs to know the GWT module name because of how the GWT compiler copies resources into the war / webroot directory.

    If that doesn't help you figure it out, you could use any sample project within 3.0 to run Visual Builder instead of trying to do it within whatever project you have that has this problem.

    Finally, you may not want to use Visual Builder to edit DataSources at all - see the QuickStart Guide, Server Framework chapter, intro materials right at the beginning about generating DataSources from various sources of metadata - this is the way to spend the least effort.

    Comment


      #3
      From server.properties I have the following

      webRoot: __AUTODETECT__
      gwtModuleName: gsui
      isomorphicPathRootRelative: $gwtModuleName/sc

      At present the datasources I am trying to be able to edit take the following form



      As I was hoping to not have to code the datasource at all. I can see that it clearly resolves all the columns and the associated types. When I use them in a list grid I can see all of the columns, however I do not see any data retrieved from the table.

      Using a db admin console I can clearly see there are rows in the tables.

      ListGrid enums = new ListGrid();
      enums.setWidth("100%");
      enums.setHeight("*");
      enums.setDataSource(DataSource.get("enumType"));
      enums.setAutoFetchData(true);

      Which successfully results in a list grid with columns that match the datasource, but upon fetch no records are returned. So in the hopes of trying to narrow down the issues I figured I would use a DS generator. I have gotten the one in VisualBuilder to work for me with great success using version 2.5. However, in 3.0 it is unusable using this theme.

      Everytime I try to use the DataSource console things go just as badly if not worse. I end up with the following exception when I try to do anything with that tool.



      I would just like for one of the known methods for generating datasources to work for me. This all worked fine in version 2.5 well at least visual builder and auto derived schemas. The Datasource console gave me the same problems.

      I just had JPA transaction issues trying to actually manipulate the tables. Hence why I moved to 3.0 so I could get the new BMT transactions. Which resolved the transaction issues I had with the datasources I had successfully created in 2.5. But now I cant generate new datasources that function at all.
      Last edited by jpappalardo; 24 Sep 2014, 10:58.

      Comment


        #4
        Your tools installation is obviously completely messed up, it suggests you've got some files from one release and some files from another. If you want to fix that, go through the full installation procedure with 3.0, and be sure to run a GWT compile and clear your browser cache before retesting.

        However there's again, no reason at all to be reaching for these tools to try to fix this problem. Just try using the DataSource normally - issue a fetch against it - and if that's not working, then post complete information here, starting with the complete server-side log for the failing (this is always needed).

        Comment

        Working...
        X