August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1660) Temporal operator fails after serialization

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1660?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1660: ------------------------------------- We had a delay, it will be out before the end of this week. > Temporal operator fails after serialization > ------------------------------------------- > > Key: DROOLS-1660 > URL: https://issues.jboss.org/browse/DROOLS-1660 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.0.0.Final > Reporter: Christopher Brecht > Assignee: Mario Fusco > Fix For: 7.2.0.Final > > Attachments: EventA.java, Reproducer.java > > > I attached a reproducer of the problem. If I am executing the rules without serialization everything is working correctly. > If I am executing it with serialization the rules are firing to often. I expect the rule to fire only once. It should fire once at 03:06:00 but it fires 3 times, once at 3:04:00 and 2 times at 3:06:00. > It have to be a problem with serialization of the temporal operators like after,before, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1660) Temporal operator fails after serialization

by Christopher Brecht (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1660?page=com.atlassian.jira.plugi... ] Christopher Brecht commented on DROOLS-1660: -------------------------------------------- Any update for version 7.2.0? When can I expect it? > Temporal operator fails after serialization > ------------------------------------------- > > Key: DROOLS-1660 > URL: https://issues.jboss.org/browse/DROOLS-1660 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.0.0.Final > Reporter: Christopher Brecht > Assignee: Mario Fusco > Fix For: 7.2.0.Final > > Attachments: EventA.java, Reproducer.java > > > I attached a reproducer of the problem. If I am executing the rules without serialization everything is working correctly. > If I am executing it with serialization the rules are firing to often. I expect the rule to fire only once. It should fire once at 03:06:00 but it fires 3 times, once at 3:04:00 and 2 times at 3:06:00. > It have to be a problem with serialization of the temporal operators like after,before, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-155) New Foreman Hostgroups for Fuse

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-155: ----------------------------------------- Summary: New Foreman Hostgroups for Fuse Key: HAWKULARQE-155 URL: https://issues.jboss.org/browse/HAWKULARQE-155 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Michael Foley We need several new foreman hostgroups for Fuse MiQ integration testing. 1. Run JBoss Fuse 6.3 on Karaf container. This is downstream Fuse project running on Karaf container. Install Hawkular Agent on JBoss Fuse. 2. Run Upstream Apache Karaf (downstream of JBoss Fuse) on Karaf container. Install Hawkular Agent on Upstream Apache Karaf. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3170) Upgrade Elytron Web to 1.1.0.CR2

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3170?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-12647 to WFCORE-3170: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3170 (was: JBEAP-12647) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade Elytron Web to 1.1.0.CR2 > -------------------------------- > > Key: WFCORE-3170 > URL: https://issues.jboss.org/browse/WFCORE-3170 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3170) Upgrade Elytron Web to 1.1.0.CR2

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3170?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3170: ------------------------------------- Fix Version/s: 3.0.0.CR1 > Upgrade Elytron Web to 1.1.0.CR2 > -------------------------------- > > Key: WFCORE-3170 > URL: https://issues.jboss.org/browse/WFCORE-3170 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3169) Upgrade WildFly Elytron to 1.1.0.CR5

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3169?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-12645 to WFCORE-3169: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3169 (was: JBEAP-12645) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade WildFly Elytron to 1.1.0.CR5 > ------------------------------------ > > Key: WFCORE-3169 > URL: https://issues.jboss.org/browse/WFCORE-3169 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.CR1 > > > Depending on the fixes merged we may want to include one or more intermediate CR releases during this phase. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3169) Upgrade WildFly Elytron to 1.1.0.CR5

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3169?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3169: ------------------------------------- Fix Version/s: 3.0.0.CR1 > Upgrade WildFly Elytron to 1.1.0.CR5 > ------------------------------------ > > Key: WFCORE-3169 > URL: https://issues.jboss.org/browse/WFCORE-3169 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.CR1 > > > Depending on the fixes merged we may want to include one or more intermediate CR releases during this phase. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-681) Hide private packages from generated javadoc.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-681?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-681: --------------------------------- Fix Version/s: 1.1.0.CR6 (was: 1.1.0.CR5) > Hide private packages from generated javadoc. > --------------------------------------------- > > Key: ELY-681 > URL: https://issues.jboss.org/browse/ELY-681 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.CR6 > > > We may want two profiles so we can generate a full javadoc and a 'public' javadoc. > The 'public' javadoc should be the default one generated and should exclude the following packages: - > org.wildfly.security._private > org.wildfly.security.asn1 > org.wildfly.security.auth.realm > org.wildfly.security.auth.realm.* > org.wildfly.security.authz.jacc > org.wildfly.security.credential.store.impl > org.wildfly.security.security.digest > org.wildfly.security.http.impl > org.wildfly.security.security.keystore > org.wildfly.security.mechanism.oauth2 > org.wildfly.security.mechanism.scram > org.wildfly.security.password.impl > org.wildfly.security.password.util > org.wildfly.security.pem > org.wildfly.security.sasl > org.wildfly.security.sasl.* (Except util) > org.wildfly.security.util > org.wildfly.security.util_private > org.wildfly.security.x500 > org.wildfly.security.x500.cert -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-659) Make all mechanism implementations final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-659?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-659: --------------------------------- Fix Version/s: 1.1.0.CR6 (was: 1.1.0.CR5) > Make all mechanism implementations final > ---------------------------------------- > > Key: ELY-659 > URL: https://issues.jboss.org/browse/ELY-659 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Mechanisms, HTTP, SASL > Reporter: David Lloyd > Priority: Critical > Fix For: 1.1.0.CR6 > > > It is very important to make all the mechanism implementations final. Relatedly, they should have no protected members. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-533) Deprecate all legacy code

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-533?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-533: --------------------------------- Fix Version/s: 1.1.0.CR6 (was: 1.1.0.CR5) > Deprecate all legacy code > ------------------------- > > Key: ELY-533 > URL: https://issues.jboss.org/browse/ELY-533 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.CR6 > > > In a few places we have legacy behaviour within the project to assist migration from previous JBoss / WildFly releases - this code should be flagged as deprecated to encourage minimal use. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 August 2017