[JBoss JIRA] (RTGOV-381) Switchyard event listener component in Karaf
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-381?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-381.
------------------------------
Resolution: Done
Integration has been implemented, but cannot properly be tested currently as drools uses a newer version of quartz than swyd (and newer than defined in the IP BOM), which causes the swyd example to no longer work.
> Switchyard event listener component in Karaf
> --------------------------------------------
>
> Key: RTGOV-381
> URL: https://issues.jboss.org/browse/RTGOV-381
> Project: RTGov (Run Time Governance)
> Issue Type: Sub-task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> When switchyard is supported on Karaf, provide a component that registers with the switchyard event manager to report activity events to RTGov.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (SRAMP-440) Add a final redirect filter to overlord SPs
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-440:
-----------------------------------
Summary: Add a final redirect filter to overlord SPs
Key: SRAMP-440
URL: https://issues.jboss.org/browse/SRAMP-440
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: UI
Reporter: Eric Wittmann
Assignee: Brett Meyer
Fix For: 0.5.0.Final
The IDP (when running in tomcat, jetty, fuse) causes the browser to do a POST of the SAML assertion to the SP (e.g. s-ramp-ui). This POST is consumed by the SPFilter and the assertion is consumed. At this point the user is authenticated and the UI is loaded.
However, if the user then tries to refresh the page, the browser will likely ask if the user wishes to Resend data.
To avoid this problem we should have a filter that does a final redirect (only after a POST to the SPFilter) so that the browser finishes up with a GET request to the UI rather than a POST.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (SRAMP-439) Add support for exclusive classifiers
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-439?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-439:
-------------------------------------
My initial thought here is that as long as we support OWL related features in the UI and not in the repository itself, we shouldn't have any spec-compliance issues. We might consider implementing at least a sensible subset of the OWL Lite and OWL specifications as UI features.
> Add support for exclusive classifiers
> -------------------------------------
>
> Key: SRAMP-439
> URL: https://issues.jboss.org/browse/SRAMP-439
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core, Governance, UI
> Reporter: Anton Giertli
> Assignee: Brett Meyer
> Priority: Optional
>
> The requested feature talks about possibility to make some Classifiers exclusive. Imagine class Gender and two subclasses Male and Female, defined in the ontology.
> If it was possible to make these classifiers exclusive, it would be possible, via S-RAMP UI to set only *one* of those.
> i.e. user can't set Male if Female is set.
> i.e. user can't set Female is Male is set.
> OWL Language should be capable of creating such constructs by using owl:disjointWith attribute
> http://www.w3.org/TR/owl-guide/#owl_disjointWith
> However, this attribute is part of OWL DL and not OWL Lite which is currently used.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (SRAMP-439) Add support for exclusive classifiers
by Anton Giertli (JIRA)
[ https://issues.jboss.org/browse/SRAMP-439?page=com.atlassian.jira.plugin.... ]
Anton Giertli updated SRAMP-439:
--------------------------------
Component/s: Core
Governance
Affects: Documentation (Ref Guide, User Guide, etc.),Compatibility/Configuration,User Experience
Forum Reference: https://community.jboss.org/thread/241284
> Add support for exclusive classifiers
> -------------------------------------
>
> Key: SRAMP-439
> URL: https://issues.jboss.org/browse/SRAMP-439
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core, Governance, UI
> Reporter: Anton Giertli
> Assignee: Brett Meyer
> Priority: Optional
>
> The requested feature talks about possibility to make some Classifiers exclusive. Imagine class Gender and two subclasses Male and Female, defined in the ontology.
> If it was possible to make these classifiers exclusive, it would be possible, via S-RAMP UI to set only *one* of those.
> i.e. user can't set Male if Female is set.
> i.e. user can't set Female is Male is set.
> OWL Language should be capable of creating such constructs by using owl:disjointWith attribute
> http://www.w3.org/TR/owl-guide/#owl_disjointWith
> However, this attribute is part of OWL DL and not OWL Lite which is currently used.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months