October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7172) Complex type properties-realm in Elytron subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7172?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7172: ----------------------------- Description: Elytron subsystem uses complex type in properties-realm resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details. *Summary:* Two OBJECTs (USERS_PROPERTIES+GROUPS_PROPERTIES) should be replaced by two simple *_PATH+*_RELATIVE_TO attributes. was:Elytron subsystem uses complex type in properties-realm resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details. > Complex type properties-realm in Elytron subsystem > -------------------------------------------------- > > Key: WFLY-7172 > URL: https://issues.jboss.org/browse/WFLY-7172 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Elytron subsystem uses complex type in properties-realm resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details. > *Summary:* Two OBJECTs (USERS_PROPERTIES+GROUPS_PROPERTIES) should be replaced by two simple *_PATH+*_RELATIVE_TO attributes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7257) Upgrade JGroups to 3.6.11.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7257: ---------------------------------- Summary: Upgrade JGroups to 3.6.11.Final Key: WFLY-7257 URL: https://issues.jboss.org/browse/WFLY-7257 Project: WildFly Issue Type: Component Upgrade Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7258) Upgrade JGroups to 3.6.11.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7258: ---------------------------------- Summary: Upgrade JGroups to 3.6.11.Final Key: WFLY-7258 URL: https://issues.jboss.org/browse/WFLY-7258 Project: WildFly Issue Type: Component Upgrade Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7172) Complex type properties-realm in Elytron subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7172?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-7172: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Complex type properties-realm in Elytron subsystem > -------------------------------------------------- > > Key: WFLY-7172 > URL: https://issues.jboss.org/browse/WFLY-7172 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Elytron subsystem uses complex type in properties-realm resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7256) Configuration differences between default configuration and read/persisted in messaging and IIOP

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7256?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-6279 to WFLY-7256: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7256 (was: JBEAP-6279) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Affects Version/s: 10.1.0.Final (was: 7.0.0.ER6) > Configuration differences between default configuration and read/persisted in messaging and IIOP > ------------------------------------------------------------------------------------------------ > > Key: WFLY-7256 > URL: https://issues.jboss.org/browse/WFLY-7256 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > Following up on JBEAP-3093, there are still differences in these 2 subsystems: > {noformat} > 258a255 > > <orb socket-binding="iiop" ssl-socket-binding="iiop-ssl"/> > 337c334 > < <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/> > --- > > <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/> > 339,341c336,338 > < <address-setting name="#" redistribution-delay="1000" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/> > < <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="http"/> > < <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"> > --- > > <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10" redistribution-delay="1000"/> > > <http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/> > > <http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput"> > 353c350 > < <cluster-connection name="my-cluster" discovery-group="dg-group1" connector-name="http-connector" address="jms"/> > --- > > <cluster-connection name="my-cluster" address="jms" connector-name="http-connector" discovery-group="dg-group1"/> > 356,358c353,355 > < <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/> > < <connection-factory name="RemoteConnectionFactory" reconnect-attempts="-1" block-on-acknowledge="true" ha="true" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/> > < <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/> > --- > > <connection-factory name="InVmConnectionFactory" connectors="in-vm" entries="java:/ConnectionFactory"/> > > <connection-factory name="RemoteConnectionFactory" ha="true" block-on-acknowledge="true" reconnect-attempts="-1" connectors="http-connector" entries="java:jboss/exported/jms/RemoteConnectionFactory"/> > > <pooled-connection-factory name="activemq-ra" transaction="xa" connectors="in-vm" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory"/> > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7256) Configuration differences between default configuration and read/persisted in messaging and IIOP

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7256?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-7256: ------------------------------ Component/s: IIOP JMS > Configuration differences between default configuration and read/persisted in messaging and IIOP > ------------------------------------------------------------------------------------------------ > > Key: WFLY-7256 > URL: https://issues.jboss.org/browse/WFLY-7256 > Project: WildFly > Issue Type: Bug > Components: IIOP, JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > Following up on JBEAP-3093, there are still differences in these 2 subsystems: > {noformat} > 258a255 > > <orb socket-binding="iiop" ssl-socket-binding="iiop-ssl"/> > 337c334 > < <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/> > --- > > <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/> > 339,341c336,338 > < <address-setting name="#" redistribution-delay="1000" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/> > < <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="http"/> > < <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"> > --- > > <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10" redistribution-delay="1000"/> > > <http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/> > > <http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput"> > 353c350 > < <cluster-connection name="my-cluster" discovery-group="dg-group1" connector-name="http-connector" address="jms"/> > --- > > <cluster-connection name="my-cluster" address="jms" connector-name="http-connector" discovery-group="dg-group1"/> > 356,358c353,355 > < <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/> > < <connection-factory name="RemoteConnectionFactory" reconnect-attempts="-1" block-on-acknowledge="true" ha="true" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/> > < <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/> > --- > > <connection-factory name="InVmConnectionFactory" connectors="in-vm" entries="java:/ConnectionFactory"/> > > <connection-factory name="RemoteConnectionFactory" ha="true" block-on-acknowledge="true" reconnect-attempts="-1" connectors="http-connector" entries="java:jboss/exported/jms/RemoteConnectionFactory"/> > > <pooled-connection-factory name="activemq-ra" transaction="xa" connectors="in-vm" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory"/> > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-669) Create "behavesAs" operator to support traiting

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-669?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-669: ------------------------------------------ Fix Version/s: 7.0.0.Beta3 (was: 7.0.0.Beta2) > Create "behavesAs" operator to support traiting > ----------------------------------------------- > > Key: DROOLS-669 > URL: https://issues.jboss.org/browse/DROOLS-669 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.2.0.CR3 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 7.0.0.Beta3 > > > Define an operator that would check if an object can provide *natively* all the methods required by an interface. This would ensure that, upon donning the interface as a trait, no soft field would be required, and that all methods in the interface would have a concrete implementation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-607) Match.getObjects() should reflect the patterns' order

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-607?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-607: ------------------------------------------ Fix Version/s: 7.0.0.Beta3 (was: 7.0.0.Beta2) > Match.getObjects() should reflect the patterns' order > ----------------------------------------------------- > > Key: DROOLS-607 > URL: https://issues.jboss.org/browse/DROOLS-607 > Project: Drools > Issue Type: Enhancement > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.1.0.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > Fix For: 7.0.0.Beta3 > > > if Match.getObjects() is called on a rule with LHS A() B() C(), > the resulting list will have the matching objects in reversed order > - that is, [c, b, a] - making it more difficult to analyze it. > The object's position in the list should reflect the LHS. > The order should be preserved even when subnetworks are present. > For example, A() not B() C() should then result in the list [a, *, c ] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-542) Expose more Commands through the KieCommands API

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-542?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-542: ------------------------------------------ Fix Version/s: 7.0.0.Beta3 (was: 7.0.0.Beta2) > Expose more Commands through the KieCommands API > ------------------------------------------------ > > Key: DROOLS-542 > URL: https://issues.jboss.org/browse/DROOLS-542 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.1.0.CR1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 7.0.0.Beta3 > > > Not all Commands are exposed by the KieCommands API interface -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-470) Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-470?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-470: ------------------------------------------ Fix Version/s: 7.0.0.Beta3 (was: 7.0.0.Beta2) > Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest)) > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-470 > URL: https://issues.jboss.org/browse/DROOLS-470 > Project: Drools > Issue Type: Enhancement > Components: decision tables > Affects Versions: 6.1.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Michael Anstis > Labels: optaplanner-request-for-drools > Fix For: 7.0.0.Beta3 > > > This DT should work: > ||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation(isNeighborOf($guest))|| > |guestName == "$param"|guestName == "$param"|doSomething();| > It crashes because of the "SeatDesignation(isNeighborOf($guest))". Only empty parenthesis are allowed. > Failing workaround 1: This workaround (as specified by the docs), does NOT work well, because it adds the same condition (isNeighborOf($guest)) multiple times in the same rule: > ||CONDITION||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation()||| > |guestName == "$param"|isNeighborOf($guest), guestName == "$param"|isNeighborOf($guest), guestAge == "$param"|doSomething();| > Failing workaround 2: Adding an extra, hidden column with that condition does not work when new rows are added because condition columns with an empty cell are ignored. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

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 2016