It's all about the answers!

Ask a question

Access created Workitem links get Error: com.ibm.team.repository.web.transport.ServiceRequest(): invalid requestParameters parameter: [object Object]


Debo Xiong (3146) | asked May 14 '13, 5:09 a.m.
Automatically create a workitem and add links to other item by IReferenceFactory. When access the links there is an issue :Error: com.ibm.team.repository.web.transport.ServiceRequest(): invalid requestParameters parameter: [object Object]

With debug=true turned on, get a more detailed message:

Error: com.ibm.team.repository.web.transport.ServiceRequest(): invalid requestParameters parameter: [object Object]
File: https://localhost:9443/ccm/web/com.ibm.team.repository.web/transport.ServiceRequest.js?debug=true&etag=X8JGCv2&_proxyURL=%2Fccm (Line: 215)

Stack:
_validateInput_$9@https://localhost:9443/ccm/web/com.ibm.team.repository.web/transport.ServiceRequest.js?debug=true&etag=X8JGCv2&_proxyURL=%2Fccm:215
constructor_$0@https://localhost:9443/ccm/web/com.ibm.team.repository.web/transport.ServiceRequest.js?debug=true&etag=X8JGCv2&_proxyURL=%2Fccm:66
singleConstructor/<@https://localhost:9443/ccm/web/dojo/dojo.js?debug=true&etag=X7auAq0&_proxyURL=%2Fccm:2845
_invokeWorkItemService_$2@https://localhost:9443/ccm/web/com.ibm.team.workitem.web/client.internal.WorkItemClient.js?debug=true&etag=X7bkSGk&_proxyURL=%2Fccm:126
getHasWorkItemChanged_$12@https://localhost:9443/ccm/web/com.ibm.team.workitem.web/client.internal.WorkItemClient.js?debug=true&etag=X7bkSGk&_proxyURL=%2Fccm:237
_checkHasWorkItemChanged_$99@https://localhost:9443/ccm/web/com.ibm.team.workitem.web/ui.internal.page.WorkItemPageController.js?debug=true&etag=X7bkSGk&_proxyURL=%2Fccm:1666
getCachedWorkItemEditor_$97@https://localhost:9443/ccm/web/com.ibm.team.workitem.web/ui.internal.page.WorkItemPageController.js?debug=true&etag=X7bkSGk&_proxyURL=%2Fccm:1636
showEditorTab_$30@https://localhost:9443/ccm/web/com.ibm.team.workitem.web/ui.internal.page.WorkItemPageView.js?debug=true&etag=X7bkSGk&_proxyURL=%2Fccm:533
viewWorkItem_$87@https://localhost:9443/ccm/web/com.ibm.team.workitem.web/ui.internal.page.WorkItemPageController.js?debug=true&etag=X7bkSGk&_proxyURL=%2Fccm:1533
run_$0@https://localhost:9443/ccm/web/net.jazz.ajax/core.internal.Action.js?debug=true&etag=X7auAKk&_proxyURL=%2Fccm:29
_runAction_$34/<@https://localhost:9443/ccm/web/net.jazz.ajax/ui.Workbench.js?debug=true&etag=X7auAKk&_proxyURL=%2Fccm:630
callContributedCode@https://localhost:9443/ccm/web/net.jazz.ajax/core.internal.util.js?debug=true&etag=X7auAKk&_proxyURL=%2Fccm:26
_runAction_$34@https://localhost:9443/ccm/web/net.jazz.ajax/ui.Workbench.js?debug=true&etag=X7auAKk&_proxyURL=%2Fccm:629
_processActionUri_$27/<@https://localhost:9443/ccm/web/net.jazz.ajax/ui.Workbench.js?debug=true&etag=X7auAKk&_proxyURL=%2Fccm:543
viewPage_$11@https://localhost:9443/ccm/web/net.jazz.ajax/ui.Workbench.js?debug=true&etag=X7auAKk&_proxyURL=%2Fccm:237
_processActionUri_$27@https://localhost:9443/ccm/web/net.jazz.ajax/ui.Workbench.js?debug=true&etag=X7auAKk&_proxyURL=%2Fccm:542
_processUri_$26@https://localhost:9443/ccm/web/net.jazz.ajax/ui.Workbench.js?debug=true&etag=X7auAKk&_proxyURL=%2Fccm:488
method_$53@https://localhost:9443/ccm/web/dojo/dojo.js?debug=true&etag=X7auAq0&_proxyURL=%2Fccm:1962
getDispatcher_$105/<@https://localhost:9443/ccm/web/dojo/dojo.js?debug=true&etag=X7auAq0&_proxyURL=%2Fccm:3553
publish_$114@https://localhost:9443/ccm/web/dojo/dojo.js?debug=true&etag=X7auAq0&_proxyURL=%2Fccm:3800
_dispatchEvent@https://localhost:9443/ccm/web/dojo/hash.js?debug=true&etag=X7auAq0&_proxyURL=%2Fccm:72


Comments
Millard Ellingsworth commented May 14 '13, 7:00 p.m.
FORUM ADMINISTRATOR / JAZZ DEVELOPER

Is this item and its links being created by software you have written? If so, can you say a bit more about how it works and perhaps provide the code for review? If you do the same work item and links creating using an RTC client, does it work correctly?


Debo Xiong commented May 14 '13, 9:53 p.m.

Hi Millard,
Yes it is created by code I have written, both the workitem and the links. Actually the workitem is created successfully no matter the automatic links code exist. If I add the automatic links code the issue appear. But in the workitem view, I am sure the links are created successfully because they are in the Tab Links view, it just can not be clicked. Here is my code for creating links:
    source = IReferenceFactory.INSTANCE.createReferenceFromURI(new URI(url));
    IReference target = refFactory.createReferenceToItem(taskWorkItem);
    ILinkService linkService = getService(ILinkService.class);
    ILinkServiceLibrary linkServiceLibrary = (ILinkServiceLibrary) linkService.getServiceLibrary(ILinkServiceLibrary.class);
    ILink link = linkServiceLibrary.createLink(WPMConstants.LINK_TYPE_OUTPUT, source, target);
    linkServiceLibrary.saveLink(link);
          


Debo Xiong commented May 15 '13, 1:23 a.m. | edited May 15 '13, 1:23 a.m.

PS:  This part works well on RTC 3.0.1.2, now we upgrade to RTC 4.0.2, the issue appear


Debo Xiong commented May 15 '13, 4:56 a.m.

I focused on a Task workitem which had parent, found the code location in firebug:
if(arguments.length==3&&!_10._validateRequestParams(_f)){

throw new Error(_11+": invalid requestParameters parameter: "+_f);
}
Snapshot for parameter _f :
 
undefined is the problem

In targetLinkItemIds.  'undefined' is the problem. _edExxx is the parent's Id. And the xxxoutputlink type is created programmatically.  But I didn't find any method to set the undefined id to a real UUID in Link code, there just two set method exist.
    link.setContextId(UUID.generate());
    link.setRequestedStateId(UUID.generate());

One answer



permanent link
aastha khatri (22619) | answered Mar 07 '17, 2:28 p.m.

I am facing similar kind of issue. Any fix available for this. I am migrating from RTC 5.0.2 to RTC6.0.2. then I see this issue
Thanks!

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.