[JBoss JIRA] (WFLY-8984) Fix tests which currently fail with -Dwildfly.tmp.enable.elytron.profile.tests
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-8984?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-8984:
-----------------------------
Affects Version/s: 11.0.0.Alpha1
> Fix tests which currently fail with -Dwildfly.tmp.enable.elytron.profile.tests
> -------------------------------------------------------------------------------
>
> Key: WFLY-8984
> URL: https://issues.jboss.org/browse/WFLY-8984
> Project: WildFly
> Issue Type: Task
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
>
> Several tests fail with -Dwildfly.tmp.enable.elytron.profile.tests=true and -Delytron as seen in
> https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterElytron
> Having a cursory glance at the build log there also appears to be some tests taking about 10 minutes before failing
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
- 1
- 0
[JBoss JIRA] (WFLY-9038) Cluster topology updates are lossy
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-9038:
----------------------------------
Summary: Cluster topology updates are lossy
Key: WFLY-9038
URL: https://issues.jboss.org/browse/WFLY-9038
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Blocker
Fix For: 11.0.0.Beta1
EJB code is not getting a complete cluster topology.
In AssociationImpl, we register cluster topology listeners by adding a {{RegistryCollector.Listener<String, List<ClientMapping>>}}. Because this listener will only receive updates relative to the time it was registered, we also iterate all the values of the original {{RegistryCollector<String, List<ClientMapping>>}} by using its {{getRegistries()}} method at this time.
However, this iteration always seems to come up empty, or else we're missing notifications some other way. So we end up with an incomplete cluster view and client invocations fail because of a perceived lack of node availability.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
- 1
- 0
[JBoss JIRA] (DROOLS-1551) Implement FEEL/DMN value marshaller
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1551?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-1551:
----------------------------------
Sprint: 2017 Week 26-27
> Implement FEEL/DMN value marshaller
> -----------------------------------
>
> Key: DROOLS-1551
> URL: https://issues.jboss.org/browse/DROOLS-1551
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine
> Affects Versions: 7.0.0.CR3
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Priority: Critical
>
> Some value types in FEEL/DMN require special formatting when marshalling/unmarshalling. For instance:
> {quote}
> So it seems that ISO 8601 does not define negative intervals. I.e., ISO 8601 only supports things like "PT1H". XPath extends that with a leading optional sign, like "+PT1H" and "-PT1H". Java extends that allowing the sign to be used in each of the units in the duration like, "PT+1H", "PT-1H", besides the leading sign "-PT1H".
> The FEEL spec on page 113 seems to follow the XPath lexical definition, so the leading sign "-PT1H" seems to be the correct format.
> {quote}
> Implement an object marshaller for DMN/FEEL that is capable of marshalling/unmarshalling objects. Most object types are straightforward, but a few of them (like durations) need special handling. In particular:
> * negative duration should use a leading - sign instead of having the sign in the unit numbers
> * durations need to be normalized before marshalled:
> {quote}
> A days and time duration in the semantic domain is a sequence of numbers for the days, hours, minutes, and seconds of duration, normalized such that the sum of these numbers is minimized.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
- 1
- 0