Bug 1228567 - Changing parameter types in REST connection results in wrong URL
Summary: Changing parameter types in REST connection results in wrong URL
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Barry LaFond
QA Contact: Andrej Smigala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-05 08:16 UTC by Andrej Smigala
Modified: 2015-11-17 18:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-17 18:05:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDES-2553 0 Major Closed Changing parameter types in REST connection results in wrong URL 2015-08-03 10:48:14 UTC

Description Andrej Smigala 2015-06-05 08:16:00 UTC
Changing the type of a parameter in the REST connection profile causes the generated URL to be wrong. Also, the Preview URL is not updated after changing the type, only after some other action (testing connection, changing the default value etc).
Furthermore, removing the paramters does not work if the type of the parameter has been changed.

Steps to reproduce:
# File -> New -> Other ->  Connection Profile -> Web Services Data Source (REST)
# set Connection URL to http://localhost:8000
# add two new parameters of type Query, p1 and p2 with default values v1 and v2
# change the p1 parameter's type to URI
# notice the Preview URL does not reflect the change
# click Test Connection
# notice the Preview URL is now http://localhost:8000/v1?p2=v2/v1  (wrong)
# change the type back to Query, click Test Connection
# notice the Preview URL is now http://localhost:8000?p1=v1&p2=v2&rest_param%3Ap1=v1
# try to delete both parameters

Comment 2 JBoss JIRA Server 2015-07-21 17:44:56 UTC
Ted Jones <tejones> updated the status of jira TEIIDDES-2553 to Resolved

Comment 3 JBoss JIRA Server 2015-08-03 07:31:21 UTC
Andrej Šmigala <asmigala> updated the status of jira TEIIDDES-2553 to Closed

Comment 4 JBoss JIRA Server 2015-08-03 10:47:45 UTC
Andrej Šmigala <asmigala> updated the status of jira TEIIDDES-2553 to Reopened

Comment 5 JBoss JIRA Server 2015-08-03 10:48:14 UTC
Andrej Šmigala <asmigala> updated the status of jira TEIIDDES-2553 to Closed


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