General Actions:
Changes for document ConnectorModule
Last modified by Ludovic Dubost on 2012/06/13 11:46
From version 4.2
edited by Ludovic Dubost
on 2012/06/12 21:16
on 2012/06/12 21:16
To version 5.1
edited by Ludovic Dubost
on 2012/06/12 21:28
on 2012/06/12 21:28
Change comment: There is no comment for this version
Content changes
| ... | ... | @@ -21,8 +21,8 @@ |
| 21 | 21 | |
| 22 | 22 | A prototype of this is available for Salesforce and JIRA on the XWiki.org incubator: |
| 23 | 23 | |
| 24 | -* [[Salesforce Prototype>>http://incubator.myxwiki.org/xwiki/bin/view/Mapping/LeadList]]: provides livetable including filters, view, edit and save of Salesforce Leads | |
| 25 | -* [[JIRA Prototype>>http://incubator.myxwiki.org/xwiki/bin/view/Mapping/JiraIssuesList]]: provides livetable (with |
|
| 24 | +* [[Salesforce Prototype>>http://incubator.myxwiki.org/xwiki/bin/view/Mapping/LeadList]]: provides livetable including filters (but no pagination), view, edit and save of Salesforce Leads | |
| 25 | +* [[JIRA Prototype>>http://incubator.myxwiki.org/xwiki/bin/view/Mapping/JiraIssuesList]]: provides livetable (with partial filters and no pagination) and view and edit (but not save) of JIRA Issues from jira.xwiki.org | |
| 26 | 26 | |
| 27 | 27 | This prototpye already shows that the XWiki LiveTable system and Form system can be used to display and navigate data from an external system using SOAP (for Salesforce) or REST (for JIRA). There is no design issue to implement the same system for a database connection or any other remote system. Also both the Salesforce code and the JIRA code implement the same Groovy class, so it is definitively possible to share code in the two systems (livetable and display code). |
| 28 | 28 |