[
https://issues.jboss.org/browse/TEIIDDES-1317?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1317:
----------------------------------------
Need to test this both by adding Schema file(s) to a VDB, saving and checking the vdb.xml
manifest for the OTHER type.
Secondly, take an OLD vdb that still has "TYPE" as a xsd model type, tweak the
VDB (i.e. edit it) and save. Then check the vdb.xml for "OTHER" instead of TYPE
for the old XSD model entry
wrong type on model in VDB definition
-------------------------------------
Key: TEIIDDES-1317
URL:
https://issues.jboss.org/browse/TEIIDDES-1317
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.6
Environment: Windows
Reporter: luca gioppo
Assignee: Barry LaFond
Priority: Blocker
Fix For: 7.7.1
In a VDB created for transforming relational data to XML from exixting XSD the VDB insert
"TYPE" in the model description in the manifest file as shown below:
<?xml version="1.0" encoding="UTF-8"
standalone="yes"?>
<vdb version="1" name="libri">
<property value="false" name="preview"/>
<model visible="true" type="PHYSICAL"
name="local_book" path="/books/local_book.xmi">
<property value="1841187605" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="440299790.INDEX" name="indexName"/>
<source translator-name="mysql5"
connection-jndi-name="java:/local_book" name="local_book"/>
</model>
<model visible="true" type="TYPE" name="Books"
path="/books/Books.xsd">
<property value="2392354248" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="4008441630.INDEX" name="indexName"/>
<property value="/books/BookDatatypes.xsd"
name="imports"/>
</model>
<model visible="true" type="TYPE"
name="BookDatatypes" path="/books/BookDatatypes.xsd">
<property value="3412846293" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="3680615365.INDEX" name="indexName"/>
</model>
<model visible="true" type="VIRTUAL" name="libro"
path="/books/libro.xmi">
<property value="1493944231" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="2863148665.INDEX" name="indexName"/>
<property value="/books/Books.xsd" name="imports"/>
<property value="/books/BookDatatypes.xsd"
name="imports"/>
<property value="/books/local_book.xmi"
name="imports"/>
<validation-error
path="bookListingDocument/bookListing/sequence/book/type"
severity="WARNING">The XML Schema component type for "type"
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 "isbn"
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">"edition" 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
"title" 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
"edition" 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
"publishDate" must be marked as an enterprise datatype to be used in
this model.</validation-error>
</model>
</vdb>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira