-
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible to prefix the root element while serializing? #5
Comments
Hi, this is not possible at the moment. I have solved it adding the prefix But it will be an interesting feature for the jms serializer, PR are On 12 Nov 2016 1:57 pm, "Frederico Martini" notifications@github.com
|
Reading better your message, do not understand the problem. What you have suggested in your code snippet is exactly how is implemented now |
I can only set prefix name to Default namespace generate is: Better to understand now? Thanks @goetas |
ah, i see. planned to be resolved in 1.5 or 1.6 version of jms serializer |
I have the same problem. I still don't know how to set the root_name. And I don't know how schmittjoh/serializer#644 is solving this? All I get is a random generated string. For example: thanks |
any reason to have a specific prefix? for xml-sematics prefix should be almost irrelevant |
Unfortunately our delivery house for Spotify rejected our xml's and said the root_name wasn't set as they need. I understand that a quick fix would be to change the .yml manually, right? I also need this added The .yml looks like this:
generating this:
But I need:
Any idea? Thanks again! |
xsd2php/src/Jms/YamlConverter.php Line 150 in d7e40e3
|
Hello, is this issue still occuring? I'm having the same problem as reported in this post.
Or do we have now something to give what we want? Thanks |
|
While generating metadata files is possible to set namespace prefix to the root element?
e.g:
myXmlElement:
xml_root_name: "ds1:foobar"
xml_root_namespace: "http://www.example"
will turn serialized:
<?xml version="1.0" encoding="UTF-8"?>
<ds1:foobar xmlns:ds1="http://www.example">
</ds1:foobar>
The text was updated successfully, but these errors were encountered: