generated namespace prefix is invalid
See original GitHub issueWith 1.0.0b12
, I now get documents from to_xml
that begin like this:
<pc:PcGts xmlns="http://schema.primaresearch.org/PAGE/gts/pagecontent/2019-07-15">
Thus, all elements use the pc
prefix, but this is not declared in the root as xmlns:pc=...
.
IMO, this regression is a combination of c0c1ea6ac9a20228fe07f2c3c1d741c4a07b2475 and the earlier af5098da – first to_xml
was rewritten to not include the pc
prefix anymore (but at that time it was also not used in the generateDS call), then the generateDS call changed (but to_xml
was not changed back accordingly).
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Invalid namespace prefix generated. - SmartBear Community
We are getting an invalid namespace prefix when generating a soap request. Example: xmlns: x/ ="
Read more >Invalid namespace prefix for xpath - xml - Stack Overflow
I've been using xml spy to run xpath. I hoped "//ns1:Value" would get me the Value nodes but it gives the error "Invalid...
Read more >Invalid XML document. The namespace prefix is not allowed ...
I get this error: Invalid XML document. The namespace prefix is not allowed to start with the reserved string "xml". Please resolve this...
Read more >PHP-client lib generates invalid XML - namespace prefix xsi ...
On aug.4.2011 I'v updated my working copy of PHP-client lib from the svn-repository http://google-api-adwords-php.googlecode.com/svn/trunk/.
Read more >"OakName0001: Invalid namespace prefix" error during ...
This error indicates a node or a property with an unregistered namespace in the package. As to the example in the Description, “custom”...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in 1.0.0b15
ok. never mind.