Bug 1273841 - REST procedure in generated dynamic VDB does not work
Summary: REST procedure in generated dynamic VDB does not work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Barry LaFond
QA Contact: Andrej Smigala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-21 11:34 UTC by Andrej Smigala
Modified: 2016-07-25 15:43 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-07 13:29:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDES-2698 0 Major Closed REST procedure in generated dynamic VDB does not work 2016-07-25 15:43:28 UTC

Description Andrej Smigala 2015-10-21 11:34:19 UTC
When a VDB containing view model with a REST procedure is exported as a dynamic VDB, the resulting autogenrated WAR does not work. This is because the generated DDL does not contain the OPTIONS clause with REST properties, not does it contain the required SET NAMESPACE statement

Generated DDL:

CREATE VIRTUAL PROCEDURE testProc (p1 string(4000))
	AS
 BEGIN
	SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
END;



Expected DDL (note that this also incorporates TEIIDDES-2697):

SET NAMESPACE 'http://teiid.org/rest' AS REST;
CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
	AS
 BEGIN
	SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
END;

Steps to Reproduce:
# import the attached project
# generate a dynamic VDB from DynamicProcedureVdb
# deploy and execute the dynamic vdb
# go to {{http://localhost:8080/dynamicprocedurevdb_1/proceduremodel/test/a}} in the browser, returns 500

Comment 2 Barry LaFond 2015-12-07 13:29:19 UTC
Using only JIRA now.  Marking as closed

Comment 3 JBoss JIRA Server 2016-03-01 14:47:41 UTC
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2698 to Reopened

Comment 4 JBoss JIRA Server 2016-03-02 11:47:59 UTC
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2698 to Resolved

Comment 5 JBoss JIRA Server 2016-07-25 15:43:29 UTC
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2698 to Closed


Note You need to log in before you can comment on or make changes to this bug.