[JBoss JIRA] (SRAMPUI-96) Remember the selected filter criteria when navigating the UI
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMPUI-96?page=com.atlassian.jira.plugin... ]
Eric Wittmann resolved SRAMPUI-96.
----------------------------------
Resolution: Done
> Remember the selected filter criteria when navigating the UI
> ------------------------------------------------------------
>
> Key: SRAMPUI-96
> URL: https://issues.jboss.org/browse/SRAMPUI-96
> Project: S-RAMP UI
> Issue Type: Enhancement
> Components: View
> Affects Versions: 0.3.0
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1
>
>
> The Artifacts page allows the user to select a number of filters to narrow down the list of artifacts being viewed. However, these options are lost when the user navigates to another page and then back again. We should remember the user's filter settings as long as they stay within the s-ramp application (or perhaps beyond by storing something in browser state?).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (SRAMP-251) Improve XSLT in overlord commons installer
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-251:
-----------------------------------
Summary: Improve XSLT in overlord commons installer
Key: SRAMP-251
URL: https://issues.jboss.org/browse/SRAMP-251
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 0.3.0 - JBPM6 Integration
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.3.1 - jBPM - bugfix 1
The current overlord commons installer XSLT used to add security domains to jboss eap/wildfly has an ambiguous element declaration. When adding the security domain, the xslt has this:
{code}
<security-domains>
<security-domain />
</security-domains>
{code}
Because the XSLT doesn't declare a default namespace, this is problematic depending on the processor used. Instead, the XSLT should be explicit about the QNames used in any element it creates.
Note that the XSLT is currently designed to work with both EAP and Wildfly, which have different namespaces for the element being created. So we'll likely need multiple templates for multiple versions of the "as" namespace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months