Schema location during development
Posted: Fri May 04, 2012 12:23 pm
Hi,
I have to do some work on schema's and documents developed by someone else at another location. From my location, the schemalocations are not accessible (they're on an internal network).
What is the best way to work on these documents, being able to validate them, without network access to the schemalocation?
I can think of a few workarounds:
- redirect requests to the schemalocation to a local server and host the xsd from there;
- temporarily replace the schemalocations with local locations and change them back when delivering the results;
Neither is very satisfying though and I was wondering if oXygen offered some way to deal with this problem internally? Or am I missing some obvious way to deal with this problem that is not particular to oXygen?
Any hints or suggestions appreciated,
Grismar.
I have to do some work on schema's and documents developed by someone else at another location. From my location, the schemalocations are not accessible (they're on an internal network).
What is the best way to work on these documents, being able to validate them, without network access to the schemalocation?
I can think of a few workarounds:
- redirect requests to the schemalocation to a local server and host the xsd from there;
- temporarily replace the schemalocations with local locations and change them back when delivering the results;
Neither is very satisfying though and I was wondering if oXygen offered some way to deal with this problem internally? Or am I missing some obvious way to deal with this problem that is not particular to oXygen?
Any hints or suggestions appreciated,
Grismar.