[JBoss JIRA] (DROOLS-1644) Create/document basic requirements
by Lance Leverich (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1644?page=com.atlassian.jira.plugi... ]
Lance Leverich updated DROOLS-1644:
-----------------------------------
Description: This task is a placeholder to gather up the requirements for creating the ability to use PMML files as resources. Initial thoughts and feedback will be expressed in the comments below, with the end results being a documented set of objectives/goals.
> Create/document basic requirements
> ----------------------------------
>
> Key: DROOLS-1644
> URL: https://issues.jboss.org/browse/DROOLS-1644
> Project: Drools
> Issue Type: Sub-task
> Reporter: Lance Leverich
> Assignee: Lance Leverich
>
> This task is a placeholder to gather up the requirements for creating the ability to use PMML files as resources. Initial thoughts and feedback will be expressed in the comments below, with the end results being a documented set of objectives/goals.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[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:
----------------------------------
Priority: Critical (was: Major)
> 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)
7 years, 4 months
[JBoss JIRA] (WFLY-9037) Cluster topology updates are lossy
by David Lloyd (JIRA)
David Lloyd created WFLY-9037:
---------------------------------
Summary: Cluster topology updates are lossy
Key: WFLY-9037
URL: https://issues.jboss.org/browse/WFLY-9037
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: David Lloyd
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)
7 years, 4 months
[JBoss JIRA] (WFLY-9002) RemoteFailoverTestCase.testSecureStatelessFailover fails due to authorization
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-9002?page=com.atlassian.jira.plugin.... ]
David Lloyd reassigned WFLY-9002:
---------------------------------
Assignee: David Lloyd
> RemoteFailoverTestCase.testSecureStatelessFailover fails due to authorization
> -----------------------------------------------------------------------------
>
> Key: WFLY-9002
> URL: https://issues.jboss.org/browse/WFLY-9002
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: David Lloyd
> Assignee: David Lloyd
> Priority: Critical
>
> On the server, the authentication information seems OK. PicketBox is rejecting authorization, probably due to some change in Elytron integration.
> The stack trace looks like this:
> {noformat}
> 2017-06-26 21:45:30 testSecureStatelessFailover(org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase) Time elapsed: 5.765 sec <<< ERROR!
> 2017-06-26 21:45:30 javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract org.jboss.as.test.clustering.cluster.ejb.remote.bean.Result org.jboss.as.test.clustering.cluster.ejb.remote.bean.Incrementor.increment() of bean: SecureStatelessIncrementorBean is not allowed
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:134)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:57)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:256)
> 2017-06-26 21:45:30 at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609)
> 2017-06-26 21:45:30 at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
> 2017-06-26 21:45:30 at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> 2017-06-26 21:45:30 at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> 2017-06-26 21:45:30 at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> 2017-06-26 21:45:30 at org.wildfly.security.auth.server.SecurityIdentity.runAsFunctionEx(SecurityIdentity.java:380)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.remote.AssociationImpl.invokeWithIdentity(AssociationImpl.java:480)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.remote.AssociationImpl.invokeMethod(AssociationImpl.java:475)
> 2017-06-26 21:45:30 at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:183)
> 2017-06-26 21:45:30 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 2017-06-26 21:45:30 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 2017-06-26 21:45:30 at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months