Hi,
I've been doing some development for the next version of our application using 10.1 pre-release.
I use the "component XML" approach to building screens and download their definitions in logical groups using RPCManager.cacheScreens() as needed.
Recently I updated our copy of SmartClient from SmartClient_SNAPSHOT_v101d_2015-08-23_Pro to SmartClient_SNAPSHOT_v101d_2015-09-29_Pro.
Now, I am unable to download any component XML at all. The call to cacheScreens() returns without error, but no screen definitions are cached.
From the tomcat access log, I can see that the call to the isomorphic screenLoader servlet is returning a 31 byte response - clearly no screen definitions.
There are warnings in the application log, one for each screen requested:
These warnings appear after each screen XML file has been read and processed.
My server.properties has the additional line:
I tried going back to SmartClient_SNAPSHOT_v101d_2015-08-30_Pro but this gives me the same result as the 09-29 release.
I don't think this is a problem with the content or location (shared/ui) of my XML files, but I've been wrong before :|
I have set the log level to "DEBUG" and attached some log files. The sc-08-23 files show a working download and the sc-08-30 show a failed download.
I edited out the timestamps and thread ids from these logs to enable a simple diff between the two cases. The only significant difference I can see is the presence of the WARN message in the second case.
I'm really hoping that Isomorphic can do a quick test of a component XML download to see whether this is an Isomorphic problem or an Andrew problem.
hoping this all makes sense,
best wishes,
Andrew
I've been doing some development for the next version of our application using 10.1 pre-release.
I use the "component XML" approach to building screens and download their definitions in logical groups using RPCManager.cacheScreens() as needed.
Recently I updated our copy of SmartClient from SmartClient_SNAPSHOT_v101d_2015-08-23_Pro to SmartClient_SNAPSHOT_v101d_2015-09-29_Pro.
Now, I am unable to download any component XML at all. The call to cacheScreens() returns without error, but no screen definitions are cached.
From the tomcat access log, I can see that the call to the isomorphic screenLoader servlet is returning a 31 byte response - clearly no screen definitions.
There are warnings in the application log, one for each screen requested:
Code:
=== 2015-10-01 11:27:44,591 [ec-3] WARN DataSource - Screen "UtHome" not found in configured locations. Skipping.
My server.properties has the additional line:
Code:
schema.strict.all:false
I don't think this is a problem with the content or location (shared/ui) of my XML files, but I've been wrong before :|
I have set the log level to "DEBUG" and attached some log files. The sc-08-23 files show a working download and the sc-08-30 show a failed download.
I edited out the timestamps and thread ids from these logs to enable a simple diff between the two cases. The only significant difference I can see is the presence of the WARN message in the second case.
I'm really hoping that Isomorphic can do a quick test of a component XML download to see whether this is an Isomorphic problem or an Andrew problem.
hoping this all makes sense,
best wishes,
Andrew
Comment