[
https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi...
]
David Hladky commented on JBIDE-19948:
--------------------------------------
The current documentation of the JDF rest service is here
https://mojo.redhat.com/docs/DOC-967368 . Because I failed to explain the JDF service, I
think I should update it to be less difficult to understand. But few notes:
* the current implementation of the
https://www.jboss.org/download-manager/rest/tc rest
service already contains all data. The only reason I wanted to change its format was it
was generated manually and it was not suitable for easy unmarshalling. My thought was to
create an artifact (available on
repository.jboss.org), that would contain the POJOs
annotated with \@XMLRootElement and similar annotations so someone could simply unmarshall
it using Rest Easy for example.
* [~rob.stryker] mentioned, that workflow=rest is not yet used so let us assume links
without it are the old version and with it are the new version (a shortcut to
workflow=rest&version=1). However I do not want any version=2 or higher to be used,
because it requires changes in your system and the reason of the JDF rest service was to
make sure you do not need to implement anything if the sales wants to add/remove some
fields.
* the only place I wanted to have the dynamic fields were in the Accept terms and
conditions step. I wanted the step to remain fairly the same - first the text of the terms
and conditions, but after it instead of *fixed country* I wanted to be either *nothing* or
*fields one under another* (no complicated formatting like two fields in a row or
something like that.). Possible field types:
** edit box
** check box
** drop box (one choice)
** list box (multiple choices)
Reimplement Eclipse Download plugin to allow dynamic work flow
--------------------------------------------------------------
Key: JBIDE-19948
URL:
https://issues.jboss.org/browse/JBIDE-19948
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime-detection, server
Affects Versions: 4.3.0.Alpha2
Reporter: David Hladky
Assignee: Rob Stryker
Fix For: 4.3.0.CR1
We need to reimplement the plugin to accept new terms and conditions models as well as
follow the workflow changes in case of changes to the current ones.
Under this issue I will create the tasks we need to achieve this goal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)