[JBoss JIRA] (DROOLS-1509) ServiceResponse XStream marshalling inconsistencies with JAXB
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1509?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-1509:
----------------------------------------
Examples XStream before, showing the inconsistencies:
{code:xml}
10:48:46.045 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to send GET request to 'http://localhost:34455/kie-server-services/services/rest/server'
10:48:46.074 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<org.kie.server.api.model.ServiceResponse>
<type>SUCCESS</type>
<msg>Kie Server info</msg>
<result class="kie-server-info">
<serverId>a0e625bf-251d-3c1f-ad11-0a17f1c14e21</serverId>
<version>7.0.0-SNAPSHOT</version>
<name>KieServer@/kie-server-services</name>
<location>http://localhost:8230/kie-server/services/rest/server</location>
<capabilities>
<string>KieServer</string>
<string>BRM</string>
<string>DMN</string>
</capabilities>
<messages>
<kie-message>
<severity>INFO</severity>
<timestamp>2017-04-04 08:48:07.717 UTC</timestamp>
<messages>
<string>Server KieServerInfo{serverId='a0e625bf-251d-3c1f-ad11-0a17f1c14e21', version='7.0.0-SNAPSHOT', location='http://localhost:8230/kie-server/services/rest/server'}started successfully at Tue Apr 04 10:48:07 CEST 2017</string>
</messages>
</kie-message>
</messages>
</result>
</org.kie.server.api.model.ServiceResponse>'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:46.122 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<org.kie.server.api.model.ServiceResponse>
<type>SUCCESS</type>
<msg>OK from container 'two-dmn-models'</msg>
<result class="dmn-evaluation-result">
<model-namespace>https://www.drools.org/kie-dmn/function-definition</model-namespace>
<model-name>function-definition</model-name>
<dmn-context class="linked-hash-map">
<entry>
<string>a</string>
<int>10</int>
</entry>
<entry>
<string>b</string>
<int>5</int>
</entry>
<entry>
<string>Math</string>
<map>
<entry>
<string>SumFunction</string>
<dmn-node-stub>function Math( v1, v2 )</dmn-node-stub>
</entry>
<entry>
<string>Sum</string>
<big-decimal>15</big-decimal>
</entry>
</map>
</entry>
</dmn-context>
<messages/>
<decision-results>
<entry>
<string>_b459d12a-f00f-4846-a12e-2883455f7d7b</string>
<dmn-decision-result>
<decision-id>_b459d12a-f00f-4846-a12e-2883455f7d7b</decision-id>
<decision-name>Math</decision-name>
<result class="map" reference="../../../../dmn-context/entry[3]/map"/>
<status>SUCCEEDED</status>
</dmn-decision-result>
</entry>
</decision-results>
</result>
</org.kie.server.api.model.ServiceResponse>'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:46.127 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to send GET request to 'http://localhost:34455/kie-server-services/services/rest/server'
10:48:46.133 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<org.kie.server.api.model.ServiceResponse>
<type>SUCCESS</type>
<msg>Kie Server info</msg>
<result class="kie-server-info">
<serverId>a0e625bf-251d-3c1f-ad11-0a17f1c14e21</serverId>
<version>7.0.0-SNAPSHOT</version>
<name>KieServer@/kie-server-services</name>
<location>http://localhost:8230/kie-server/services/rest/server</location>
<capabilities>
<string>KieServer</string>
<string>BRM</string>
<string>DMN</string>
</capabilities>
<messages>
<kie-message>
<severity>INFO</severity>
<timestamp>2017-04-04 08:48:07.717 UTC</timestamp>
<messages>
<string>Server KieServerInfo{serverId='a0e625bf-251d-3c1f-ad11-0a17f1c14e21', version='7.0.0-SNAPSHOT', location='http://localhost:8230/kie-server/services/rest/server'}started successfully at Tue Apr 04 10:48:07 CEST 2017</string>
</messages>
</kie-message>
</messages>
</result>
</org.kie.server.api.model.ServiceResponse>'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:46.151 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<org.kie.server.api.model.ServiceResponse>
<type>SUCCESS</type>
<msg>OK from container 'two-dmn-models'</msg>
<result class="dmn-evaluation-result">
<model-namespace>https://github.com/kiegroup/kie-dmn/input-data-string</model-namespace>
<model-name>input-data-string</model-name>
<dmn-context class="linked-hash-map">
<entry>
<string>Full Name</string>
<string>John Doe</string>
</entry>
<entry>
<string>Greeting Message</string>
<string>Hello John Doe</string>
</entry>
</dmn-context>
<messages/>
<decision-results>
<entry>
<string>d_GreetingMessage</string>
<dmn-decision-result>
<decision-id>d_GreetingMessage</decision-id>
<decision-name>Greeting Message</decision-name>
<result class="string">Hello John Doe</result>
<status>SUCCEEDED</status>
</dmn-decision-result>
</entry>
</decision-results>
</result>
</org.kie.server.api.model.ServiceResponse>'
into type: 'class org.kie.server.api.model.ServiceResponse'
{code}
> ServiceResponse XStream marshalling inconsistencies with JAXB
> -------------------------------------------------------------
>
> Key: DROOLS-1509
> URL: https://issues.jboss.org/browse/DROOLS-1509
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
> XML Element in XStream is rendered with canonical name instead of being consistent with JAXB, for "response".
> Additionally in JAXB marshalling the {{type}} and {{msg}} are attributes, while in XStream are child elements.
> Please notice String special character escape is handled differently JAXB Vs XStream and this is NOT subject of this bug.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-1509) ServiceResponse XStream marshalling inconsistencies with JAXB
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1509?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-1509:
----------------------------------------
Example JAXB (baseline of reference, and unchanged):
{code:xml}
10:48:11.167 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to send GET request to 'http://localhost:34455/kie-server-services/services/rest/server'
10:48:11.518 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="SUCCESS" msg="Kie Server info">
<kie-server-info>
<capabilities>KieServer</capabilities>
<capabilities>BRM</capabilities>
<capabilities>DMN</capabilities>
<location>http://localhost:8230/kie-server/services/rest/server</location>
<messages>
<content>Server KieServerInfo{serverId='a0e625bf-251d-3c1f-ad11-0a17f1c14e21', version='7.0.0-SNAPSHOT', location='http://localhost:8230/kie-server/services/rest/server'}started successfully at Tue Apr 04 10:48:07 CEST 2017</content>
<severity>INFO</severity>
<timestamp>2017-04-04T10:48:07.717+02:00</timestamp>
</messages>
<name>KieServer@/kie-server-services</name>
<id>a0e625bf-251d-3c1f-ad11-0a17f1c14e21</id>
<version>7.0.0-SNAPSHOT</version>
</kie-server-info>
</response>
'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:11.672 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to send GET request to 'http://localhost:34455/kie-server-services/services/rest/server/containers'
10:48:11.677 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="SUCCESS" msg="List of created containers">
<kie-containers/>
</response>
'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:43.307 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to send GET request to 'http://localhost:34455/kie-server-services/services/rest/server'
10:48:43.313 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="SUCCESS" msg="Kie Server info">
<kie-server-info>
<capabilities>KieServer</capabilities>
<capabilities>BRM</capabilities>
<capabilities>DMN</capabilities>
<location>http://localhost:8230/kie-server/services/rest/server</location>
<messages>
<content>Server KieServerInfo{serverId='a0e625bf-251d-3c1f-ad11-0a17f1c14e21', version='7.0.0-SNAPSHOT', location='http://localhost:8230/kie-server/services/rest/server'}started successfully at Tue Apr 04 10:48:07 CEST 2017</content>
<severity>INFO</severity>
<timestamp>2017-04-04T10:48:07.717+02:00</timestamp>
</messages>
<name>KieServer@/kie-server-services</name>
<id>a0e625bf-251d-3c1f-ad11-0a17f1c14e21</id>
<version>7.0.0-SNAPSHOT</version>
</kie-server-info>
</response>
'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:44.944 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="SUCCESS" msg="Container two-dmn-models successfully deployed with module org.kie.server.testing:two-dmn-models:1.0.0.Final.">
<kie-container container-id="two-dmn-models" status="STARTED">
<release-id>
<artifact-id>two-dmn-models</artifact-id>
<group-id>org.kie.server.testing</group-id>
<version>1.0.0.Final</version>
</release-id>
<resolved-release-id>
<artifact-id>two-dmn-models</artifact-id>
<group-id>org.kie.server.testing</group-id>
<version>1.0.0.Final</version>
</resolved-release-id>
<scanner status="DISPOSED"/>
</kie-container>
</response>
'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:44.999 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to send GET request to 'http://localhost:34455/kie-server-services/services/rest/server'
10:48:45.004 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="SUCCESS" msg="Kie Server info">
<kie-server-info>
<capabilities>KieServer</capabilities>
<capabilities>BRM</capabilities>
<capabilities>DMN</capabilities>
<location>http://localhost:8230/kie-server/services/rest/server</location>
<messages>
<content>Server KieServerInfo{serverId='a0e625bf-251d-3c1f-ad11-0a17f1c14e21', version='7.0.0-SNAPSHOT', location='http://localhost:8230/kie-server/services/rest/server'}started successfully at Tue Apr 04 10:48:07 CEST 2017</content>
<severity>INFO</severity>
<timestamp>2017-04-04T10:48:07.717+02:00</timestamp>
</messages>
<name>KieServer@/kie-server-services</name>
<id>a0e625bf-251d-3c1f-ad11-0a17f1c14e21</id>
<version>7.0.0-SNAPSHOT</version>
</kie-server-info>
</response>
'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:45.372 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="SUCCESS" msg="OK from container 'two-dmn-models'">
<dmn-evaluation-result>
<model-namespace>https://www.drools.org/kie-dmn/function-definition</model-namespace>
<model-name>function-definition</model-name>
<dmn-context xsi:type="jaxbListWrapper" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<type>MAP</type>
<element xsi:type="jaxbStringObjectPair" key="a">
<value xsi:type="xs:int" xmlns:xs="http://www.w3.org/2001/XMLSchema">10</value>
</element>
<element xsi:type="jaxbStringObjectPair" key="b">
<value xsi:type="xs:int" xmlns:xs="http://www.w3.org/2001/XMLSchema">5</value>
</element>
<element xsi:type="jaxbStringObjectPair" key="Math">
<value xsi:type="jaxbListWrapper">
<type>MAP</type>
<element xsi:type="jaxbStringObjectPair" key="SumFunction">
<value xsi:type="dmnNodeStub">function Math( v1, v2 )</value>
</element>
<element xsi:type="jaxbStringObjectPair" key="Sum">
<value xsi:type="xs:decimal" xmlns:xs="http://www.w3.org/2001/XMLSchema">15</value>
</element>
</value>
</element>
</dmn-context>
<messages/>
<decisionResults>
<entry>
<key>_b459d12a-f00f-4846-a12e-2883455f7d7b</key>
<value>
<decision-id>_b459d12a-f00f-4846-a12e-2883455f7d7b</decision-id>
<decision-name>Math</decision-name>
<result xsi:type="jaxbListWrapper" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<type>MAP</type>
<element xsi:type="jaxbStringObjectPair" key="SumFunction">
<value xsi:type="dmnNodeStub">function Math( v1, v2 )</value>
</element>
<element xsi:type="jaxbStringObjectPair" key="Sum">
<value xsi:type="xs:decimal" xmlns:xs="http://www.w3.org/2001/XMLSchema">15</value>
</element>
</result>
<status>SUCCEEDED</status>
</value>
</entry>
</decisionResults>
</dmn-evaluation-result>
</response>
'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:45.429 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to send GET request to 'http://localhost:34455/kie-server-services/services/rest/server'
10:48:45.436 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="SUCCESS" msg="Kie Server info">
<kie-server-info>
<capabilities>KieServer</capabilities>
<capabilities>BRM</capabilities>
<capabilities>DMN</capabilities>
<location>http://localhost:8230/kie-server/services/rest/server</location>
<messages>
<content>Server KieServerInfo{serverId='a0e625bf-251d-3c1f-ad11-0a17f1c14e21', version='7.0.0-SNAPSHOT', location='http://localhost:8230/kie-server/services/rest/server'}started successfully at Tue Apr 04 10:48:07 CEST 2017</content>
<severity>INFO</severity>
<timestamp>2017-04-04T10:48:07.717+02:00</timestamp>
</messages>
<name>KieServer@/kie-server-services</name>
<id>a0e625bf-251d-3c1f-ad11-0a17f1c14e21</id>
<version>7.0.0-SNAPSHOT</version>
</kie-server-info>
</response>
'
into type: 'class org.kie.server.api.model.ServiceResponse'
10:48:45.541 [main] DEBUG o.k.s.c.i.AbstractKieServicesClientImpl - About to deserialize content:
'<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="SUCCESS" msg="OK from container 'two-dmn-models'">
<dmn-evaluation-result>
<model-namespace>https://github.com/kiegroup/kie-dmn/input-data-string</model-namespace>
<model-name>input-data-string</model-name>
<dmn-context xsi:type="jaxbListWrapper" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<type>MAP</type>
<element xsi:type="jaxbStringObjectPair" key="Full Name">
<value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">John Doe</value>
</element>
<element xsi:type="jaxbStringObjectPair" key="Greeting Message">
<value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">Hello John Doe</value>
</element>
</dmn-context>
<messages/>
<decisionResults>
<entry>
<key>d_GreetingMessage</key>
<value>
<decision-id>d_GreetingMessage</decision-id>
<decision-name>Greeting Message</decision-name>
<result xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello John Doe</result>
<status>SUCCEEDED</status>
</value>
</entry>
</decisionResults>
</dmn-evaluation-result>
</response>
'
into type: 'class org.kie.server.api.model.ServiceResponse'
{code}
> ServiceResponse XStream marshalling inconsistencies with JAXB
> -------------------------------------------------------------
>
> Key: DROOLS-1509
> URL: https://issues.jboss.org/browse/DROOLS-1509
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
> XML Element in XStream is rendered with canonical name instead of being consistent with JAXB, for "response".
> Additionally in JAXB marshalling the {{type}} and {{msg}} are attributes, while in XStream are child elements.
> Please notice String special character escape is handled differently JAXB Vs XStream and this is NOT subject of this bug.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (HAWKULARQE-83) Create test cases for hawkular-wildfly-agent-installer.jar
by Hayk Hovsepyan (JIRA)
[ https://issues.jboss.org/browse/HAWKULARQE-83?page=com.atlassian.jira.plu... ]
Hayk Hovsepyan reassigned HAWKULARQE-83:
----------------------------------------
Assignee: Hayk Hovsepyan (was: Michael Foley)
> Create test cases for hawkular-wildfly-agent-installer.jar
> ----------------------------------------------------------
>
> Key: HAWKULARQE-83
> URL: https://issues.jboss.org/browse/HAWKULARQE-83
> Project: Hawkular QE
> Issue Type: Task
> Reporter: Filip Brychta
> Assignee: Hayk Hovsepyan
>
> hawkular-wildfly-agent-installer.jar has following options:
> Options:
> -D, --D Defines system properties to set
> --installer-config Installer .properties configuration file
> --encryption-key If specified, this is used to decode the properties that were encrypted. If you do not provide a value with the option, you will be prompted for one.
> --encryption-salt The salt used for generating the key. Recommended, if encryption is used. If not specified, the same value as the key will be used.
> --enabled Indicates if the agent should be enabled at startup
> --config-only Skip installation of the add-ons modules, and only update the server config (e.g. standalone.xml).
> --target-location Target home directory of the application server where the agent is to be installed
> --module-dist Hawkular WildFly Agent Module distribution zip file - can be a file path or URL
> --server-url Server URL where the agent will send its monitoring data. This is a string to be set as the storage adapter URL.
> --download-server-url Server URL from which the installer will download content it may need. If not specified and the installer needs to download something then --server-url will be used.
> --target-config The target configuration file to write to. Can be either absolute path or relative to target-location
> --subsystem-snippet Customized subsystem XML content that overrides the default subsystem configuration
> --managed-server-name The agent will use this name to refer to the server where it is deployed and locally managing.
> --feed-id The feed ID that the agent will use to identify its data.
> --tenant-id The tenant ID that the agent will ask to be used. Usually only used when in metrics-only mode.
> --metrics-only If true, the agent will be configured to run in metrics-only mode (inventory will not be stored and no websocket connection to a Hawkular Server will be made.) If true, you must specify a tenant-id.
> --managed-server-resource-type-sets If true, the agent will be configured to monitor these resource type sets. If not provided, a default set will be used based on the type of application server where the agent is being installed into (standalone or domain).
> --keystore-path Keystore file. Required when server-url protocol is https
> --keystore-password Keystore password. When server-url protocol is https and this option is not passed, installer will ask for password
> --username User the agent will use when connecting to Hawkular Server.
> --password Credentials agent will use when connecting to Hawkular Server.
> We need to create test cases to cover that
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-1509) ServiceResponse XStream marshalling inconsistencies with JAXB
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1509?page=com.atlassian.jira.plugi... ]
Matteo Mortari updated DROOLS-1509:
-----------------------------------
Description:
XML Element in XStream is rendered with canonical name instead of being consistent with JAXB, for "response".
Additionally in JAXB marshalling the {{type}} and {{msg}} are attributes, while in XStream are child elements.
Please notice String special character escape is handled differently JAXB Vs XStream and this is NOT subject of this bug.
was:
... instead of being consistent with JAXB, for "response".
Additionally in JAXB marshalling the
> ServiceResponse XStream marshalling inconsistencies with JAXB
> -------------------------------------------------------------
>
> Key: DROOLS-1509
> URL: https://issues.jboss.org/browse/DROOLS-1509
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
> XML Element in XStream is rendered with canonical name instead of being consistent with JAXB, for "response".
> Additionally in JAXB marshalling the {{type}} and {{msg}} are attributes, while in XStream are child elements.
> Please notice String special character escape is handled differently JAXB Vs XStream and this is NOT subject of this bug.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2622) Logging handler lost due to conflict handlers in logging.properties and standalone.xml
by Kabir Khan (JIRA)
Kabir Khan created WFCORE-2622:
----------------------------------
Summary: Logging handler lost due to conflict handlers in logging.properties and standalone.xml
Key: WFCORE-2622
URL: https://issues.jboss.org/browse/WFCORE-2622
Project: WildFly Core
Issue Type: Bug
Components: Logging
Affects Versions: 2.0.10.Final
Reporter: Takayoshi Kimura
Assignee: James Perkins
Fix For: 3.0.0.Beta11
Console logging doesn't work after logging subsystem init with the following configuration.
* logging.properties is configured with ASYNC with CONSOLE handlers.
* standalone.xml is configured with stock FILE and CONSOLE handlers.
Background of why there is a mismatch between logging.properties and standalone.xml, EAP image for OpenShift is configured with ASYNC with CONSOLE handlers by default. But users can customize standalone.xml and apply custom configuration based on the stock standalone.xml.
Expected result is logging configuration from standalone.xml is applied once logging subsystem come up regardless the mismatch.
Most likely related to WFCORE-159.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2621) Upgrade jboss-logmanager from 2.0.5.Final to 2.0.6.Final
by Kabir Khan (JIRA)
Kabir Khan created WFCORE-2621:
----------------------------------
Summary: Upgrade jboss-logmanager from 2.0.5.Final to 2.0.6.Final
Key: WFCORE-2621
URL: https://issues.jboss.org/browse/WFCORE-2621
Project: WildFly Core
Issue Type: Component Upgrade
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Fix For: 3.0.0.Beta11
An upgrade to the log manager will be required to resolve WFCORE-1585. An enhancement was made as part of LOGMGR-147 to allow child handlers to not be closed when the parent handler is closed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-1507) Error message "unable to invole method" should mention DRL line
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1507?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1507:
-------------------------------------
Affects Version/s: 6.5.0.Final
> Error message "unable to invole method" should mention DRL line
> ---------------------------------------------------------------
>
> Key: DROOLS-1507
> URL: https://issues.jboss.org/browse/DROOLS-1507
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> In a complex DRL file we wrote something like this:
> {code}
> when
> Visit(foo != null, $w : foo.weekOfYear)
> not Visit(foo.weekOfYear < $w)
> then
> ...
> end
> {code}
> throws this exception:
> {code}
> java.lang.RuntimeException: cannot invoke getter: getFoo ...
> at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:74)
> ...
> Caused by: java.lang.RuntimeException: unable to invoke method: ....foo.getWeekOfYear: target of method is null
> at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:66)
> at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:40)
> ...
> Caused by: java.lang.NullPointerException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:43)
> {code}
> with no DRL line.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months