-
Notifications
You must be signed in to change notification settings - Fork 43
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
xsd2py failing #83
Comments
I have been working on a lot of fixes and this one might be solved in my improvements branch by the commit 828e4a5. I still have a few more things to finish before I submit a pull request. According to the specification |
@thomas-mangin Can you try Nick's branch as suggest in his comment above? |
I was pretty sure to run this branch but to make absolutely sure, I done this ( OSX )
So it seems the bug is still present in this branch -- sorry 😢 |
And sorry - I should have said I was running Nick's branch - but looking at the recent tickets it looked like the code to run to try parse complex XSDs. |
Thank you for your quick response. Unfortunately I'm short on time (easter around the corner) so if you need something faster than 2 weeks you need either to debug this yourself or look at another library... attached reproducer file so it can't go away: cwmp14.txt |
Being an open source developer too, I can appreciate your position. As it seems your library is the right fit for us, you will most likely see me pop up back here in a few weeks - I hope you won't mind the pestering if your life an work got in the way of happy hacking 😄 Thank you for your help so far. |
Looking forward to your questions/contributions :-) |
It is related to my changes to support relative paths and these imports.
When I had this problem, I just removed these imports and it worked. Of course it is not the fix, just a quick hack. I'll try to fix it soon. |
@iurisilvio I have further changes I was working on related to the relative path issues so I'll look at your changes and compare to mine. I should be able to push further updates later today. |
Based on what @pope1ni said is it ok if I wait a bit with merging? @iurisilvio: thank you very much for your quick fix, much appreciated. |
Yes, wait for @pope1ni. Feel free to use my changes or ignore it if you already did something to fix this issue. 👍 |
I tested this XSD file today and it failed for another reason. This issue is fixed.
Now it fails with another error.
First the command failed because the site does not accept requests |
If I recall, the issue we had was to do with whether imported files were local or remote and this would be affected in different ways depending on whether the initial path provided on the command line was local or remote. In this instance, although the initial path was a remote path, the code originally checked whether the path started with a slash to determine whether it was local. In the remote case, however, starting with a slash indicates that the path is relative to the root of the domain. Worse, if the file is then downloaded from the initial path and used locally, these paths will be incorrect as they should be rewritten to remote paths rather than looking like absolute local paths. But there is probably not much we can do about that... |
You are correct. I fixed the problem with the relative paths for remote files, that were handled as local paths. If you download the file and run it, I think all WSDL/XSD readers will fail too, because you don't have the original URL reference. Maybe we can provide a way to reference it from command line, but I don't think it is a real issue, you have to download all your xsd schema tree. |
PR #93 was irrelevant to this issue, but PR #96 resolved the issue in the latest stacktrace above. In addition, I fixed two additional problems in 2ef18c8 and 3ac2a6b that affected the schema file in question. Now we are blowing up because we always expect I've attached all of the schema files for future reference: cwmp-1-1.xsd.txt There are also other weird things that haven't event been considered in some of these such as |
Hello Felix,
I never had to use xsd/wsdl/soap before but I am trying to find a library which can help me implement correctly a tr-069 server (instead of just generating/parsing the XML 'by hand') like many available open source projects.
soapfish seems to be a good contender for the job but before I can even get started I have this issue.
Any help would be welcomed ! Thank you.
The text was updated successfully, but these errors were encountered: