-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Problems with JMS-Metadata-Generator #137
Comments
hmm, that is nice |
thanks for the help :) I've managed to create a naming strategy, mentioned in this PR: |
to clarify, i had to take another path. the CustomNamingStrategy made problems when trying to (de)serialize, i wasn't able to create the php-object or a schema-valid xml file. i had to change the generation part: i had to change the (de)serializaion part -> jms-serializer: $serializerBuilder->setMetadataDriverFactory(new CallbackDriverFactory(function ($metadataDirs, Reader $reader) {
return new DriverChain([
new YamlDriver(new MyOwnFileLocator($metadataDirs), new SerializedNameAnnotationStrategy(new CamelCaseNamingStrategy())),
new AnnotationDriver($reader, new SerializedNameAnnotationStrategy(new CamelCaseNamingStrategy())),
]);
})); atm it looks like all tests are green :) |
nice idea... having such |
Hello, have to implement an OTA-Fork called Alpinebits.
Link to the documentation: Alpinebits-Documentation
I use xsd2php and the JMS-Serializer which is an awesome combination!!!
But the xsd-schema is very nested and during generation, i get errors for some nested elements, that the filename is longer than 255.
Are there possibilities to solve this Problem ?
My config.yml
Some generated Metadata-Definitions
The text was updated successfully, but these errors were encountered: