[ https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19948: ------------------------------------- [~dhladky] I think there's probably just a small communication gap here, and I think you should continue with your work on the server side. We will still need a call to discuss the details, but for now, the 100% most important things to note are: 1) Current behavior must NOT CHANGE if no version flag is passed in. 2) Item 1) must be unit tested to guarantee that there are no changes. The unit tests must be thorough, testing all aspects of current non-versioned behavior, including status codes, return values, returned xml form and structure, as well as its behavior when different request headers are passed in. Once those unit tests are created, I have absolutely no problem with you continuing development work with a version=2 being passed in via parameter or request header. As for the UI, the general agreement we had (as I recall) is that once you've got a provisional version=2 that's workable, I would *then* design a UI based on the 100% unchanging responses that I know you're generating. Version 2 would then also be extensively unit tested to guarantee that it will also remain unchanging afterwards. I think I was just confused by your suggestion of me making 9 different UIs, because in my head, designing the UI was to be performed AFTER the core communication was complete, and would be based on version 2 of the request/response being unchanging. For me to design such a UI before I know what version 2 of the request/response looks like would be a little bit backwards. -- This message was sent by Atlassian JIRA (v6.3.15#6346)