[JBoss JIRA] (DROOLS-729) Android Support
by Mark Kedzierski (JIRA)
[ https://issues.jboss.org/browse/DROOLS-729?page=com.atlassian.jira.plugin... ]
Mark Kedzierski updated DROOLS-729:
-----------------------------------
Git Pull Request: https://github.com/mvel/mvel/pull/72, https://github.com/droolsjbpm/drools/pull/416 (was: https://github.com/mvel/mvel/pull/72)
> Android Support
> ---------------
>
> Key: DROOLS-729
> URL: https://issues.jboss.org/browse/DROOLS-729
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.3.0.Final
> Environment: Android
> Reporter: Mark Kedzierski
> Assignee: Mario Fusco
> Priority: Optional
> Labels: Android
>
> I've done some work porting Drools 6.0.1.Final to work on Android. My current effort uses Dex classloaders for all generated classes. Precompiled rule packages execute on Android with either java or mvel dialect.
> code:
> http://www.github.com/kedzie/drools-android
> Features:
> -Dex classloaders for all generated classes
> -Roboguice integration for injecting knowledge bases from precompiled packages
> -Maven plugin which pre-compiles rule packages
> Issues:
> -Android 5.0 support requires change in mvel2. android 5 doesn't allow overriding the java.version system property. mvel needs to look for an alternate property if that one is not available. One which can be set. I am preparing a pull request for this.
> -using KieClasspathContainer depends on my pull request to maven-android-plugin to not strip out kmodule.xml and other meta inf resources
> -multiple kjars in dependencies will clobber each other's kmodule.xml. as all jars are merged into a single apk.
> I am wondering how to move forward and contribute this code. I think it would be ideal if the same codebase worked on both desktop and android platforms. Otherwise it would need to be a seperate fork. Also how to manage unit testing in the Android version. Any thoughts welcome.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (DROOLS-729) Android Support
by Mark Kedzierski (JIRA)
[ https://issues.jboss.org/browse/DROOLS-729?page=com.atlassian.jira.plugin... ]
Mark Kedzierski updated DROOLS-729:
-----------------------------------
Description:
I've done some work porting Drools 6.0.1.Final to work on Android. My current effort uses Dex classloaders for all generated classes. Precompiled rule packages execute on Android with either java or mvel dialect.
code:
http://www.github.com/kedzie/drools-android
Features:
-Dex classloaders for all generated classes
-Roboguice integration for injecting knowledge bases from precompiled packages
-Maven plugin which pre-compiles rule packages
Issues:
-Android 5.0 support requires change in mvel2. android 5 doesn't allow overriding the java.version system property. mvel needs to look for an alternate property if that one is not available. One which can be set. I am preparing a pull request for this.
-using KieClasspathContainer depends on my pull request to maven-android-plugin to not strip out kmodule.xml and other meta inf resources
-multiple kjars in dependencies will clobber each other's kmodule.xml. as all jars are merged into a single apk.
I am wondering how to move forward and contribute this code. I think it would be ideal if the same codebase worked on both desktop and android platforms. Otherwise it would need to be a seperate fork. Also how to manage unit testing in the Android version. Any thoughts welcome.
was:
I've done some work porting Drools 6.0.1.Final to work on Android. My current effort uses Dex classloaders for all generated classes. Precompiled rule packages execute on Android with either java or mvel dialect.
code:
http://www.github.com/kedzie/drools-android
http://www.github.com/kedzie/drools-android-sample
Features:
-Dex classloaders for all generated classes
-Roboguice integration for injecting knowledge bases from precompiled packages
-Maven plugin which pre-compiles rule packages
Issues:
-Android 5.0 support requires change in mvel2. android 5 doesn't allow overriding the java.version system property. mvel needs to look for an alternate property if that one is not available. One which can be set. I am preparing a pull request for this.
-using KieClasspathContainer depends on my pull request to maven-android-plugin to not strip out kmodule.xml and other meta inf resources
-multiple kjars in dependencies will clobber each other's kmodule.xml. as all jars are merged into a single apk.
I am wondering how to move forward and contribute this code. I think it would be ideal if the same codebase worked on both desktop and android platforms. Otherwise it would need to be a seperate fork. Also how to manage unit testing in the Android version. Any thoughts welcome.
> Android Support
> ---------------
>
> Key: DROOLS-729
> URL: https://issues.jboss.org/browse/DROOLS-729
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.3.0.Final
> Environment: Android
> Reporter: Mark Kedzierski
> Assignee: Mario Fusco
> Priority: Optional
> Labels: Android
>
> I've done some work porting Drools 6.0.1.Final to work on Android. My current effort uses Dex classloaders for all generated classes. Precompiled rule packages execute on Android with either java or mvel dialect.
> code:
> http://www.github.com/kedzie/drools-android
> Features:
> -Dex classloaders for all generated classes
> -Roboguice integration for injecting knowledge bases from precompiled packages
> -Maven plugin which pre-compiles rule packages
> Issues:
> -Android 5.0 support requires change in mvel2. android 5 doesn't allow overriding the java.version system property. mvel needs to look for an alternate property if that one is not available. One which can be set. I am preparing a pull request for this.
> -using KieClasspathContainer depends on my pull request to maven-android-plugin to not strip out kmodule.xml and other meta inf resources
> -multiple kjars in dependencies will clobber each other's kmodule.xml. as all jars are merged into a single apk.
> I am wondering how to move forward and contribute this code. I think it would be ideal if the same codebase worked on both desktop and android platforms. Otherwise it would need to be a seperate fork. Also how to manage unit testing in the Android version. Any thoughts welcome.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFLY-4405) NPE in AstValue.setValue()
by Christer Bernérus (JIRA)
[ https://issues.jboss.org/browse/WFLY-4405?page=com.atlassian.jira.plugin.... ]
Christer Bernérus updated WFLY-4405:
------------------------------------
That will be hard. The app causing this needs a lot of infrastucture to be able to run off-site.
I can try to put together something simple, however not this week, I'll be too busy and as
for myself I'm in no hurry. Please let me know if someone else have similar problems though.
-- Chris
> NPE in AstValue.setValue()
> --------------------------
>
> Key: WFLY-4405
> URL: https://issues.jboss.org/browse/WFLY-4405
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 8.2.0.Final
> Environment: MacOS X, RHEL6
> Reporter: Christer Bernérus
> Assignee: Farah Juma
>
> When submitting a page made up using a custom tag, or a composite component, WildFly reports NPE in AstValue.setValue().
> The code where this happens is in javax.el-3.0.1-b05.jar and looks like this:
> {code:title=AstValue.java|borderStyle=solid}
> /* Note by kchung 10/2013
> * The spec does not say if the value should be cocerced to the target
> * type before setting the value to the target. The conversion is kept
> * here to be backward compatible.
> */
> ctx.setPropertyResolved(false);
> Class<?> targetType = elResolver.getType(ctx, t.base, property);
> if (ctx.isPropertyResolved()) {
> ctx.setPropertyResolved(false);
> Object targetValue = elResolver.convertToType(ctx, value, targetType);
> if (ctx.isPropertyResolved()) {
> value = targetValue;
> } else {
> if (value != null || targetType.isPrimitive()) {
> value = ELSupport.coerceToType(value, targetType);
> }
> }
> }
> {code}
> From my debugging session, I have seen that the code in
> {{elResolver.getType()}} may return null, which happens to me,
> but the subsequent code in {{AstValue.setValue()}} happily uses that null valued variable {{targetType}} for calling the method {{isPrimitive()}} which of course causes an NPE.
> Strangely enough, this behaviour seems intermittent in that restarting WildFly might make the bug go away or come back, but redeployment does not.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (DROOLS-711) Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-711?page=com.atlassian.jira.plugin... ]
Matteo Mortari commented on DROOLS-711:
---------------------------------------
Hi, just FYI I tested with 6.2.0.Final and the problem persist also in this release.
> Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test
> ----------------------------------------------------------------------------------------
>
> Key: DROOLS-711
> URL: https://issues.jboss.org/browse/DROOLS-711
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR4, 6.2.0.Final
> Environment: kie-server on WildFly 8.2.0.Final running with JDK 8
> Reporter: Matteo Mortari
> Assignee: Mark Proctor
> Attachments: 20150213.DROOLS-711.zip
>
>
> I have deployed Kie Server kie-server-distribution-wars-6.2.0.CR4-ee7.war on WildFly 8.2.0.Final.
> I have a simple rule base in the project {{client-test-rules}} as per below, in a kie project structured as kie-drools-archetype, which passes all test and install in m2 repo with {{mvn clean install}}.
> {code:java}
> package com.acme.client_test_rules;
> declare Measurement
> @role(event)
> end
> rule "keep latest Measurement ID"
> salience 1000
> no-loop
> when
> $old : Measurement( $id : id )
> $new : Measurement( id == $id , this after $old )
> then
> System.out.println("keep latest old : "+$old+" new (kept): "+$new);
> retract($old);
> end
> {code}
> Then I issue Kie Server commands, using the client library, using project {{client-test}} to instantiate a container for the same artifact, but in the wildfly logs I get the following error below - which doesn't happen for kie-maven-plugin nor during unit test. Please note I'm assuming user {{kieserver}} with password {{kieserver}} is a valid user for the Kie Server Realm, or configure wildfly or the code in the project {{client-test}} accordingly to your environment =).
> {code}
> 09:41:41,700 ERROR [org.drools.compiler.kie.builder.impl.AbstractKieModule] (default task-4) Unable to build KieBaseModel:kbase1
> Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement'
> : [Rule name='keep latest Measurement ID']
> java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement'
> Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement'
> : [Rule name='keep latest Measurement ID']
> java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement'
> Field Reader does not exist for declaration '$id' in 'predicate 'id == $id'' in the rule 'keep latest Measurement ID' : [Rule name='keep latest Measurement ID']
> Unable to Analyse Expression id == $id:
> [Error: unable to resolve method using strict-mode: com.acme.client_test_rules.Measurement.id()]
> [Near : {... id == $id ....}]
> ^
> [Line: 12, Column: 4] : [Rule name='keep latest Measurement ID']
> {code}
> Can you kindly verify if some bug is hiding behind this odd behavior, please?
> Thank you
> MM
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (DROOLS-711) Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-711?page=com.atlassian.jira.plugin... ]
Matteo Mortari updated DROOLS-711:
----------------------------------
Affects Version/s: 6.2.0.Final
> Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test
> ----------------------------------------------------------------------------------------
>
> Key: DROOLS-711
> URL: https://issues.jboss.org/browse/DROOLS-711
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR4, 6.2.0.Final
> Environment: kie-server on WildFly 8.2.0.Final running with JDK 8
> Reporter: Matteo Mortari
> Assignee: Mark Proctor
> Attachments: 20150213.DROOLS-711.zip
>
>
> I have deployed Kie Server kie-server-distribution-wars-6.2.0.CR4-ee7.war on WildFly 8.2.0.Final.
> I have a simple rule base in the project {{client-test-rules}} as per below, in a kie project structured as kie-drools-archetype, which passes all test and install in m2 repo with {{mvn clean install}}.
> {code:java}
> package com.acme.client_test_rules;
> declare Measurement
> @role(event)
> end
> rule "keep latest Measurement ID"
> salience 1000
> no-loop
> when
> $old : Measurement( $id : id )
> $new : Measurement( id == $id , this after $old )
> then
> System.out.println("keep latest old : "+$old+" new (kept): "+$new);
> retract($old);
> end
> {code}
> Then I issue Kie Server commands, using the client library, using project {{client-test}} to instantiate a container for the same artifact, but in the wildfly logs I get the following error below - which doesn't happen for kie-maven-plugin nor during unit test. Please note I'm assuming user {{kieserver}} with password {{kieserver}} is a valid user for the Kie Server Realm, or configure wildfly or the code in the project {{client-test}} accordingly to your environment =).
> {code}
> 09:41:41,700 ERROR [org.drools.compiler.kie.builder.impl.AbstractKieModule] (default task-4) Unable to build KieBaseModel:kbase1
> Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement'
> : [Rule name='keep latest Measurement ID']
> java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement'
> Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement'
> : [Rule name='keep latest Measurement ID']
> java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement'
> Field Reader does not exist for declaration '$id' in 'predicate 'id == $id'' in the rule 'keep latest Measurement ID' : [Rule name='keep latest Measurement ID']
> Unable to Analyse Expression id == $id:
> [Error: unable to resolve method using strict-mode: com.acme.client_test_rules.Measurement.id()]
> [Near : {... id == $id ....}]
> ^
> [Line: 12, Column: 4] : [Rule name='keep latest Measurement ID']
> {code}
> Can you kindly verify if some bug is hiding behind this odd behavior, please?
> Thank you
> MM
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFCORE-589) Get system-jmx out of core
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-589:
---------------------------------------
Summary: Get system-jmx out of core
Key: WFCORE-589
URL: https://issues.jboss.org/browse/WFCORE-589
Project: WildFly Core
Issue Type: Task
Components: Server
Reporter: Brian Stansberry
Assignee: Tomaz Cerar
Fix For: 1.0.0.Beta1
The system-jmx module doesn't belong in core; it's equivalent to the "pojo" module, but for mbean services / sars instead of JBoss Microcontainer services. So we need to get it back into full.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months