May 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-468) Don't inject call trace service in Situations provider to avoid issues in Karaf

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-468?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-468: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/90 > Don't inject call trace service in Situations provider to avoid issues in Karaf > ------------------------------------------------------------------------------- > > Key: RTGOV-468 > URL: https://issues.jboss.org/browse/RTGOV-468 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > As weld is packaged in rtgov-ui, the situations provider attempts to inject the call trace service. As it is not packaged inside the war, this causes problems. > It is better to have it as a separate OSGi service and just instantiate an implementation. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-468) Don't inject call trace service in Situations provider to avoid issues in Karaf

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-468?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-468. ------------------------------ Resolution: Done > Don't inject call trace service in Situations provider to avoid issues in Karaf > ------------------------------------------------------------------------------- > > Key: RTGOV-468 > URL: https://issues.jboss.org/browse/RTGOV-468 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > As weld is packaged in rtgov-ui, the situations provider attempts to inject the call trace service. As it is not packaged inside the war, this causes problems. > It is better to have it as a separate OSGi service and just instantiate an implementation. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-439) Add support for exclusive classifiers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-439?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-439: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1099908 > 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: 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

1
0
0 / 0

[JBoss JIRA] (SRAMP-439) Add support for exclusive classifiers

by Anton Giertli (JIRA)

Anton Giertli created SRAMP-439: ----------------------------------- Summary: 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: 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

1
0
0 / 0

[JBoss JIRA] (RTGOV-468) Don't inject call trace service in Situations provider to avoid issues in Karaf

by Gary Brown (JIRA)

Gary Brown created RTGOV-468: -------------------------------- Summary: Don't inject call trace service in Situations provider to avoid issues in Karaf Key: RTGOV-468 URL: https://issues.jboss.org/browse/RTGOV-468 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final As weld is packaged in rtgov-ui, the situations provider attempts to inject the call trace service. As it is not packaged inside the war, this causes problems. It is better to have it as a separate OSGi service and just instantiate an implementation. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-423) Enable SRAMP to be deployed to fabric as a profile

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-423: --------------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/69, https://github.com/Governance/s-ramp/pull/421 (was: https://github.com/Governance/overlord-commons/pull/69) > Enable SRAMP to be deployed to fabric as a profile > -------------------------------------------------- > > Key: SRAMP-423 > URL: https://issues.jboss.org/browse/SRAMP-423 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Enable SRAMP to be deployed to fabric as a profile. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-423) Enable SRAMP to be deployed to fabric as a profile

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-423: --------------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/69 > Enable SRAMP to be deployed to fabric as a profile > -------------------------------------------------- > > Key: SRAMP-423 > URL: https://issues.jboss.org/browse/SRAMP-423 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Enable SRAMP to be deployed to fabric as a profile. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-464) Create profiles for 'rtgov-all' and 'rtgov-client' features

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/RTGOV-464?page=com.atlassian.jira.plugin.... ] Work on RTGOV-464 started by David virgil naranjo. > Create profiles for 'rtgov-all' and 'rtgov-client' features > ----------------------------------------------------------- > > Key: RTGOV-464 > URL: https://issues.jboss.org/browse/RTGOV-464 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 2.0.0.Final > > Original Estimate: 4 days > Remaining Estimate: 4 days > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-423) Enable SRAMP to be deployed to fabric as a profile

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.... ] Work on SRAMP-423 started by David virgil naranjo. > Enable SRAMP to be deployed to fabric as a profile > -------------------------------------------------- > > Key: SRAMP-423 > URL: https://issues.jboss.org/browse/SRAMP-423 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Enable SRAMP to be deployed to fabric as a profile. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-429) Move jetty login-realm config from s-ramp installer to overlord-commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-429: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/68, https://github.com/Governance/s-ramp/pull/420 (was: https://github.com/Governance/overlord-commons/pull/68) > Move jetty login-realm config from s-ramp installer to overlord-commons installer > --------------------------------------------------------------------------------- > > Key: SRAMP-429 > URL: https://issues.jboss.org/browse/SRAMP-429 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Currently we simply replace the jetty.xml in the s-ramp installer for jetty8. Instead we should transform the existing one to add what we want. The s-ramp installer should add the s-ramp datasource. The overlord-commons installer should add the idp realm. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2014