[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1861:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1042907|https://bugzilla.redhat.com/show_bug.cgi?id=1042907] from NEW to ASSIGNED
> Designer deletes data role "condition" information
> --------------------------------------------------
>
> Key: TEIIDDES-1861
> URL: https://issues.jboss.org/browse/TEIIDDES-1861
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration, VDB & Execution
> Affects Versions: 8.2
> Environment: Windows 7, Eclipse kepler.
> Reporter: Pablo Navascues
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
> Attachments: Teiiddes-1861-screencapture.m4v
>
>
> Create a VDB
> Create a source model by importing from JDBC
> Add model to VDB
> Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)"
> Synchronize, save VBD.
> Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml.
> Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well.
> This has happened more than once and to more than one developer in the team.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1861:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1042907
> Designer deletes data role "condition" information
> --------------------------------------------------
>
> Key: TEIIDDES-1861
> URL: https://issues.jboss.org/browse/TEIIDDES-1861
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration, VDB & Execution
> Affects Versions: 8.2
> Environment: Windows 7, Eclipse kepler.
> Reporter: Pablo Navascues
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
> Attachments: Teiiddes-1861-screencapture.m4v
>
>
> Create a VDB
> Create a source model by importing from JDBC
> Add model to VDB
> Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)"
> Synchronize, save VBD.
> Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml.
> Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well.
> This has happened more than once and to more than one developer in the team.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1861:
-----------------------------------
Fix Version/s: 8.3.x
(was: 8.4)
> Designer deletes data role "condition" information
> --------------------------------------------------
>
> Key: TEIIDDES-1861
> URL: https://issues.jboss.org/browse/TEIIDDES-1861
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration, VDB & Execution
> Affects Versions: 8.2
> Environment: Windows 7, Eclipse kepler.
> Reporter: Pablo Navascues
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
> Attachments: Teiiddes-1861-screencapture.m4v
>
>
> Create a VDB
> Create a source model by importing from JDBC
> Add model to VDB
> Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)"
> Synchronize, save VBD.
> Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml.
> Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well.
> This has happened more than once and to more than one developer in the team.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1992) Designer generates wrong view model transformations for some services
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1992?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1992:
-----------------------------------
Fix Version/s: 8.3.x
(was: 8.4)
> 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.3.x
>
>
> 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, 9 months
[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 reassigned TEIIDDES-1992:
-----------------------------------
Assignee: Ted Jones (was: Barry LaFond)
> 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
>
> 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, 9 months