[JBoss JIRA] (DROOLS-1015) Wrong MvelConstraint compilation with Unicode class name and the same name property
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1015?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration updated DROOLS-1015:
--------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1294048
Bugzilla Update: Perform
> Wrong MvelConstraint compilation with Unicode class name and the same name property
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1015
> URL: https://issues.jboss.org/browse/DROOLS-1015
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
>
> If a fact has a property of Unicode class name (e.g. 住所) and the property name is the same (住所), constraint is not correctly compiled by MVEL. Internally, AbstractParser.createPropertyToken() misunderstands the property as a class name literal.
> {code:java}
> public class I18nPerson implements Serializable {
> private 住所 住所; // "address" in Japanese
> public 住所 get住所() {
> return 住所;
> }
> ....
> {code}
> {noformat}
> when
> p : I18nPerson( 住所 != null )
> {noformat}
> This constraint is always evaluated to "true".
> Essentially, this is not only a problem of Unicode. We can reproduce the issue by a capitalized property name.
> {code:java}
> public class Person implements Serializable {
> private Address address;
> public Address getAddress() {
> return address;
> }
> ....
> {code}
> {noformat}
> when
> p : I18nPerson( Address != null )
> {noformat}
> Of course we should use lower case letters here from JavaBeans point of view so we don't hit this issue with English usually. But some languages like Japanese cannot express "lower case/upper case" so result in this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (DROOLS-1015) Wrong MvelConstraint compilation with Unicode class name and the same name property
by Toshiya Kobayashi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1015?page=com.atlassian.jira.plugi... ]
Toshiya Kobayashi updated DROOLS-1015:
--------------------------------------
Git Pull Request: https://github.com/droolsjbpm/drools/pull/592
> Wrong MvelConstraint compilation with Unicode class name and the same name property
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1015
> URL: https://issues.jboss.org/browse/DROOLS-1015
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
>
> If a fact has a property of Unicode class name (e.g. 住所) and the property name is the same (住所), constraint is not correctly compiled by MVEL. Internally, AbstractParser.createPropertyToken() misunderstands the property as a class name literal.
> {code:java}
> public class I18nPerson implements Serializable {
> private 住所 住所; // "address" in Japanese
> public 住所 get住所() {
> return 住所;
> }
> ....
> {code}
> {noformat}
> when
> p : I18nPerson( 住所 != null )
> {noformat}
> This constraint is always evaluated to "true".
> Essentially, this is not only a problem of Unicode. We can reproduce the issue by a capitalized property name.
> {code:java}
> public class Person implements Serializable {
> private Address address;
> public Address getAddress() {
> return address;
> }
> ....
> {code}
> {noformat}
> when
> p : I18nPerson( Address != null )
> {noformat}
> Of course we should use lower case letters here from JavaBeans point of view so we don't hit this issue with English usually. But some languages like Japanese cannot express "lower case/upper case" so result in this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (DROOLS-1015) Wrong MvelConstraint compilation with Unicode class name and the same name property
by Toshiya Kobayashi (JIRA)
Toshiya Kobayashi created DROOLS-1015:
-----------------------------------------
Summary: Wrong MvelConstraint compilation with Unicode class name and the same name property
Key: DROOLS-1015
URL: https://issues.jboss.org/browse/DROOLS-1015
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.3.0.Final
Reporter: Toshiya Kobayashi
Assignee: Mario Fusco
If a fact has a property of Unicode class name (e.g. 住所) and the property name is the same (住所), constraint is not correctly compiled by MVEL. Internally, AbstractParser.createPropertyToken() misunderstands the property as a class name literal.
{code:java}
public class I18nPerson implements Serializable {
private 住所 住所; // "address" in Japanese
public 住所 get住所() {
return 住所;
}
....
{code}
{noformat}
when
p : I18nPerson( 住所 != null )
{noformat}
This constraint is always evaluated to "true".
Essentially, this is not only a problem of Unicode. We can reproduce the issue by a capitalized property name.
{code:java}
public class Person implements Serializable {
private Address address;
public Address getAddress() {
return address;
}
....
{code}
{noformat}
when
p : I18nPerson( Address != null )
{noformat}
Of course we should use lower case letters here from JavaBeans point of view so we don't hit this issue with English usually. But some languages like Japanese cannot express "lower case/upper case" so result in this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (DROOLS-1012) kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1012?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on DROOLS-1012:
-------------------------------------------------
Alessandro Lazarotti <alazarot(a)redhat.com> changed the Status of [bug 1293965|https://bugzilla.redhat.com/show_bug.cgi?id=1293965] from NEW to ASSIGNED
> kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-1012
> URL: https://issues.jboss.org/browse/DROOLS-1012
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
> Attachments: brms-fuse-integration-master.tgz
>
>
> kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry. This implies that when the KieContainer is created in a OSGi environment it is not able to get an instance of the MavenClassLoaderResolver and then cannot create a ClassLoader including all the transitive dependencies of the kjar to be compiled.
> The attached project reproduces this issue. In order to run it, it's enough to do a mvn clean install of the project and issue the following commands in fuse:
> features:addurl mvn:com.redhat/brms-fuse-integration-features/0.0.1-SNAPSHOT/xml/features
> features:install brms-integration-bundle
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5911) Update fasterxml.jackson.* from 2.5.4 to 2.6.4.
by Frank Langelage (JIRA)
Frank Langelage created WFLY-5911:
-------------------------------------
Summary: Update fasterxml.jackson.* from 2.5.4 to 2.6.4.
Key: WFLY-5911
URL: https://issues.jboss.org/browse/WFLY-5911
Project: WildFly
Issue Type: Component Upgrade
Components: REST
Affects Versions: 10.0.0.CR5
Reporter: Frank Langelage
Assignee: Stuart Douglas
Fix For: 10.0.0.Final
Update com.fasterxml.jackson to latest version.
Precondition: update of resteasy to latest version.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months