[JBoss JIRA] (TEIIDDES-2137) Unable to Generate REST WAR Due to Missing Teiid Class
by Ted Jones (JIRA)
Ted Jones created TEIIDDES-2137:
-----------------------------------
Summary: Unable to Generate REST WAR Due to Missing Teiid Class
Key: TEIIDDES-2137
URL: https://issues.jboss.org/browse/TEIIDDES-2137
Project: Teiid Designer
Issue Type: Feature Request
Components: Web Services Support
Affects Versions: 8.5
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 8.5
When attempting to generate a REST war, I received the following exception:
java.lang.Exception: /Users/tejones/apps/plugins/teiid-designer/plugins/org.teiid.designer.webservice/rest_war_build/work/1398793292649_5538618606854300057/BooksRest/WEB-INF/classes/org/teiid/rest/services/TeiidRSProviderPost.java:34: cannot find symbol
symbol : class TransformationException
location: package org.teiid.core.types
at org.teiid.designer.runtime.ui.wizards.webservices.util.RestWebArchiveBuilderImpl.createResourceJavaClasses(RestWebArchiveBuilderImpl.java:557)
at org.teiid.designer.runtime.ui.wizards.webservices.util.RestWebArchiveBuilderImpl.createWebArchive(RestWebArchiveBuilderImpl.java:222)
at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.execute(RestWarDeploymentInfoDialog.java:210)
at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog$1.run(RestWarDeploymentInfoDialog.java:165)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
--
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
10 years
[JBoss JIRA] (TEIIDDES-1992) Designer generates wrong view model transformations for some services
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1992?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-1992.
---------------------------------
Resolution: Done
While some of the code was missing from the original PR in master (perhaps due to the merging of client code to handle multiple Teiid versions), there were still additional changes that needed to be made for handling ns with child elements in the request. Also, while adding a DEFAULT ns might "fix" the issue, this is dangerous in cases where there are other namespaces used in the schema. The country info schema has a target namespace, but only one ns in total, so DEFAULT worked. The change made for this fix was to use the ns for the element (which is the tns in this case).
Country info WSDL used for dev and test: http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoServic...
> Designer generates wrong view model transformations for some services
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-1992
> URL: https://issues.jboss.org/browse/TEIIDDES-1992
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Ted Jones
> Priority: Critical
> Fix For: 8.5, 8.4, 8.3.1
>
>
> When generating web service view from WSDL, the designer incorrectly adds the namespace to the request. The request [1] declares the "tns" prefix but since the namespace is not added to the actual request it generates [2].
> User can workaround this by directly modifying the request [3].
> [1]
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT XMLELEMENT(NAME getPeopleByName, XMLNAMESPACES('http://www.jboss.org/jbossas/dv/PeopleJaxws' AS tns)) AS xml_out;
> END
> [2] Caused by: javax.xml.ws.ProtocolException: Remote javax.xml.ws.soap.SOAPFaultException: Unexpected wrapper element getPeopleByName found. Expected {http://www.jboss.org/jbossas/dv/PeopleJaxws}getPeopleByName.
> [3]
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT XMLELEMENT(NAME getPeopleByName, XMLNAMESPACES(DEFAULT 'http://www.jboss.org/jbossas/dv/PeopleJaxws')) AS xml_out;
> END
--
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
10 years
[JBoss JIRA] (TEIIDDES-2134) Changing connection profile of a source model does not update the translator in importing VDB
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2134?page=com.atlassian.jira.plu... ]
Lucie Fabrikova commented on TEIIDDES-2134:
-------------------------------------------
Regarding the JNDI name (again tab Source binding in vdb editor), I think it is not updated in the method VdbModelEntry.synchronizeModelEntry() at all; but for the connection profile of type JBoss datasource, the JNDI name property is being set.
Proposed fix for the JNDI name:
- evaluate the helper.getJndiProperty(mr), if it is not null and not empty, set this.sourceInfo.getSource(0).setJndiName(helper.getJndiProperty(mr));
> Changing connection profile of a source model does not update the translator in importing VDB
> ---------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2134
> URL: https://issues.jboss.org/browse/TEIIDDES-2134
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Andrej Šmigala
>
> Steps to reproduce:
> # Import a source model
> # Create a new VDB and add the source model to it
> # Set connection profile to a different db (with different translator)
> # Synchronize the model in the VDB
> The translator and JNDI name are not updated in the VDB.
--
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
10 years
[JBoss JIRA] (TEIIDDES-2135) Parse Error Persists After Correcting Query
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2135?page=com.atlassian.jira.plu... ]
Ted Jones commented on TEIIDDES-2135:
-------------------------------------
This version check for a query starting with BEGIN seems to be the issue. On line 1112 of the generated Teiid8Parser, there is a case statement for BEGIN followed by a required version check on line 1113 for a minimum version of 8.5 (I am connected to an 8.4 server). I know this syntax was supported prior to 8.5, so the required version should be lowered.
> Parse Error Persists After Correcting Query
> -------------------------------------------
>
> Key: TEIIDDES-2135
> URL: https://issues.jboss.org/browse/TEIIDDES-2135
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Validation
> Affects Versions: 8.5
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> After incurring a parse error in the sql transformation error, the parse error remains even after correcting the sql.
--
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
10 years