[JBoss JIRA] (DROOLS-4118) [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4118?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4118:
--------------------------------
Description:
This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
h2. Acceptance test
Firefox and Chrome
- Multiple data types
- Data types with constraints
- List data types
- Connected nodes
- Separated nodes
- Nodes exceeding canvas size
- Fonts, Colors
Linux/Windows
- Download and open
was:
This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
h2. Acceptance test
Firefox and Chrome
- Multiple data types
- Data types with constraints
- List data types
- Connected nodes
- Separated nodes
- Nodes exceeding canvas size
Linux/Windows
- Download and open
> [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4118
> URL: https://issues.jboss.org/browse/DROOLS-4118
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
> This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
> This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
> h2. Acceptance test
> Firefox and Chrome
> - Multiple data types
> - Data types with constraints
> - List data types
> - Connected nodes
> - Separated nodes
> - Nodes exceeding canvas size
> - Fonts, Colors
> Linux/Windows
> - Download and open
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4118) [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4118?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4118:
--------------------------------
Description:
This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
h2. Acceptance test
Firefox and Chrome
- Multiple data types
- Data types with constraints
- List data types
- Connected nodes
- Separated nodes
- Nodes exceeding canvas size
Linux/Windows
- Download and open
was:
This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
h2. Acceptance test
Firefox and Chrome
- Multiple data types
- Data types with constraints
- List data types
- Connected nodes
- Separated nodes
- Nodes exceeding canvas size
> [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4118
> URL: https://issues.jboss.org/browse/DROOLS-4118
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
> This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
> This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
> h2. Acceptance test
> Firefox and Chrome
> - Multiple data types
> - Data types with constraints
> - List data types
> - Connected nodes
> - Separated nodes
> - Nodes exceeding canvas size
> Linux/Windows
> - Download and open
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4118) [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4118?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4118:
--------------------------------
Description:
This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
h2. Acceptance test
Firefox and Chrome
- Multiple data types
- Data types with constraints
- List data types
- Connected nodes
- Separated nodes
- Nodes exceeding canvas size
was:
This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
h2. Acceptance test
- Multiple data types
- Data types with constraints
- List data types
- Connected nodes
- Separated nodes
- Nodes exceeding canvas size
> [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4118
> URL: https://issues.jboss.org/browse/DROOLS-4118
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
> This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
> This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
> h2. Acceptance test
> Firefox and Chrome
> - Multiple data types
> - Data types with constraints
> - List data types
> - Connected nodes
> - Separated nodes
> - Nodes exceeding canvas size
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4118) [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4118?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4118:
--------------------------------
Description:
This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
h2. Acceptance test
- Multiple data types
- Data types with constraints
- List data types
- Connected nodes
- Separated nodes
- Nodes exceeding canvas size
was:
This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
> [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4118
> URL: https://issues.jboss.org/browse/DROOLS-4118
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
> This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
> This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
> h2. Acceptance test
> - Multiple data types
> - Data types with constraints
> - List data types
> - Connected nodes
> - Separated nodes
> - Nodes exceeding canvas size
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4117) [DMN Designer] Documentation tab - Simple Stunner infrastructure setup
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4117?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4117:
--------------------------------
Description:
This initial setup aims to show the documentation tab with some static content (using Mustache template).
Implementation of the {{DocumentationView}}, and a simple DMN version of the {{DiagramDocumentationService}}.
h2. Acceptance test
Firefox and Chrome
- Content differs if multiple diagrams opened
- BPMN not affected
was:
This initial setup aims to show the documentation tab with some static content (using Mustache template).
Implementation of the {{DocumentationView}}, and a simple DMN version of the {{DiagramDocumentationService}}.
h2. Acceptance test
- Content differs if multiple diagrams opened
- BPMN not affected
> [DMN Designer] Documentation tab - Simple Stunner infrastructure setup
> ----------------------------------------------------------------------
>
> Key: DROOLS-4117
> URL: https://issues.jboss.org/browse/DROOLS-4117
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> This initial setup aims to show the documentation tab with some static content (using Mustache template).
> Implementation of the {{DocumentationView}}, and a simple DMN version of the {{DiagramDocumentationService}}.
> h2. Acceptance test
> Firefox and Chrome
> - Content differs if multiple diagrams opened
> - BPMN not affected
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4117) [DMN Designer] Documentation tab - Simple Stunner infrastructure setup
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4117?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4117:
--------------------------------
Description:
This initial setup aims to show the documentation tab with some static content (using Mustache template).
Implementation of the {{DocumentationView}}, and a simple DMN version of the {{DiagramDocumentationService}}.
h2. Acceptance test
- Content differs if multiple diagrams opened
- BPMN not affected
was:
This initial setup aims to show the documentation tab with some static content (using Mustache template).
Implementation of the {{DocumentationView}}, and a simple DMN version of the {{DiagramDocumentationService}}.
> [DMN Designer] Documentation tab - Simple Stunner infrastructure setup
> ----------------------------------------------------------------------
>
> Key: DROOLS-4117
> URL: https://issues.jboss.org/browse/DROOLS-4117
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> This initial setup aims to show the documentation tab with some static content (using Mustache template).
> Implementation of the {{DocumentationView}}, and a simple DMN version of the {{DiagramDocumentationService}}.
> h2. Acceptance test
> - Content differs if multiple diagrams opened
> - BPMN not affected
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-3964) EJBAccessException is not returned to remote client
by Panagiotis Sotiropoulos (Jira)
[ https://issues.jboss.org/browse/WFLY-3964?page=com.atlassian.jira.plugin.... ]
Panagiotis Sotiropoulos closed WFLY-3964.
-----------------------------------------
Resolution: Out of Date
> EJBAccessException is not returned to remote client
> ---------------------------------------------------
>
> Key: WFLY-3964
> URL: https://issues.jboss.org/browse/WFLY-3964
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Reporter: Dirk Weil
> Assignee: Panagiotis Sotiropoulos
> Priority: Major
>
> When calling an EJB method with access restrictions via @RolesAllowed from a remote client with unsufficient user priveledges, an EJBAccessException should be returned to the remote caller. WildFly returns a java.io.StreamCorruptedException instead.
> Stacktrace on client:
> {code}
> java.io.StreamCorruptedException: Unexpected byte found when reading an object: 0
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:236)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)
> at com.sun.proxy.$Proxy6.restrictedMethod(Unknown Source)
> at de.gedoplan.beantrial.wildflyejbremote.DemoTest.testRestrictedMethod(DemoTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: java.io.StreamCorruptedException: Unexpected byte found when reading an object: 0
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:751)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.jboss.ejb.client.remoting.ProtocolMessageHandler.readAttachments(ProtocolMessageHandler.java:55)
> at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:82)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:276)
> at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocationResult(EJBObjectInterceptor.java:64)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocationResult(EJBHomeInterceptor.java:88)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:46)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocationResult(ReceiverInterceptor.java:129)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:265)
> at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:453)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:202)
> ... 30 more
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:865)
> at org.junit.Assert.assertThat(Assert.java:832)
> at org.junit.rules.ExpectedException.handleException(ExpectedException.java:198)
> at org.junit.rules.ExpectedException.access$500(ExpectedException.java:85)
> at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:177)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-3964) EJBAccessException is not returned to remote client
by Panagiotis Sotiropoulos (Jira)
[ https://issues.jboss.org/browse/WFLY-3964?page=com.atlassian.jira.plugin.... ]
Panagiotis Sotiropoulos commented on WFLY-3964:
-----------------------------------------------
Also with 17.0.0.Final :
[INFO] Running de.gedoplan.beantrial.wildflyejbremote.DemoTest
Jun 13, 2019 10:39:13 AM org.jboss.naming.remote.client.InitialContextFactory <clinit>
INFO: WFNAM00025: org.jboss.naming.remote.client.InitialContextFactory is deprecated; new applications should use org.wildfly.naming.client.WildFlyInitialContextFactory instead
Jun 13, 2019 10:39:13 AM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.10.Final
Jun 13, 2019 10:39:13 AM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.9.1.Final
Jun 13, 2019 10:39:13 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.7.2.Final
Jun 13, 2019 10:39:13 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.7.2.Final
Jun 13, 2019 10:39:13 AM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.3.Final
Jun 13, 2019 10:39:13 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.12.Final
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.796 s - in de.gedoplan.beantrial.wildflyejbremote.DemoTest
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Closing this issue
> EJBAccessException is not returned to remote client
> ---------------------------------------------------
>
> Key: WFLY-3964
> URL: https://issues.jboss.org/browse/WFLY-3964
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Reporter: Dirk Weil
> Assignee: Panagiotis Sotiropoulos
> Priority: Major
>
> When calling an EJB method with access restrictions via @RolesAllowed from a remote client with unsufficient user priveledges, an EJBAccessException should be returned to the remote caller. WildFly returns a java.io.StreamCorruptedException instead.
> Stacktrace on client:
> {code}
> java.io.StreamCorruptedException: Unexpected byte found when reading an object: 0
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:236)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)
> at com.sun.proxy.$Proxy6.restrictedMethod(Unknown Source)
> at de.gedoplan.beantrial.wildflyejbremote.DemoTest.testRestrictedMethod(DemoTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: java.io.StreamCorruptedException: Unexpected byte found when reading an object: 0
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:751)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.jboss.ejb.client.remoting.ProtocolMessageHandler.readAttachments(ProtocolMessageHandler.java:55)
> at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:82)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:276)
> at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocationResult(EJBObjectInterceptor.java:64)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocationResult(EJBHomeInterceptor.java:88)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:46)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocationResult(ReceiverInterceptor.java:129)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:265)
> at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:453)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:202)
> ... 30 more
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:865)
> at org.junit.Assert.assertThat(Assert.java:832)
> at org.junit.rules.ExpectedException.handleException(ExpectedException.java:198)
> at org.junit.rules.ExpectedException.access$500(ExpectedException.java:85)
> at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:177)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4172) rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-4172:
------------------------------------
Summary: rule filtering by folder-type packages attribute does not work after upgrading to 7.11.0.Final
Key: DROOLS-4172
URL: https://issues.jboss.org/browse/DROOLS-4172
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.11.0.Final, 7.14.0.Final, 7.18.0.Final
Reporter: Hiroko Miura
Assignee: Mario Fusco
Attachments: buildKjarTest.zip
In kjar project, there are many rules per folder under resources directory and
filtered these rules by using packages attribute in kmodule.xml.
e.g.
- file structure
{noformat}
src/main/resources/
├── logback-test.xml
├── META-INF
│ ├── kmodule.xml
│ └── maven
│ └── pom.properties
└── rules
├── aws
│ └── Sample1.drl
├── test1
│ └── Sample1.drl
└── test2
└── Sample2.drl
{noformat}
- kmodule.xml
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
<kbase name="rules" packages="rules.aws">
<ksession name="ksession-rules"/>
</kbase>
</kmodule>
{noformat}
This could be built with library version 7.5.0.Final.
But after upgrading 7.11.0.Final or later, it fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4485) Support for multiple security realms - Distributed Identities
by Lumir Navrat (Jira)
[ https://issues.jboss.org/browse/WFCORE-4485?page=com.atlassian.jira.plugi... ]
Lumir Navrat edited comment on WFCORE-4485 at 6/13/19 4:29 AM:
---------------------------------------------------------------
Our use case is this:
Eclipse RCP remote thick client that connect to WF server.
1. during connect from rcp client to WF input username and password.
2. on server is now Elytron intermediate configuration that pass ot to JAAS. Where is configured our custom WinCoreLoginModule with sufficent and standard JDBC server login module. with sufficent too.
When user isn't authenticated in WinCoreModule than it is tried if exists in database. Our WinCoreModule allow authenticate user to the windows credentional store located on computer where server is running. In case when WF is instaled on same machine as thick client => clients computer.
I'm not sure if real mapper is usable in our use case. Because username is in same format for both login modules.
>From developer view. On client is used:
{code}
AuthenticationConfiguration authenticationConfiguration = AuthenticationConfiguration.empty()
.useName(login)
.usePassword(password);
AuthenticationContext authenticationContext = AuthenticationContext.empty()
.with(MatchRule.ALL.matchHost(host), authenticationConfiguration);
AuthenticationContext.getContextManager().setGlobalDefault(authenticationContext);
{code} and we catch exception and investigate if there is Authentication or Sasl exception and inform user about wrong credentionals or other connectivity problems.
was (Author: lnavrat):
Our use case is this:
Eclipse RCP remote thick client that connect to WF server.
1. during connect to WF input username and password.
2. on server is now Elytron intermediate configuration that pass ot to JAAS. Where is configured our custom WinCoreLoginModule with sufficent and standard JDBC server login module. with sufficent too.
When user isn't authenticated in WinCoreModule than it is tried if exists in database. Our WinCoreModule allow authenticate user to the windows credentional store located on computer where server is running. In case when WF is instaled on same machine as thick client => clients computer.
I'm not sure if real mapper is usable in our use case. Because username is in same format for both login modules.
> Support for multiple security realms - Distributed Identities
> -------------------------------------------------------------
>
> Key: WFCORE-4485
> URL: https://issues.jboss.org/browse/WFCORE-4485
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Priority: Major
> Labels: CD17-Deferred, EAP-CD19, Previous_RFE
> Fix For: 11.0.0.Beta1
>
>
> By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list.
> This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together.
> Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged.
> This RFE is not about fail over in the event of a realm being unavailable although it may be related.
> This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month