[
https://issues.jboss.org/browse/JBRULES-3155?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3155:
--------------------------------------------------
lcarlon <lcarlon(a)redhat.com> made a comment on [bug
845843|https://bugzilla.redhat.com/show_bug.cgi?id=845843]
Hi Mario,
could you review this bug to see if it should be included in the release notes, and if so
provide the release notes content?
Thanks
Lee
Bug with default properties in KnowledgeStoreServiceImpl
--------------------------------------------------------
Key: JBRULES-3155
URL:
https://issues.jboss.org/browse/JBRULES-3155
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.Final
Reporter: Pavel Sknar
Assignee: Mario Fusco
Priority: Minor
Fix For: 5.3.2.Final, 5.4.1.Final, 5.5.0.Beta1
Method setDefaultImplementations() set default properties in configProps (class
KnowledgeStoreServiceImpl). mergeConfig() execute after specific properties loaded to
configuration. This overlaps specific properties.
[17:08] <pavlz> hi
[17:09] <pavlz> I have bug for you
[17:09] <Rikkola> :(
[17:10] <pavlz> Problem with KnowledgeStoreServiceImpl
[17:10] <pavlz> in org.drools.persistence.jpa
[17:12] <pavlz> default properties merged first in config (in ChainedProperties:
this.props.add( 0, properties ))
[17:14] <pavlz> and this overlaps specific properties
[17:15] <pavlz> drools.commandService, drools.timerService and else
[17:15] <pavlz> I have this bug in 5.2.0.Final
[17:23] <conan> pavlz: do you have a fix?
[17:25] <pavlz> No, I see this now
[17:27] <pavlz> but I think: need to create in ChainedProperties new method
"setDefaultProperties"
[17:29] <pavlz> and in SessionConfiguration too, to use this method in
KnowledgeStoreServiceImpl.mergeConfig()
[17:30] <pavlz> then default properties loaded later
[17:31] <Rikkola> pavlz: best to make a jira about it
[17:31] <Rikkola>
https://issues.jboss.org/browse/JBRULES
[17:31] <pavlz> ok
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira