xsd2cocoa icon indicating copy to clipboard operation
xsd2cocoa copied to clipboard

Tests fail & App not working on El Capitan / Xcode 7

Open ghost opened this issue 9 years ago • 10 comments

Hello,

I was pretty glad to find a framework helping me in working with XSDs. Unfortunately, I can build the App and run, but the generation fails. I then started the tests, and many of them fail. I noticed that several error message are talking of "namespace", so it may be that this relates to the other open issue here. As I'm not using ObjC, but Swift, I'm pretty helpless in fixing anything myself... ;-) I attached the test results for your information.

Best regards

ghost avatar Nov 28 '15 09:11 ghost

hi, weird. you are missing the default include directory. im not on 10.11 and there all tests work :(

ill look into it - maybe tomorrow night maybe moday

can you provide me the xsd & xml you wanna parse?

cheers, dominik

On Nov 28, 2015, at 10:41 AM, innoreq [email protected] wrote:

Hello,

I was pretty glad to find a framework helping me in working with XSDs. Unfortunately, I can build the App and run, but the generation fails. I then started the tests, and many of them fail. I noticed that several error message are talking of "namespace", so it may be that this relates to the other open issue here. As I'm not using ObjC, but Swift, I'm pretty helpless in fixing anything myself... ;-) I attached the test results for your information.

Best regards

Hardy TestResults.txt https://github.com/Daij-Djan/xsd2cocoa/files/46302/TestResults.txt — Reply to this email directly or view it on GitHub https://github.com/Daij-Djan/xsd2cocoa/issues/6.

Daij-Djan avatar Nov 28 '15 15:11 Daij-Djan

Hello Dominik,

thanks for your response! Actually, I’m not yet at the point to input any XSD (actually, I can, but then the app fails, probably for the same reason - that’s why I executed the tests - so the effect is independent of any data).

Attached you find a screenshot of the test run. Perhaps this gives you some more hints.

Cheerio, Hardy

Am 28.11.2015 um 16:33 schrieb Dominik Pich [email protected]:

hi, weird. you are missing the default include directory. im not on 10.11 and there all tests work :(

ill look into it - maybe tomorrow night maybe moday

can you provide me the xsd & xml you wanna parse?

cheers, dominik

On Nov 28, 2015, at 10:41 AM, innoreq [email protected] wrote:

Hello,

I was pretty glad to find a framework helping me in working with XSDs. Unfortunately, I can build the App and run, but the generation fails. I then started the tests, and many of them fail. I noticed that several error message are talking of "namespace", so it may be that this relates to the other open issue here. As I'm not using ObjC, but Swift, I'm pretty helpless in fixing anything myself... ;-) I attached the test results for your information.

Best regards

Hardy TestResults.txt https://github.com/Daij-Djan/xsd2cocoa/files/46302/TestResults.txt — Reply to this email directly or view it on GitHub https://github.com/Daij-Djan/xsd2cocoa/issues/6.

— Reply to this email directly or view it on GitHub https://github.com/Daij-Djan/xsd2cocoa/issues/6#issuecomment-160311433.

ghost avatar Nov 28 '15 15:11 ghost

ok I fixed the unit tests for 10.11. the problem was that I used the /usr/include dir directly and on 10.11 this isn't there by default. They should be all green now.

The demo apps also work fine for me.

what is your issue exactly?

Daij-Djan avatar Dec 05 '15 22:12 Daij-Djan

Great, things look much better now. However, there is still a problem in some of the Swift tests: bildschirmfoto 2015-12-06 um 11 48 25 This concerns three of those tests, all other tests are working fine: bildschirmfoto 2015-12-06 um 11 50 10

ghost avatar Dec 06 '15 10:12 ghost

I tried to run the tool with my own XSD. I selected the XSD file, the output folder was elicited automatically, target was "Swift", pushing "Process" button => nothing happens. No error, no change of the output folder, no dialog, just nothing... strange...

ghost avatar Dec 06 '15 10:12 ghost

I noticed, btw, that when after the line a comment line occurs (like with Altova XMLSpy), the input XSD file is not recognized as such by the tool.

ghost avatar Dec 06 '15 10:12 ghost

Changing to "ObjC" does not change the bevaviour of doing nothing.

ghost avatar Dec 06 '15 10:12 ghost

I removed all whitespaces and comments from my XSD file, but no change. (I suspected the comments to be the reason for the problems.)

ghost avatar Dec 06 '15 11:12 ghost

I made the parsers way more tolerant concerning other content atop the root element

Daij-Djan avatar Mar 28 '16 13:03 Daij-Djan

ill upload a version tonight (CET)

Daij-Djan avatar Mar 28 '16 13:03 Daij-Djan