[JBoss JIRA] (DROOLS-3453) Data type constraints: Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3453?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3453:
--------------------------------
Attachment: (was: enumeration1.png)
> Data type constraints: Time
> ---------------------------
>
> Key: DROOLS-3453
> URL: https://issues.jboss.org/browse/DROOLS-3453
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration2.png, range3.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Time (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3453) Data type constraints: Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3453?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3453:
--------------------------------
Attachment: enumeration2.png
range3.png
> Data type constraints: Time
> ---------------------------
>
> Key: DROOLS-3453
> URL: https://issues.jboss.org/browse/DROOLS-3453
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration1.png, enumeration2.png, range1.png, range2.png, range3.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Time (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-3452:
------------------------------------------
[~uxdlc] I like it, assuming it's on 24-hour system for optimal accessibility. Thanks.
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration-question.png, enumerationB.png, enumerationC.png, revised-range2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3452:
--------------------------------
Attachment: enumerationC.png
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration-question.png, enumerationB.png, enumerationC.png, revised-range2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3452:
-------------------------------------
[~stetson.robinson][~karreiro] I went ahead and updated to natural language, if the formatting needs tweaks please let me know. Thanks!
!enumerationC.png|thumbnail!
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration-question.png, enumerationB.png, enumerationC.png, revised-range2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3452:
-------------------------------------
Thanks [~stetson.robinson], I believe the file will use the ISO/XML... formatting on the backend, but I think we can use natural language for the ui. [~karreiro] Wdyt?
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration-question.png, enumerationB.png, revised-range2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-11663) NullPointerException - with SNI configured on IBM JDK 1.8
by Jan Stourac (Jira)
Jan Stourac created WFLY-11663:
----------------------------------
Summary: NullPointerException - with SNI configured on IBM JDK 1.8
Key: WFLY-11663
URL: https://issues.jboss.org/browse/WFLY-11663
Project: WildFly
Issue Type: Bug
Components: Security, Web (Undertow)
Affects Versions: 15.0.1.Final
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
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)
6 years, 10 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Stetson Robinson edited comment on DROOLS-3452 at 1/31/19 12:29 PM:
--------------------------------------------------------------------
If that's the DMN syntax requirement, then I guess we need to keep it. If it's not and it's up to us, then definitely natural language, in the format "31 Jan 2019, 14:00:00+02:00:00" or whatever. If having spaces and punctuation is a problem, then the compromised style recommendation is "31Jan2019T14:00:00+02:00:00", assuming seconds are used.
was (Author: stetson.robinson):
If that's the DMN syntax requirement, then I guess we need to keep it. If it's not and it's up to us, then definitely natural language, in the format "31 Jan 2019, 14:00:00+02:00:00" or whatever. If having spaces and punctuation is a problem, then the style recommendation is "31Jan2019T14:00:00+02:00:00", assuming seconds are used.
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration-question.png, enumerationB.png, revised-range2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-3452:
------------------------------------------
If that's the DMN syntax requirement, then I guess we need to keep it. If it's not and it's up to us, then definitely natural language, in the format "31 Jan 2019, 14:00:00+02:00:00" or whatever. If having spaces and punctuation is a problem, then the style recommendation is "31Jan2019T14:00:00+02:00:00", assuming seconds are used.
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration-question.png, enumerationB.png, revised-range2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3452:
--------------------------------
Attachment: enumeration-question.png
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration-question.png, enumerationB.png, revised-range2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months