[jbosstools-issues] [JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244778#comment-13244778 ] 

Fred Bricon edited comment on JBIDE-22459 at 5/30/16 9:38 AM:
--------------------------------------------------------------

[~lkrzyzanek] the sys_type parameter we can change without any issue, as long as it yields the same results. I honestly don't remember how I came up with the hack version (either I was told, saw it used elsewhere or figured it out myself).

The output format is definitely, absolutely not the same as in v1, as most fields are returned as arrays instead of simple values, this definitely breaks our parsing in JBDS 9 (and 10 currently). If the output could be the exact same as v1, then we could switch over to v2 without sweating. We'd only lose the help search feature eventually.

As for the  result limit set to 500, this is to allow us to perform only 1 query, do the appropriate processing on the results and present them to the user. Filtering in Central doesn't do any round trips to the server. The search is cached for offline use. Search is performed every time Central is opened (which is *usually* once every time you open Eclipse). We can add more identifying parameters to the search query if you need, to help you log usage.


was (Author: fbricon):
[~lkrzyzanek] the sys_type parameter we can change without any issue, as long as it yields the same results. I honestly don't remember how I came up with the hack version (either I was told, saw it used elsewhere or figured it out myself).

The output format is definitely, absolutely not the same as in v1, as most fields are returned as arrays instead of simple values, this definitely breaks our parsing in JBDS 9 (and 10 currently). If the output could be the exact same as v1, then we could switch over to v2 without sweating. We'd only loose the help search feature eventually.

As for the  result limit set to 500, this is to allow us to perform only 1 query, do the appropriate processing on the results and present them to the user. Filtering in Central doesn't do any round trips to the server. The search is cached for offline use. Search is performed every time Central is opened (which is *usually* once every time you open Eclipse). We can add more identifying parameters to the search query if you need, to help you log usage.

> Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central
> -------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22459
>                 URL: https://issues.jboss.org/browse/JBIDE-22459
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: central
>            Reporter: Max Rydahl Andersen
>            Assignee: Fred Bricon
>            Priority: Blocker
>
> ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats.
> In the context of EAP 7 coming out there are new quickstarts.
> In a perfect world the following have happend:
> EAP 7 Quickstarts added to DCP
> Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts
> What seem to have happened instead is:
> if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available
> DCP has changed its format/approach and not sure what the impact of this is
>  (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?)
> This bug is to gather the facts and figure out what we do about them.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)