[JBoss JIRA] (RTGOV-619) RTGov UI: Assign button does not cause the UI to move to the next state
by Gary Brown (JIRA)
Gary Brown created RTGOV-619:
--------------------------------
Summary: RTGov UI: Assign button does not cause the UI to move to the next state
Key: RTGOV-619
URL: https://issues.jboss.org/browse/RTGOV-619
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
When a situation is assigned, it causes the user to be recorded in the 'assignedTo' property of the situation in the backend, but the UI no longer updates to reflect this new property in the situation, or change the range of buttons available on the page.
Even if the page is refreshed, it just shows the additional 'assignedTo' property, but still displays the 'Assign' button.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (RTGOV-617) RTGov UI: No message content displayed
by Gary Brown (JIRA)
Gary Brown created RTGOV-617:
--------------------------------
Summary: RTGov UI: No message content displayed
Key: RTGOV-617
URL: https://issues.jboss.org/browse/RTGOV-617
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
When selecting a situation, on the details page, the Message tab should show the content - however it is blank.
The bean returned via the REST service has the content (as an XML message) - not sure if this is causing an issue when returned in the JSON response, when deserialized in the browser.
To reproduce,
a) deploy the quickstarts from the top samples folder: mvn jboss-as:deploy
b) go to the ordermgnt/app folder and run "mvn exec:java -Dreq=order3"
This will create a couple of situations, select the one related to the promoted OrderService (rather than the internal InventoryService).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (RTGOV-616) RTGov UI: application list no longer displayed
by Gary Brown (JIRA)
Gary Brown created RTGOV-616:
--------------------------------
Summary: RTGov UI: application list no longer displayed
Key: RTGOV-616
URL: https://issues.jboss.org/browse/RTGOV-616
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
Since RTGOV-610, the service list page's application list (combo) is no longer populated, although the REST service does provide the information.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (RTGOV-614) Reinstate security context for RTGov UI backend services
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-614?page=com.atlassian.jira.plugin.... ]
Gary Brown closed RTGOV-614.
----------------------------
Fix Version/s: (was: 2.1.0.Final)
Resolution: Rejected
Not an issue - SecurityContext can be injected in the service impl rather than on the method signature.
> Reinstate security context for RTGov UI backend services
> --------------------------------------------------------
>
> Key: RTGOV-614
> URL: https://issues.jboss.org/browse/RTGOV-614
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
>
> As part of moving from Errai RPC services to JAX-RS services (RTGOV-610), security context (identifying the user principal) has been disabled, as this was provided via the Errai bus at the backend.
> Adding SecurityContext to the REST services causes issues with the RTGov UI, as the same interface is used by the GWT/Errai client.
> One workaround would be to have two versions of the service interface, one pure and the other with the @Context SecurityContext parameter in the relevant methods. However this is not ideal. Need to see whether there is any other standard way to get the SecurityContext, and if not, consider whether using a filter may provide a better solution.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (RTGOV-614) Reinstate security context for RTGov UI backend services
by Gary Brown (JIRA)
Gary Brown created RTGOV-614:
--------------------------------
Summary: Reinstate security context for RTGov UI backend services
Key: RTGOV-614
URL: https://issues.jboss.org/browse/RTGOV-614
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
As part of moving from Errai RPC services to JAX-RS services (RTGOV-610), security context (identifying the user principal) has been disabled, as this was provided via the Errai bus at the backend.
Adding SecurityContext to the REST services causes issues with the RTGov UI, as the same interface is used by the GWT/Errai client.
One workaround would be to have two versions of the service interface, one pure and the other with the @Context SecurityContext parameter in the relevant methods. However this is not ideal. Need to see whether there is any other standard way to get the SecurityContext, and if not, consider whether using a filter may provide a better solution.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (SRAMP-604) Show relationships targeting the current artifact in the UI
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-604?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-604:
-----------------------------------
The queries in https://developer.jboss.org/thread/250121 should help
> Show relationships targeting the current artifact in the UI
> -----------------------------------------------------------
>
> Key: SRAMP-604
> URL: https://issues.jboss.org/browse/SRAMP-604
> Project: S-RAMP
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Great idea from [~eric.wittmann] on an email thread:
> {quote}
> I also think there is room in the UI for some way to show all artifacts
> that point to the current artifact by a specific relationship. So
> perhaps an editable drop-down control allowing the user to select a
> common relationship or type their own, which would result in this query:
> /s-ramp/<model>/<type>[<relationship>[@uuid = <uuid>]]
> The <model>, <type>, and <uuid> values come from the currently selected
> artifact. The <relationship> comes from the dropdown. Populate a table
> with the results!
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month