March 14, 2012 at 12:46 pm
This issue will be 5 years old two weeks from tomorrow so we can take out time.
But maybe a little poke might be appropriate.
I do have to get this solved but I'm thinkin' maybe Pascal, C or our old company DIBOL?
We generated XML with that and it looked just fine.
The attachment started out as an appendix to my documentation for the project, hence 'Appendix B', but evolved somewhat.
The attachment has test data, code, references and snide remarks.
It might even be good as a final exam question.
You have my permission.
Thanks
March 14, 2012 at 2:07 pm
Why not create the xml structure without the namespace reference, but with the nil element and replace < sourcename > with < sourcename xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > and nil="true" with "xsi:nil="true" ?
Edit: Or, alternatively, replace
< detail xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > with < detail >
March 14, 2012 at 4:44 pm
I was thinking, since the incoming files are SOAP and I have to rinse out the SOAP before I can shred them, I may as well rinse out the namespace in the detail before I send it out.
Of course, with all of the SOAP floating around, some Water Quality Control Board will pay a visit.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply