Hello,
We have extended DataSourceLoader with DynamicDSGenerators, to load up DataSources based on database-extracted ds.xml files.
All worked well when we used long prefixes ("TAB_" and "TREE_").
However, when we modified the prefixes, the DynamicDSGenerator for the "R" prefix started - with its DataSource.fromXML() method - trying to load things like...
..."RowSpacerItem0" from an RPCManager.loadScreen-requested xml.ui file, most probably because its name matches the prefix.
It seems that if our app loads anything from XML, and the element's name matches one of the DynamicDSGenerator prefixes, the load request gets routed through the DataSourceLoader.
SmartGWT EE version:
v8.3p_2013-02-14/EVAL Deployment
Browser:
Firefox 20.0
Our exceptions are custom, so they would not provide you too much pertinent information.
If it seems like it might be hard to reproduce, please let us know - we will be happy to cobble together a test case.
Regards.
We have extended DataSourceLoader with DynamicDSGenerators, to load up DataSources based on database-extracted ds.xml files.
All worked well when we used long prefixes ("TAB_" and "TREE_").
However, when we modified the prefixes, the DynamicDSGenerator for the "R" prefix started - with its DataSource.fromXML() method - trying to load things like...
..."RowSpacerItem0" from an RPCManager.loadScreen-requested xml.ui file, most probably because its name matches the prefix.
It seems that if our app loads anything from XML, and the element's name matches one of the DynamicDSGenerator prefixes, the load request gets routed through the DataSourceLoader.
SmartGWT EE version:
v8.3p_2013-02-14/EVAL Deployment
Browser:
Firefox 20.0
Our exceptions are custom, so they would not provide you too much pertinent information.
If it seems like it might be hard to reproduce, please let us know - we will be happy to cobble together a test case.
Regards.
Comment