Hi Malaka, On Mon, May 26, 2014 at 3:04 AM, Malaka Silva <[email protected]> wrote:
> Check the way it's done for salesforce. (Creating records) > > https://docs.wso2.org/display/ESB481/Salesforce+Connector > > Thank you for the info. I will follow that. As I see the required parameters are given through a <payloadFactory>. > Also make this type mails available to public as well. > > Noted. Thanks. Added dev@ so others can refer for similar issues.. Thanks. On Sun, May 25, 2014 at 3:35 PM, Malintha Amarasinghe <[email protected]>wrote: > >> Hi Malaka, >> >> I have currently completed the integration testing on the methods I newly >> added to the existing jira connector which are: >> >> Group related: >> -addUserToGroup >> -createGroup >> -deleteGroup >> -getAllGroups >> -getGroupUsers >> -removeUserFromGroup >> >> User Related: >> -createUser >> -deleteUser >> -getUserGroups >> >> Project Related: >> -addGroupToProjectRole >> -removeGroupFromProjectRole >> -getAllProjects >> -addUserToProjectRole >> -removeUserFromProjectRole >> >> >> You suggested me on the last code review to further improve some of the >> existing methods such as createIssue[1] which currently supports only 4 >> parameters. >> >> I have currently encounted a problem with[1] where it has some parameters >> like "components" where user can add a array of ids of components. >> >> "components": [ >> { >> "id": "10000" >> } >> ], >> >> >> So I initially thought this should be implemented such a way that this >> can used through the synapse config like this: >> >> <jira.createIssue> >> <projectKey>WIDGET20</projectKey> >> <summary>Update 2.0 license agreement file</summary> >> <description>description</description> >> <issueType>Bug</issueType> >> >> .... >> >> *<components> >> <id>10000</id> >> <id>10002</id> >> </components>* >> >> .... >> >> </jira.createIssue> >> >> >> But the problem is when I save such a config in ESB(4.8.1) it removes the >> inner childs of the *<components> *and becomes .... >> >> <jira.createIssue> >> <projectKey>WIDGET20</projectKey> >> <summary>Update 2.0 license agreement file</summary> >> <description>description</description> >> <issueType>Bug</issueType> >> >> .... >> >> *<components/>* >> >> .... >> >> </jira.createIssue> >> >> Doesn't ESB currently support those types of parameters? Anyway I can use >> a different way like the following. >> >> <jira.createIssue> >> <projectKey>WIDGET20</projectKey> >> <summary>Update 2.0 license agreement file</summary> >> <description>description</description> >> <issueType>Bug</issueType> >> >> .... >> >> *<components>* >> >> >> * { "id":"10000" }, >> { "id":"10002" }* >> >> * </components>* >> >> .... >> >> </jira.createIssue> >> >> This works but it may not be a good way since it uses json inside xml. >> >> Is the above way OK or otherwise can you please give me any suggestions >> to solve this? >> >> [1] https://docs.atlassian.com/software/jira/docs/api/REST/latest/#d2e961 >> >> Thank you. >> Regards, >> Malintha >> Engneering Intern >> > > > > -- > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > http://www.wso2.com/about/team/malaka-silva/<http://wso2.com/about/team/malaka-silva/> > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
