-
Notifications
You must be signed in to change notification settings - Fork 154
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
problem following import #23
Comments
I haven't checked it but could you try the following?
It doesn't follow import by design since I didn't want scalaxb to go out to the web. |
Eugene, Similar result: scalaxb EPCglobal.xsd epcglobal_1_0.xsd StandardBusinessDocumentHeader.xsd -p test java.lang.RuntimeException: resolveType type not found: Partner ReferenceTypeSymbol(Partner,null) Here is the contents of standardBusinessDocumentHeader.xsd <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" targetNamespace="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" elementFormDefault="qualified" attributeFormDefault="unqualified"> |
Ok, I'll take a look at this. |
It can't resolve
You need to pass in all dependent schemas. |
That worked! Actually this worked: scalaxb basicTypes.xsd businessScope.xsd documentIdentification.xsd epcglobal_1_0.xsd EPCglobal.xsd epcglobalMasterData_1_0.xsd epcglobalQuery_1_0.xsd manifest.xsd partner.xsd standardBusinessDocumentHeader.xsd -p test Can't wait to play with the output, Thanks for your time, david... |
No problem. I am now thinking maybe I should load schemas automatically at least from the local file system if they are not passed in explicitly. |
Makes sense to me. Also it would be great if the tutorial made it more explicit you can pass multiple xsd's to it. |
Implemented current directory search. Also added a document on the website: http://scalaxb.org/multiple-schema-files |
running
yields:
with the following two files:
epcglobal_1_0.xsd:
and EPCglobal.xsd:
---- thanks ... david bolene
The text was updated successfully, but these errors were encountered: