[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2028:
--------------------------------
Fix Version/s: 8.4
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> …
[View More] Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Ted Jones
> Fix For: 8.4
>
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2028:
----------------------------------------
The user used the New Model Wizard (Web Service) > Build from existing WSDL option rather than importing via the newer "Import > Teiid Designer > WSDL File or URL >> Source and View Model (SOAP)" option.
The old method results in a WS model (Operations) with XML Document model. THis is intended to allow getting XML …
[View More]out the top and is kind of hands-off.
THinking better way is to use new importer to create view model, then create Web Service model from the the view model.
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2028:
-------------------------------------
Summary: Teiid tooling fails to create metamodel for web service
Key: TEIIDDES-2028
URL: https://issues.jboss.org/browse/TEIIDDES-2028
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 8.3
Reporter: Van Halbert
Description of problem:
Unable to build metamodel for customer provided WSDL file. …
[View More]Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
Version-Release number of selected component (if applicable):
JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
How reproducible:
Everytime
Steps to Reproduce:
1. Create Teiid Model Project
2. Import WSDL under schemas folder
3. Use Teiid Metamodel wizard to consume WSDL
see BZ for attachments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2026) Missed metadata on import
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2026?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2026:
----------------------------------------
This is the block of code in RelationalModelProcessorImpl that is extracting the column properties:
{code}
// Get the column information ...
final Request request = tableNode.getRequest(GetColumnsRequest.NAME, false);
final Results results = request.getResults();
final Object[] rows =…
[View More] results.getRows();
final int numRows = results.getRowCount();
// Results are ordered by ORDINAL_POSITION
for (int i = 0; i < numRows; ++i) {
final Object row = rows[i];
final String name = results.getString(row, 3);
final int type = results.getInt(row, 4);
final String typeName = results.getString(row, 5);
final int columnSize = results.getInt(row, 6);
// buffer length; unused
final int numDecDigits = results.getInt(row, 8);
final int numPrecRadix = results.getInt(row, 9);
final int nullable = results.getInt(row, 10);
final String remarks = results.getString(row, 11);
final String defaultValue = results.getString(row, 12);
// sql_data_type; unused
// sql_datetime_sub; unused
final int charOctetLen = results.getInt(row, 15);
// final int position = results.getInt(row,16);
// final String isNullable = results.getString(row,17);
{code}
> Missed metadata on import
> -------------------------
>
> Key: TEIIDDES-2026
> URL: https://issues.jboss.org/browse/TEIIDDES-2026
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.7, 8.3
> Reporter: Johnathon Lee
>
> After import, NUM_DISTINCT and NUM_NULLS metadata found in the source system shows as "-1" when the underlying datasource has values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2025) JBDS 7/Designer 8.3 having issues connecting to a EDS 5.x server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2025?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2025.
------------------------------------
Fix Version/s: 8.3.1
Resolution: Done
Done. Applied to 8.3.x Branch and 8.4 (master)
> JBDS 7/Designer 8.3 having issues connecting to a EDS 5.x server
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2025
> URL: https://issues.…
[View More]jboss.org/browse/TEIIDDES-2025
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Paul Richardson
> Priority: Critical
> Fix For: 8.4, 8.3.1
>
>
> Teiid Designer is having issues connecting to an EDS 5.x server.
> I see the issue manifest itself in several areas:
> - setting up the server instance to point to the EDS 5.x server, and have it configured to externally managed. Start the server, but the Teiid Server Instance subsystem shows its not connected
> - Was able to use the JBDS import to create source model, but was unable to execute data preview, as an error message was presented that said it could not connect to the server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2026) Missed metadata on import
by Colin Mondesir (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2026?page=com.atlassian.jira.plu... ]
Colin Mondesir commented on TEIIDDES-2026:
------------------------------------------
After running "EXEC dbms_stats.gather_schema_stats(’CMONDESIR’, cascade=>TRUE)" to generate stats for tables under my schema, I checked the number of distinct and null values for a specific table:
SQL> SELECT COLUMN_NAME, NUM_DISTINCT, NUM_NULLS FROM DBA_TAB_COL_STATISTICS WHERE TABLE_NAME ='JBM_POSTOFFICE' and OWNER = '…
[View More]CMONDESIR' ORDER BY COLUMN_NAME;
COLUMN_NAME NUM_DISTINCT NUM_NULLS
------------------------------ ------------ ----------
ALL_NODES 1 0
CHANNEL_ID 117 0
CLUSTERED 2 0
COND 57 0
NODE_ID 4 0
POSTOFFICE_NAME 1 0
QUEUE_NAME 57 0
SELECTOR 0 117
Then [Import] --> [Teiid Designer] --> [JDBC Database >> Source Model] add select the table above
One the table metadata has been imported click through each field and notice that "Distinct Value Count" and "Null Value Count" display as "-1".
Checking the .xmi I see that there are no "distinctValueCount" or "nullValueCount" entries.
> Missed metadata on import
> -------------------------
>
> Key: TEIIDDES-2026
> URL: https://issues.jboss.org/browse/TEIIDDES-2026
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.7, 8.3
> Reporter: Johnathon Lee
>
> After import, NUM_DISTINCT and NUM_NULLS metadata found in the source system shows as "-1" when the underlying datasource has values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 2 months