Bug 1261834 - Improve separation of KieModules used by "asset validation" and "project" build
Improve separation of KieModules used by "asset validation" and "project" build
Status: NEW
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: Business Central (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: ---
: ---
Assigned To: manstis
Jiri Locker
Depends On:
  Show dependency treegraph
Reported: 2015-09-10 05:43 EDT by manstis
Modified: 2016-01-08 17:13 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Enhancement
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description manstis 2015-09-10 05:43:06 EDT
Description of problem:

Business Central uses different instances of KieBuilder and related KieFileSystem to build KieModules for the *same* ReleaseId during "asset validation" and "project build". The separation is to support validation of (DRL) assets by KieBuilder before the User commits changes made during authoring to the main "project" KieBuilder instance.

This leads to problems when "validation" has occurred *after* a Project build as KieServices.newKieContainer(ReleaseId) resolves the KieModule from KieRepository, which in the above scenario means it is the *transient* KieModule used for validation and may lack many "project" assets.

A temporary workaround was put into 6.3.x (Community) to prevent the lookup of a KieModule from KieRepository during "project" build, but after discussion with mfusco it is considered a temporary solution.

Ideally the KieBuilder used for "asset validation" should use a transient ReleaseId (i.e. manipulate the pom.xml to have a different G, A or V, e.g. append -<userId>-<sessionId> etc and remove the transient KieModule from KieRepository after validation has been performed.




Version-Release number of selected component (if applicable):

6.3.x (Community)

How reproducible:


Note You need to log in before you can comment on or make changes to this bug.