Announcement

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

    VisualBuilder on deployed application issue

    Hi,

    I'm trying to edit some screens at runtime using visualBuilder, this is working fine when using hosted mode however when I open visualBuilder on the deployed application, the only options available are "New Screen" and "Import from Balsamiq".
    I'm guessing this has to do with some sort of permissions problem, but I don't see any error in the smartGWT logs.


    Log (visual builder starting): http://pastebin.com/NWWJj9QK


    Appreciate any help or tip you can provide me.

    Thanks.

    Information:
    SmartGWT Version: v4.0p_2014_01_19/EVAL
    SmartClient Version: v9.0p_2014-01-19/EVAL Deployment (expires 2014.03.20_08.15.16) Licensed to: Isomorphic Software (#ISC_EVAL_NIGHTLY)

    Browsers: Any

    #2
    What was it that you were expecting to see, screens and DataSources from the app?

    Are they in the expected locations in the deployment (war/shared/ds for DataSources for example)?

    Comment


      #3
      Hi, thanks for the quick reply. Yes I was expecting to be able to see and edit the screens from the app. As stated in my previous post, I can already see and edit the screens when I run the app in hosted mode.

      They are in the expected locations, actually the application works with the screens I created, but the options to open existing screens or save are disabled in visual builder when opened from tomcat (using versions 5 and 6).

      Attached screenshot showing the problem.


      Thanks
      Attached Files

      Comment


        #4
        This looks like FilesystemDataSource is not enabled - you need:

        Code:
        FilesystemDataSource.enabled: true
        .. in server.properties. It's not clear how hosted mode could differ from deployed mode, but this setting being missing would produce exactly what you're seeing.

        Note this is not required for 4.1, you should plan to update.

        Comment


          #5
          Adding that property to server.properties fixed the problem.

          Thanks.

          Comment

          Working...
          X