October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9422) Wildfly HTTP client 1.0.6.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9422?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-9422: --------------------------------- Summary: Wildfly HTTP client 1.0.6.Final (was: Wildfly HTTP client 1.0.5.Final) > Wildfly HTTP client 1.0.6.Final > ------------------------------- > > Key: WFLY-9422 > URL: https://issues.jboss.org/browse/WFLY-9422 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9422) Wildfly HTTP client 1.0.5.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9422?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-13399 to WFLY-9422: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9422 (was: JBEAP-13399) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > Wildfly HTTP client 1.0.5.Final > ------------------------------- > > Key: WFLY-9422 > URL: https://issues.jboss.org/browse/WFLY-9422 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3342) Upgrade JBoss Remoting to 5.0.3.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3342: ----------------------------------- Summary: Upgrade JBoss Remoting to 5.0.3.Final Key: WFCORE-3342 URL: https://issues.jboss.org/browse/WFCORE-3342 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.5.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3341) Upgrade XNIO to 3.5.2.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3341: ----------------------------------- Summary: Upgrade XNIO to 3.5.2.Final Key: WFCORE-3341 URL: https://issues.jboss.org/browse/WFCORE-3341 Project: WildFly Core Issue Type: Component Upgrade Components: IO Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.5.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3340) Upgrade JBoss Marshalling to 2.0.2.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3340: ----------------------------------- Summary: Upgrade JBoss Marshalling to 2.0.2.Final Key: WFCORE-3340 URL: https://issues.jboss.org/browse/WFCORE-3340 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.5.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1751) NullPointerException on org.mvel2.MVEL.executeExpression()

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1751?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1751: -------------------------------- Sprint: 2017 Week 40-41 > NullPointerException on org.mvel2.MVEL.executeExpression() > ---------------------------------------------------------- > > Key: DROOLS-1751 > URL: https://issues.jboss.org/browse/DROOLS-1751 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.3.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Labels: support > > Under the conditions: > - 2 KiePackages with the same package name but different rules > - Those packages are used by a kbase so "inUse = true" > - Create another kbase and call kbase.addPackages() for those packages > MVELDialectRuntimeData has a problem in merging mvelReaders so later rule execution fails with NullPointerException. > {noformat} > java.lang.NullPointerException: null > at org.mvel2.MVEL.executeExpression(MVEL.java:953) > at org.drools.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:506) > at org.drools.core.base.extractors.MVELObjectClassFieldReader.getValue(MVELObjectClassFieldReader.java:140) > at org.drools.core.rule.Declaration.getValue(Declaration.java:222) > at org.drools.core.base.mvel.MVELCompilationUnit.updateFactory(MVELCompilationUnit.java:386) > at org.drools.core.base.mvel.MVELCompilationUnit.getFactory(MVELCompilationUnit.java:320) > at org.drools.core.base.dataproviders.MVELDataProvider.evaluate(MVELDataProvider.java:137) > at org.drools.core.base.dataproviders.MVELDataProvider.getResults(MVELDataProvider.java:133) > at org.drools.core.phreak.PhreakFromNode.doLeftInserts(PhreakFromNode.java:106) > at org.drools.core.phreak.PhreakFromNode.doNode(PhreakFromNode.java:68) > at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:387) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:333) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169) > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127) > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87) > at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34) > at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067) > at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1320) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1311) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1295) > at org.drools.compiler.integrationtests.Misc2Test.testMergeMVELDialect(Misc2Test.java:9109) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1388) Clean up credential-store-type in schema

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1388: ------------------------------------- Summary: Clean up credential-store-type in schema Key: ELY-1388 URL: https://issues.jboss.org/browse/ELY-1388 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Affects Versions: 1.2.0.Beta4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 The credential store type contains the following definition: - {code} <xsd:complexType name="credential-store-type"> <xsd:annotation> <xsd:documentation> An individual credential store definition. </xsd:documentation> </xsd:annotation> <xsd:all minOccurs="0" maxOccurs="1"> <xsd:element name="attributes" type="attributes-type"/> <xsd:element name="protection-parameter-credentials" type="client-credentials-type"/> <xsd:element name="providers" type="providers-type" /> </xsd:all> <xsd:attribute name="name" type="xsd:string" use="required" /> <xsd:attribute name="type" type="xsd:string" default="KeyStoreCredentialStore" use="optional"> <xsd:annotation> <xsd:documentation> The credential store type, e.g. KeyStoreCredentialStore. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="provider" type="xsd:string" use="optional"> <xsd:annotation> <xsd:documentation> The name of the provider to use to instantiate the CredentialStoreSpi, if the provider is not specified then the first provider found that can create an instance of the specified 'type' will be used. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:complexType> {code} This effectively says the child elements are optional but if one is specified they all need to be specified, however they are all optional and can be specified individually. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1387) SSLContext for where authentication client resources load from a resource.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1387: ------------------------------------- Summary: SSLContext for where authentication client resources load from a resource. Key: ELY-1387 URL: https://issues.jboss.org/browse/ELY-1387 Project: WildFly Elytron Issue Type: Enhancement Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 Where resources can be loaded from a URI we may want to define an SSLContext for access to that resource so we can verify it is a trusted resource. i.e. our local config contains internal key and trust stores but the remove destinations may change so we load the certificates and revocation lists from an internal trusted source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1386) <certificate-revocation-list /> should also support a URI and resource in addition to path.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1386: ------------------------------------- Summary: <certificate-revocation-list /> should also support a URI and resource in addition to path. Key: ELY-1386 URL: https://issues.jboss.org/browse/ELY-1386 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 KeyStores can be loaded from a path, a URI, or as a resource - the certificate revocation list should be the same. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1385) Add option to override the KeyManager and TrustManager within <authentication-client />

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1385: ------------------------------------- Summary: Add option to override the KeyManager and TrustManager within <authentication-client /> Key: ELY-1385 URL: https://issues.jboss.org/browse/ELY-1385 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 At the moment we can reference an alias from a KeyStore and reference a complete KeyStore for use by the TrustManager but there is not option to override which key and trust managers are actually enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017