[JBoss JIRA] (WFCORE-4303) NullPointerException - with SNI configured on IBM JDK 1.8
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-4303?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved WFLY-11663 to WFCORE-4303:
-------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-4303 (was: WFLY-11663)
Component/s: Security
(was: Security)
(was: Web (Undertow))
Affects Version/s: (was: 15.0.1.Final)
> NullPointerException - with SNI configured on IBM JDK 1.8
> ---------------------------------------------------------
>
> Key: WFCORE-4303
> URL: https://issues.jboss.org/browse/WFCORE-4303
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Environment: IBM JDK 1.8:
> {code}
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 8.0.5.20 - pxa6480sr5fp20-20180802_01(SR5 FP20))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180731_393394 (JIT enabled, AOT enabled)
> OpenJ9 - bd23af8
> OMR - ca1411c
> IBM - 98805ca)
> JCL - 20180719_01 based on Oracle jdk8u181-b12
> {code}
> Reporter: Jan Stourac
> Assignee: Darran Lofthouse
> Priority: Major
>
> When running with IBM JDK 1.8, there is an NPE during the request performed against https-listener which has configured 'server-ssl-sni-context' instance (when using standard 'server-ssl-context' no exception is present):
> {code}
> $ curl https://localhost:8443 -k
> curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8443
> {code}
> related exception in server.log:
> {code}
> 18:23:01,227 ERROR [io.undertow.request.io] (default I/O-6) UT005090: Unexpected failure: java.lang.NullPointerException
> at io.undertow.protocols.ssl.SslConduit.doUnwrap(SslConduit.java:772)
> at io.undertow.protocols.ssl.SslConduit.read(SslConduit.java:567)
> at org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127)
> at io.undertow.server.protocol.http.AlpnOpenListener$AlpnConnectionListener.handleEvent(AlpnOpenListener.java:348)
> at io.undertow.server.protocol.http.AlpnOpenListener.handleEvent(AlpnOpenListener.java:305)
> at io.undertow.server.protocol.http.AlpnOpenListener.handleEvent(AlpnOpenListener.java:64)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:131)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> {code}
> When I switch to OpenSSL provider using
> {code}
> /subsystem=elytron/server-ssl-context=defaultSSC:write-attribute(name=providers,value=openssl)
> {code}
> then the exception disappears.
> ----
> Note: sometimes I can also see shorter exception stacktrace:
> {code}
> 18:17:15,711 ERROR [io.undertow.request.io] (default I/O-2) UT005090: Unexpected failure: java.lang.NullPointerException
> at io.undertow.protocols.ssl.SslConduit.doUnwrap(SslConduit.java:772)
> at io.undertow.protocols.ssl.SslConduit.doHandshake(SslConduit.java:648)
> at io.undertow.protocols.ssl.SslConduit.access$900(SslConduit.java:63)
> at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1136)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (DROOLS-3566) Contextual menus for canvas nodes - imported.
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3566?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3566:
----------------------------------------
[~uxdlc] I like it.
This I assume is _one_ way of managing nodes within a DRD (e.g. also drag nodes from the DRD to a DRG in the "Decision Navigator" etc).
> Contextual menus for canvas nodes - imported.
> ----------------------------------------------
>
> Key: DROOLS-3566
> URL: https://issues.jboss.org/browse/DROOLS-3566
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UXTeam, drools-tools
> Attachments: contextual-menu.png
>
>
> Canvas node actions related to imported components.
> As a user I want to easily select and group nodes on the canvas so that I can add them to a DRD or to create a new DRD.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (WFLY-10319) NameBinding annotations on resources are ignored in subresources
by Javier Estevez Sanchez (Jira)
[ https://issues.jboss.org/browse/WFLY-10319?page=com.atlassian.jira.plugin... ]
Javier Estevez Sanchez commented on WFLY-10319:
-----------------------------------------------
[~ron_sigal], [~mkopecky]
I agree with you on this one. I think the spec is the source of confusion here (not all _methods of a resource_ (e.g. sub-resource locators) being _resource methods_). Maybe another name like _resource operations_ would make it less confusing. I will report this to the jaxrs-spec group.
Thanks for your support,
Javier
> NameBinding annotations on resources are ignored in subresources
> ----------------------------------------------------------------
>
> Key: WFLY-10319
> URL: https://issues.jboss.org/browse/WFLY-10319
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 12.0.0.Final
> Reporter: Javier Estevez Sanchez
> Assignee: Alessio Soldano
> Priority: Major
>
> The following JAX-RS resource exposes two resources via a GET operation: /demo and /demo/subresource. The first one via a sub-resource method, the latter via a sub-resource locator. Additionally, a response filter is binded to the JAX-RS resource class to modify the response. From the JAX-RS 2.0 spec, §6.5.2 Name Binding:
> {quote}
> Binding annotations that decorate resource classes apply to all resource methods defined in them.
> {quote}
> However, the binding annotation is not applying to the sub-resource locator method. This happens when the name binding annotation is on the resource class or on the sub-resource locator method. Annotating the sub-resource class or the method within works as expected, though.
> Below is the code needed to reproduce this issue:
> {code:java|title=The resource and subresource}
> @DemoNameBinding
> @Produces(MediaType.APPLICATION_JSON)
> @Path("/demo")
> public class DemoResource {
> @GET
> public String getDemoValue() {
> return "A value";
> }
> @Path("/subresource")
> public DemoSubResource getSubResource() {
> return new DemoSubResource();
> }
> public class DemoSubResource {
> @GET
> public String getDemoValue() {
> return "A value";
> }
> }
> }
> {code}
> {code:java|title=The filter}
> @Provider
> @DemoNameBinding
> public class SomeFilter implements ContainerResponseFilter {
> @Override
> public void filter(ContainerRequestContext requestContext, ContainerResponseContext responseContext) {
> responseContext.setEntity("A filtered value");
> }
> }
> {code}
> {code:java|title=The binding}
> @NameBinding
> @Target({ElementType.TYPE, ElementType.METHOD})
> @Retention(RetentionPolicy.RUNTIME)
> public @interface DemoNameBinding {
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3420:
---------------------------------
Description:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# The field *Choose DMN asset* should be marked with *{color:red}*{color}* (required field). -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
was:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# The fields *Package*, *Source type*, and *Choose DMN asset* should be marked with *{color:red}*{color}* (required fields). -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
> -------------------------------------------------------------------
>
> Key: DROOLS-3420
> URL: https://issues.jboss.org/browse/DROOLS-3420
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Minor
>
> SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
> Later, ask [~Rikkola] to move it on upper framework.
> *ADDITIONAL IMPROVEMENTS:*
> # When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # Change *Choose DMN asset* to *Choose a DMN asset*.
> # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
> # The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # The field *Choose DMN asset* should be marked with *{color:red}*{color}* (required field). -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3420:
---------------------------------
Description:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# The fields *Package*, *Source type*, and *Choose DMN asset* should be marked with *{color:red}*{color}* (required fields). -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
was:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# The fields *Package*, *Source type*, and *Choose DMN asset* should be marked with *{color:red}*{color}* (required fields).
> Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
> -------------------------------------------------------------------
>
> Key: DROOLS-3420
> URL: https://issues.jboss.org/browse/DROOLS-3420
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Minor
>
> SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
> Later, ask [~Rikkola] to move it on upper framework.
> *ADDITIONAL IMPROVEMENTS:*
> # When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # Change *Choose DMN asset* to *Choose a DMN asset*.
> # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
> # The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # The fields *Package*, *Source type*, and *Choose DMN asset* should be marked with *{color:red}*{color}* (required fields). -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3021:
-------------------------------------
[~karreiro] I tried to use enumerations with comma inside and they are parsed differently between reopening.
h2. Before saving
!Screenshot from 2019-02-01 08-54-00.png|thumbnail!
h2. After saving
!Screenshot from 2019-02-01 08-55-19.png|thumbnail!
Used asset: [^enums.dmn]
> [DMN Designer] Data Types - Constraints - Enumeration component
> ---------------------------------------------------------------
>
> Key: DROOLS-3021
> URL: https://issues.jboss.org/browse/DROOLS-3021
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-02-01 08-54-00.png, Screenshot from 2019-02-01 08-55-19.png, enums.dmn, future.png, prototype.png
>
>
> - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded;
> !prototype.png|thumbnail!
> - The component contains a dynamic list to insert the possible values
> - The input is a simple input without any validation
> This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}):
> !future.png|thumbnail!
> ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3420:
---------------------------------
Description:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# The fields *Package*, *Source type*, and *Choose DMN asset* should be marked with *{color:red}*{color}* (required fields).
was:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.
> Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
> -------------------------------------------------------------------
>
> Key: DROOLS-3420
> URL: https://issues.jboss.org/browse/DROOLS-3420
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Minor
>
> SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
> Later, ask [~Rikkola] to move it on upper framework.
> *ADDITIONAL IMPROVEMENTS:*
> # When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # Change *Choose DMN asset* to *Choose a DMN asset*.
> # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
> # The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # The fields *Package*, *Source type*, and *Choose DMN asset* should be marked with *{color:red}*{color}* (required fields).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months