unable to open saved screen in Visual Builder

[rpoyner]

I'm using the embedded server with SmartClient_SNAPSHOT_v101d_2015-06-02_Pro SDK. I've created a screen in visual builder and saved it. However when I try to reopen it in Visual Builder it appears to be empty. The tools/visualBuiler/workspace/screen.ui.xml file is there and the contents seem to match what I had built. The OS is CentOS 7 with java 1.8.0_45-b14.


Perhaps I should be using a different snapshot? I tried the nightly fro 9/13 but didn't get as far as with the 6/2 snapshot.
Thanks

[Isomorphic]

Definitely use the latest snapshot at any given time if you are going to be reporting a bug.

With bug reports, we need you to include the diagnostics listed in the FAQ at a minimum. With no log, no information about the screen, etc, this report basically says "something didn't work" and we can't do much with that :)

[rpoyner]

Getting the same behavior with SmartClient_v100p_2015-09-16_Pro. Tell visual builder to load the screen and then a blank screen appears. This is repeatable in chrome and Firefox running on Centos7

Console log from the server:

=== 2015-09-17 14:25:13,163 [80-2] INFO  RequestContext - URL: '/tools/visualBuilder/vbOperations.jsp', User-Agent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36': Safari with Accept-Encoding header
=== 2015-09-17 14:25:13,172 [80-2] DEBUG XML - Parsed XML from (in memory stream): 8ms
=== 2015-09-17 14:25:13,173 [80-2] DEBUG RPCManager - Processing 1 requests.
=== 2015-09-17 14:25:13,173 [80-2] DEBUG RPCManager - Request #1 (DSRequest) payload: {
    criteria:{
        path:"/tank0/SmartClient10/SmartClient_v100p_2015-09-16_Pro/smartclientSDK/tools/visualBuilder/workspace/gradAppl.ui.xml"
    },
    operationConfig:{
        dataSource:"Filesystem",
        repo:null,
        operationType:"fetch",
        textMatchStyle:"exact"
    },
    appID:"builtinApplication",
    operation:"loadFile",
    oldValues:{
        path:"/tank0/SmartClient10/SmartClient_v100p_2015-09-16_Pro/smartclientSDK/tools/visualBuilder/workspace/gradAppl.ui.xml"
    }
}
=== 2015-09-17 14:25:13,174 [80-2] DEBUG DeclarativeSecurity - Processing security checks for DataSource null, field null
=== 2015-09-17 14:25:13,174 [80-2] DEBUG DeclarativeSecurity - DataSource Filesystem is not in the pre-checked list, processing...
=== 2015-09-17 14:25:13,174 [80-2] WARN  DataSourceDMI - DataSource Filesystem: received a request to execute an operation of type 'fetch' named 'loadFile', but this operation is not defined to the dataSource.  Falling back to default behavior for operationType 'fetch'
=== 2015-09-17 14:25:13,174 [80-2] DEBUG AppBase - [builtinApplication.loadFile] No userTypes defined, allowing anyone access to all operations for this application
=== 2015-09-17 14:25:13,174 [80-2] DEBUG AppBase - [builtinApplication.loadFile] No public zero-argument method named '_loadFile' found, performing generic datasource operation
=== 2015-09-17 14:25:13,174 [80-2] DEBUG FilesystemDataSource - [builtinApplication.loadFile] returnContent is: true
=== 2015-09-17 14:25:13,174 [80-2] WARN  FilesystemDataSource - [builtinApplication.loadFile] using path: /tools/visualBuilder/workspace/gradAppl.ui.xml
=== 2015-09-17 14:25:13,174 [80-2] DEBUG FilesystemDataSource - [builtinApplication.loadFile] responseForFileList is Loading: /tank0/SmartClient10/SmartClient_v100p_2015-09-16_Pro/smartclientSDK/tools/visualBuilder/workspace/gradAppl.ui.xml
=== 2015-09-17 14:25:13,174 [80-2] INFO  DSResponse - [builtinApplication.loadFile] DSResponse: List with 1 items
=== 2015-09-17 14:25:13,175 [80-2] DEBUG RPCManager - Content type for RPC transaction: text/plain; charset=UTF-8
=== 2015-09-17 14:25:13,175 [80-2] DEBUG RPCManager - non-DMI response, dropExtraFields: false

[Isomorphic]

It looks like you posted one item that the FAQ mentions, but we actually need all the items listed in the FAQ, as well as the screen definition in this case (or, any screen definition that replicates the problem).

[rpoyner]

I was able to get this fixed by switching to a newer snapshot, and re-creating the screen I was working on.