October 2017 - jboss-jira - Jboss List Archives

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

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1388?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1388: ---------------------------------- Fix Version/s: 1.2.0.Beta6 (was: 1.2.0.Beta5) > 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.Beta6 > > > 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, 9 months

1
0
0 / 0

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

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1387?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1387: ---------------------------------- Fix Version/s: 1.2.0.Beta6 (was: 1.2.0.Beta5) > 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.Beta6 > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1390) Release WildFly Elytron 1.2.0.Beta5

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1390?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1390. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.2.0.Beta5 > ----------------------------------- > > Key: ELY-1390 > URL: https://issues.jboss.org/browse/ELY-1390 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta5 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1389) Release WildFly Elytron 1.1.4.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1389?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1389. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.4.Final > ----------------------------------- > > Key: ELY-1389 > URL: https://issues.jboss.org/browse/ELY-1389 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.4.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1752) substring after(“foobar”,”x”) returns “foobar” but should return “”

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1752?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1752: ---------------------------------- Sprint: 2017 Week 40-41 > substring after(“foobar”,”x”) returns “foobar” but should return “” > ------------------------------------------------------------------- > > Key: DROOLS-1752 > URL: https://issues.jboss.org/browse/DROOLS-1752 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.3.0.Final > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.4.0.Final > > > substring after(“foobar”,”x”) returns “foobar” but should return “” -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1753) replace("0123456789", "(\d{3})(\d{3})(\d{4})", "($1) $2-$3") raises a parsing exception

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1753?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1753: ---------------------------------- Sprint: 2017 Week 40-41 > replace("0123456789","(\d{3})(\d{3})(\d{4})","($1) $2-$3") raises a parsing exception > --------------------------------------------------------------------------------------- > > Key: DROOLS-1753 > URL: https://issues.jboss.org/browse/DROOLS-1753 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.3.0.Final > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.4.0.Final > > > replace("0123456789","(\d{3})(\d{3})(\d{4})","($1) $2-$3") raises a parsing exception -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1753) replace("0123456789", "(\d{3})(\d{3})(\d{4})", "($1) $2-$3") raises a parsing exception

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1753: ------------------------------------- Summary: replace("0123456789","(\d{3})(\d{3})(\d{4})","($1) $2-$3") raises a parsing exception Key: DROOLS-1753 URL: https://issues.jboss.org/browse/DROOLS-1753 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.3.0.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.4.0.Final replace("0123456789","(\d{3})(\d{3})(\d{4})","($1) $2-$3") raises a parsing exception -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1752) substring after(“foobar”,”x”) returns “foobar” but should return “”

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1752: ------------------------------------- Summary: substring after(“foobar”,”x”) returns “foobar” but should return “” Key: DROOLS-1752 URL: https://issues.jboss.org/browse/DROOLS-1752 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.3.0.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.4.0.Final substring after(“foobar”,”x”) returns “foobar” but should return “” -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9353) system property to set cluster name

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9353?page=com.atlassian.jira.plugin.... ] Paul Ferraro edited comment on WFLY-9353 at 10/6/17 6:46 PM: ------------------------------------------------------------- [~bmaxwell] The cluster name can be manipulated via the JGroups channel resource. e.g. {code:xml} <channel name="ee" stack="..." cluster="${jboss.cluster.name}"/> {code} Is this insufficient? was (Author: pferraro): [~bmaxwell] The cluster name can be manipulated via the Infinispan transport. e.g. {code:xml} <cache-container name="ejb"> <transport cluster="${jboss.cluster.name}-ejb"/> </cache-container> {code} Is this insufficient? > system property to set cluster name > ----------------------------------- > > Key: WFLY-9353 > URL: https://issues.jboss.org/browse/WFLY-9353 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Brad Maxwell > Assignee: Paul Ferraro > > The cluster name is basically always server/web/ejb/hibernate/... as shown below. It would be useful to define a system property substitution in the standard configs to make it easy to set for instances where multiple clusters are needed. > Something like ${jboss.cluster.name:}-ejb or ${jboss.partition.name:DefaultPartition} would make it clear what the cluster name is and how to change it. > {code} > <cache-container name="ejb" aliases="sfsb" default-cache="dist" module="org.wildfly.clustering.ejb.infinispan"> > <transport lock-timeout="60000" cluster="${jboss.cluster.name:}-ejb"/> > {code} > {code} > <subsystem xmlns="urn:jboss:domain:infinispan:4.0"> > <cache-container name="server" aliases="singleton cluster" default-cache="default" module="org.wildfly.clustering.server"> > <transport lock-timeout="60000"/> > ... > <cache-container name="web" default-cache="dist" module="org.wildfly.clustering.web.infinispan"> > <transport lock-timeout="60000"/> > ... > <cache-container name="ejb" aliases="sfsb" default-cache="dist" module="org.wildfly.clustering.ejb.infinispan"> > <transport lock-timeout="60000"/> > ... > <cache-container name="hibernate" default-cache="local-query" module="org.hibernate.infinispan"> > <transport lock-timeout="60000"/> > ... > </subsystem> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3347) add-content operation of deployment resource contains alternative attributes that doesn't exist

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3347?page=com.atlassian.jira.plugi... ] Claudio Miranda updated WFCORE-3347: ------------------------------------ Description: add-content operation contains "content" attribute, {code} /deployment=*:read-operation-description(name=add-content) {code} "content" attribute it is a list of other attributes as: input-stream-index, hash, bytes, url. They themselves contains the alternatives metadata as {code} "url" => { "type" => STRING, "description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).", "expressions-allowed" => false, "required" => false, "nillable" => true, "alternatives" => [ "input-stream-index", "hash", "bytes", "path", "relative-to", "empty" ], "min-length" => 1L, "max-length" => 2147483647L }, {code} But the following attributes doesn't exist: path, relative-to, empty was: add-content operation contains "content" attribute, {code} /deployment=*:read-operation-description(name=add-content) {code} "content" attribute it is a list of other attributes, they themselves contains the alternatives metadata as {code} "alternatives" => [ "hash", "bytes", "url", "path", "relative-to", "empty" ], {code} But the following attributes doesn't exist: path, relative-to, empty > add-content operation of deployment resource contains alternative attributes that doesn't exist > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-3347 > URL: https://issues.jboss.org/browse/WFCORE-3347 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Brian Stansberry > Priority: Minor > > add-content operation contains "content" attribute, > {code} > /deployment=*:read-operation-description(name=add-content) > {code} > "content" attribute it is a list of other attributes as: input-stream-index, hash, bytes, url. They themselves contains the alternatives metadata as > {code} > "url" => { > "type" => STRING, > "description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "alternatives" => [ > "input-stream-index", > "hash", > "bytes", > "path", > "relative-to", > "empty" > ], > "min-length" => 1L, > "max-length" => 2147483647L > }, > {code} > But the following attributes doesn't exist: path, relative-to, empty -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017