EDN Admin
Well-known member
I have some complex xml files I need to validate against schemas that import/refer to other (sub) schemas. This is working fine during development, but when I deploy to a system that is virtualized (meaning the workstation and MS-SQL servers are virtual machines), one of the first sub schema I try to add to an xmlSchemaSet takes much longer than on the development system. It also slows way down on the xmlReader.create statement.
Another big note is that the virtualized system is a closed network (not connected to the Internet).
Other notes: I have one xml file that validates aginast only one schema, and that xmlSchemaSet.add and the following xmlReader.create runs without hesitation.
Has anyone ever experienced a problem like this? The validation routine works buts its very slow on the virtualized system (except for the xml file that validates against only one schema, it runs faster on the virtual system than on the dev system).
All the schemas and xmls validate without problems through other tools, but I need this be automatic.
Im thinking it might be hardware configuration, but I cant isolate it as of yet.
Any ideas?
r/Jamie
View the full article
Another big note is that the virtualized system is a closed network (not connected to the Internet).
Other notes: I have one xml file that validates aginast only one schema, and that xmlSchemaSet.add and the following xmlReader.create runs without hesitation.
Has anyone ever experienced a problem like this? The validation routine works buts its very slow on the virtualized system (except for the xml file that validates against only one schema, it runs faster on the virtual system than on the dev system).
All the schemas and xmls validate without problems through other tools, but I need this be automatic.
Im thinking it might be hardware configuration, but I cant isolate it as of yet.
Any ideas?
r/Jamie
View the full article