[JBoss JIRA] (DROOLS-2397) PMML modules have classloader issues in OSGi
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-2397?page=com.atlassian.jira.plug... ]
Gabriele Cardosi closed DROOLS-2397.
------------------------------------
Resolution: Won't Fix
Invalid with new PMML implementation
> PMML modules have classloader issues in OSGi
> --------------------------------------------
>
> Key: DROOLS-2397
> URL: https://issues.redhat.com/browse/DROOLS-2397
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.6.0.Final
> Environment: Equinox OSGi container, Java 8
> Reporter: Jens Reimann
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: drools-core
>
> The drools PMML modules (drools-pmml and kie-pmml) both suffer from a few class loader issues when running inside an OSGi container.
> The KieBase built for transforming the PMML model to Drools model selects the wrong class loader (based on the context class loader). The JAXB instance creator fails with the same problem.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-2397) PMML modules have classloader issues in OSGi
by Jiri Petrlik (Jira)
[ https://issues.redhat.com/browse/DROOLS-2397?page=com.atlassian.jira.plug... ]
Jiri Petrlik reassigned DROOLS-2397:
------------------------------------
Assignee: Gabriele Cardosi (was: Edson Tirelli)
> PMML modules have classloader issues in OSGi
> --------------------------------------------
>
> Key: DROOLS-2397
> URL: https://issues.redhat.com/browse/DROOLS-2397
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.6.0.Final
> Environment: Equinox OSGi container, Java 8
> Reporter: Jens Reimann
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: drools-core
>
> The drools PMML modules (drools-pmml and kie-pmml) both suffer from a few class loader issues when running inside an OSGi container.
> The KieBase built for transforming the PMML model to Drools model selects the wrong class loader (based on the context class loader). The JAXB instance creator fails with the same problem.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4840) Support for multiple security realms - Distributed Identities
by Martin Mazánek (Jira)
Martin Mazánek created WFCORE-4840:
--------------------------------------
Summary: Support for multiple security realms - Distributed Identities
Key: WFCORE-4840
URL: https://issues.redhat.com/browse/WFCORE-4840
Project: WildFly Core
Issue Type: Feature Request
Components: Security
Reporter: Martin Mazánek
Assignee: Martin Mazánek
By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list.
This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together.
Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged.
This RFE is not about fail over in the event of a realm being unavailable although it may be related.
This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ELY-1932) Support for multiple security realms - Distributed Identities
by Martin Mazánek (Jira)
[ https://issues.redhat.com/browse/ELY-1932?page=com.atlassian.jira.plugin.... ]
Martin Mazánek moved WFCORE-4840 to ELY-1932:
---------------------------------------------
Project: WildFly Elytron (was: WildFly Core)
Key: ELY-1932 (was: WFCORE-4840)
Component/s: (was: Security)
> Support for multiple security realms - Distributed Identities
> -------------------------------------------------------------
>
> Key: ELY-1932
> URL: https://issues.redhat.com/browse/ELY-1932
> Project: WildFly Elytron
> Issue Type: Feature Request
> Reporter: Martin Mazánek
> Assignee: Martin Mazánek
> Priority: Major
> Labels: CD17-Deferred, EAP-CD19, Previous_RFE
>
> By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list.
> This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together.
> Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged.
> This RFE is not about fail over in the event of a realm being unavailable although it may be related.
> This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4485) Support for multiple security realms - Distributed Identities
by Martin Mazánek (Jira)
[ https://issues.redhat.com/browse/WFCORE-4485?page=com.atlassian.jira.plug... ]
Martin Mazánek reassigned WFCORE-4485:
--------------------------------------
Assignee: Martin Mazánek
> Support for multiple security realms - Distributed Identities
> -------------------------------------------------------------
>
> Key: WFCORE-4485
> URL: https://issues.redhat.com/browse/WFCORE-4485
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Martin Mazánek
> Priority: Major
> Labels: CD17-Deferred, EAP-CD19, Previous_RFE
>
> By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list.
> This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together.
> Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged.
> This RFE is not about fail over in the event of a realm being unavailable although it may be related.
> This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months