You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
and thanks for your answer.
While trying to reproduce the bug in a test case, i discovered from where the bug is coming from :
i have a "namespace" annotation on my "Feed" class, with the uri attribute linking to an xsl file.
Is the serializer checking that xsl schema definition ?
or that still a bug ? (i got the test case if you want)
i have a "namespace" annotation on my "Feed" class, with the uri attribute linking to an xsl file.
Is the serializer checking that xsl schema definition ?
depends on what you have exactly as namespace... but in general yes..
Hello,
i think i encountered a weird issue in the xml deserialization.
I got a Feed class that contains a collection of Products. These products have an array of string (entry = ean.
Here is my simplified model :
When i create the xml from the php model, i got exactly what i want :
Results in :
But then, when i deserialize back this feed :
My product->eans is an empty array...
The weird thing is when i work with only one product (no feed, no array collection) my eans array is well hydrated :
I got the expected xml, and then the expected EANs hydrated in my $productUnserialized object.
Is that a bug from the deserializer ?
Thanks for helping
The text was updated successfully, but these errors were encountered: