<validation-error path="bookListingDocument/bookListing/sequence/book/type" severity="WARNING">The XML Schema component type for &quot;type&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/isbn" severity="WARNING">The XML Schema component type for &quot;isbn&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

<validation-error path="bookListingDocument/Mapping Class Set Container/Mapping Classes/book" severity="WARNING">Possible cross-join: Group/s '[local_book.aria.books, local_book.aria.publishers]' are not joined either directly or transitively to other groups through a join criteria. Check all queries in the transformation.</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">&quot;edition&quot; has a fixed or default value and should not be mapped. (See validation Preferences)</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/title" severity="WARNING">The XML Schema component type for &quot;title&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">The XML Schema component type for &quot;edition&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/publishDate" severity="WARNING">The XML Schema component type for &quot;publishDate&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

</model>

</vdb>

Could the type= TYPE be the problem?

maybe the designer missed the correct TYPE to assign to the xsd files included in the VDB?

<validation-error path="bookListingDocument/bookListing/sequence/book/isbn" severity="WARNING">The XML Schema component type for &quot;isbn&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">&quot;edition&quot; has a fixed or default value and should not be mapped. (See validation Preferences)</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/type" severity="WARNING">The XML Schema component type for &quot;type&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/publishDate" severity="WARNING">The XML Schema component type for &quot;publishDate&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">The XML Schema component type for &quot;edition&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/title" severity="WARNING">The XML Schema component type for &quot;title&quot; must be marked as an enterprise datatype to be used in this model.</validation-error>

https://issues.jboss.org/browse/TEIID-2017 addresses TEIIDDES-1317 on the Teiid side and will be in the final release. As for the underlying exception. What OS are you on? Can you show the contents of the VDB? In particular the path in the vdb to the .xmi file representing the document model (presumably this would be /books/libro.xmi) and then the pathes of the associated schemas (presumably at /books/*.xsd). Also can you show the modelImports/@modelLocation attribute values from the libro.xmi (presumably they should be /books/Books.xsd, etc.).

Is based on the book example from Ramesh using the xsd given in a previous post of this forum (I'm trying to reproduce the how-to written by Ramesh, just renamed the vdb and few stuff using irtalian words).

I expected to go smoothly and understand the relational to XML, but ... we know IT

I can query the mysql DB from squirrelsql so I presume that the VDB works correctly (at least I remember how to create a VDB), but when I try to query the document as in pg. 8 of Ramesh's PDF I get the error reported.

I must say that I DID NOT deployed any xsd in teiid server, just deployed the VDB and created the mysql data source.