[JBoss JIRA] (DROOLS-3803) Build error with executable-model, nested property with double-bytes property name
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-3803:
------------------------------------
Summary: Build error with executable-model, nested property with double-bytes property name
Key: DROOLS-3803
URL: https://issues.jboss.org/browse/DROOLS-3803
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.18.0.Final
Environment: 7.18.0.Final
7.18.0.Final-redhat-00002 (RHDM7.3.0)
7.14.0.Final-redhat-00004 (RHDM7.1.2)
Reporter: Hiroko Miura
Assignee: Luca Molteni
Attachments: NestedPropertyTest.zip
Build of Executable Model fails with the following conditions in LHS:
* multi-bytes property name (or started with capital letter)
* accessing the property by the name without using getter.
* accessing nested property by `.`
e.g.
{noformat}
when
$fact : Fact( 住所.zipCode == "1000001")
...
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3802) Build error with executable-model, nested property with double-bytes property name
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-3802?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-3802:
---------------------------------
Description:
Build of Executable Model fails with the following conditions in LHS:
* multi-bytes property name (or started with capital letter)
* accessing the property by the name without using getter.
* accessing nested property by `.`
e.g.
{noformat}
when
$fact : Fact( 住所.zipCode == "1000001")
...
{noformat}
was:
Build of Executable Model fails with the following conditions in LHS:
* multi-bytes property name (or started with capital letter)
* accessing the property by the name without using getter.
* accessing nested property by `.`
e.g.
{noformat}
when
$fact : Fact( 住所 .zipCode == "1000001")
...
{noformat}
> Build error with executable-model, nested property with double-bytes property name
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-3802
> URL: https://issues.jboss.org/browse/DROOLS-3802
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.18.0.Final
> Environment: 7.18.0.Final
> 7.18.0.Final-redhat-00002 (RHDM7.3.0)
> 7.14.0.Final-redhat-00004 (RHDM7.1.2)
> Reporter: Hiroko Miura
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
> Attachments: NestedPropertyTest.zip
>
>
> Build of Executable Model fails with the following conditions in LHS:
> * multi-bytes property name (or started with capital letter)
> * accessing the property by the name without using getter.
> * accessing nested property by `.`
> e.g.
> {noformat}
> when
> $fact : Fact( 住所.zipCode == "1000001")
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3802) Build error with executable-model, nested property with double-bytes property name
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-3802:
------------------------------------
Summary: Build error with executable-model, nested property with double-bytes property name
Key: DROOLS-3802
URL: https://issues.jboss.org/browse/DROOLS-3802
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.18.0.Final
Environment: 7.18.0.Final
7.18.0.Final-redhat-00002 (RHDM7.3.0)
7.14.0.Final-redhat-00004 (RHDM7.1.2)
Reporter: Hiroko Miura
Assignee: Luca Molteni
Attachments: NestedPropertyTest.zip
Build of Executable Model fails with the following conditions in LHS:
* multi-bytes property name (or started with capital letter)
* accessing the property by the name without using getter.
* accessing nested property by `.`
e.g.
{noformat}
when
$fact : Fact( 住所 .zipCode == "1000001")
...
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3800) Parser error with executable-model on Map literal expression in constraint
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-3800?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-3800:
---------------------------------
Summary: Parser error with executable-model on Map literal expression in constraint (was: Parser error with executable-model on Map literal expression in costraint)
> Parser error with executable-model on Map literal expression in constraint
> --------------------------------------------------------------------------
>
> Key: DROOLS-3800
> URL: https://issues.jboss.org/browse/DROOLS-3800
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.18.0.Final
> Environment: 7.18.0.Final
> 7.18.0.Final-redhat-00002 (RHDM7.3.0)
> 7.14.0.Final-redhat-00004 (RHDM7.1.2)
> Reporter: Hiroko Miura
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
> Attachments: MapLiteralTest.zip
>
>
> When MAP literal expression is used in LHS like the following
> {noformat}
> when
> $fact: Fact(
> calc(["src":name, "target":"TEST"])
> )
> ...
> {noformat}
> KieBase build as Executable Model fails with parser error like:
> {noformat}
> org.drools.javaparser.ParseProblemException:
> Encountered unexpected token: "[" "["
> at line 1, column 6.
> Was expecting one of:
> ")"
> {noformat}
> This error does not happen when building this rule as normal kjar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3801) Parser error with executable-model on Map literal expression in costraint
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-3801:
------------------------------------
Summary: Parser error with executable-model on Map literal expression in costraint
Key: DROOLS-3801
URL: https://issues.jboss.org/browse/DROOLS-3801
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.18.0.Final
Environment: 7.18.0.Final
7.18.0.Final-redhat-00002 (RHDM7.3.0)
7.14.0.Final-redhat-00004 (RHDM7.1.2)
Reporter: Hiroko Miura
Assignee: Luca Molteni
Attachments: MapLiteralTest.zip
When MAP literal expression is used in LHS like the following
{noformat}
when
$fact: Fact(
calc(["src":name, "target":"TEST"])
)
...
{noformat}
KieBase build as Executable Model fails with parser error like:
{noformat}
org.drools.javaparser.ParseProblemException:
Encountered unexpected token: "[" "["
at line 1, column 6.
Was expecting one of:
")"
{noformat}
This error does not happen when building this rule as normal kjar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-11911) Remove READ_TIMEOUT from cannel configuration options
by Teresa Miyar Gil (Jira)
[ https://issues.jboss.org/browse/WFLY-11911?page=com.atlassian.jira.plugin... ]
Teresa Miyar Gil updated WFLY-11911:
------------------------------------
Description:
The only configuration options allowed on the channel by the ultimate consumer of the options org.jboss.remoting3.remote.RemoteReadListener are:
RemotingOptions.TRANSMIT_WINDOW_SIZE,
RemotingOptions.MAX_OUTBOUND_MESSAGES
RemotingOptions.RECEIVE_WINDOW_SIZE
RemotingOptions.MAX_INBOUND_MESSAGES
RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE
RemotingOptions.MAX_INBOUND_MESSAGE_SIZE.
Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be removed.
was:
The only configuration options allowed on the channel are
RemotingOptions.TRANSMIT_WINDOW_SIZE,
RemotingOptions.MAX_OUTBOUND_MESSAGES
RemotingOptions.RECEIVE_WINDOW_SIZE
RemotingOptions.MAX_INBOUND_MESSAGES
RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE
RemotingOptions.MAX_INBOUND_MESSAGE_SIZE.
Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be removed.
> Remove READ_TIMEOUT from cannel configuration options
> -----------------------------------------------------
>
> Key: WFLY-11911
> URL: https://issues.jboss.org/browse/WFLY-11911
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 16.0.0.Final
> Reporter: Teresa Miyar Gil
> Assignee: Teresa Miyar Gil
> Priority: Major
>
> The only configuration options allowed on the channel by the ultimate consumer of the options org.jboss.remoting3.remote.RemoteReadListener are:
> RemotingOptions.TRANSMIT_WINDOW_SIZE,
> RemotingOptions.MAX_OUTBOUND_MESSAGES
> RemotingOptions.RECEIVE_WINDOW_SIZE
> RemotingOptions.MAX_INBOUND_MESSAGES
> RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE
> RemotingOptions.MAX_INBOUND_MESSAGE_SIZE.
> Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be removed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3800) Parser error with executable-model on Map literal expression in costraint
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-3800:
------------------------------------
Summary: Parser error with executable-model on Map literal expression in costraint
Key: DROOLS-3800
URL: https://issues.jboss.org/browse/DROOLS-3800
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.18.0.Final
Environment: 7.18.0.Final
7.18.0.Final-redhat-00002 (RHDM7.3.0)
7.14.0.Final-redhat-00004 (RHDM7.1.2)
Reporter: Hiroko Miura
Assignee: Luca Molteni
Attachments: MapLiteralTest.zip
When MAP literal expression is used in LHS like the following
{noformat}
when
$fact: Fact(
calc(["src":name, "target":"TEST"])
)
...
{noformat}
KieBase build as Executable Model fails with parser error like:
{noformat}
org.drools.javaparser.ParseProblemException:
Encountered unexpected token: "[" "["
at line 1, column 6.
Was expecting one of:
")"
{noformat}
This error does not happen when building this rule as normal kjar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-11914) Upgrade wildfly-http-client to 1.0.14.Final
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11914:
---------------------------------------
Summary: Upgrade wildfly-http-client to 1.0.14.Final
Key: WFLY-11914
URL: https://issues.jboss.org/browse/WFLY-11914
Project: WildFly
Issue Type: Component Upgrade
Components: EJB
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Depend on a release that depends on JBoss Marshalling 2.0.6 -- See WEJBHTTP-24 and WFLY-11720
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months