Bug 843435 - RuntimeDroolsException, Invalid package name does not indicate which package name is invalid.
RuntimeDroolsException, Invalid package name does not indicate which package ...
Status: NEW
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor) (Show other bugs)
5.0.1
All All
unspecified Severity medium
: ---
: ---
Assigned To: Tihomir Surdilovic
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-26 06:30 EDT by James Read
Modified: 2012-10-17 05:57 EDT (History)
1 user (show)

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


Attachments (Terms of Use)

  None (edit)
Description James Read 2012-07-26 06:30:48 EDT
Description of problem:

After deploying rule flows to guvnor and building the package, Guvnor throws the following exception: 

- org.drools.RuntimeDroolsException: invalid package name

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

Appears to be version 5.1, although I'm not sure how to check. 

How reproducible:

Always (if there is an invalid package name). 

Steps to Reproduce:
1. Deploy a package with an invalid package name. 
  
Actual results:

An exception which is pretty useless.

Expected results:

An exception which is useful, that at least contains the package name that is invalid, along with the file the the package is defined in. 

Here is the stacktrace, so you can find where the exception is being thrown: 

11:05:14,350 ERROR [STDERR] org.drools.RuntimeDroolsException: invalid package name
11:05:14,350 ERROR [STDERR] 	at org.jbpm.compiler.ProcessBuilderImpl.buildProcess(ProcessBuilderImpl.java:173)
11:05:14,350 ERROR [STDERR] 	at org.jbpm.compiler.ProcessBuilderImpl.addProcessFromXml(ProcessBuilderImpl.java:252)
11:05:14,350 ERROR [STDERR] 	at org.drools.compiler.PackageBuilder.addProcessFromXml(PackageBuilder.java:620)
11:05:14,350 ERROR [STDERR] 	at org.drools.compiler.PackageBuilder.addProcessFromXml(PackageBuilder.java:633)
11:05:14,350 ERROR [STDERR] 	at org.drools.compiler.PackageBuilder.addRuleFlow(PackageBuilder.java:605)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.contenthandler.RuleFlowHandler.compile(RuleFlowHandler.java:198)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.builder.PackageAssemblerBase.compile(PackageAssemblerBase.java:74)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.builder.PackageAssemblerBase.buildAsset(PackageAssemblerBase.java:58)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.builder.PackageAssembler.addAsset(PackageAssembler.java:99)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.builder.PackageAssembler.loadAllButDRLAssets(PackageAssembler.java:83)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.builder.PackageAssembler.loadAssets(PackageAssembler.java:73)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.builder.PackageAssembler.buildPackage(PackageAssembler.java:65)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.builder.PackageAssembler.compile(PackageAssembler.java:55)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.RepositoryPackageOperations.buildPackage(RepositoryPackageOperations.java:571)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.RepositoryPackageOperations.buildPackage(RepositoryPackageOperations.java:542)
11:05:14,350 ERROR [STDERR] 	at org.drools.guvnor.server.RepositoryPackageService.buildPackage(RepositoryPackageService.java:343)

<SNIP>
Comment 2 James Read 2012-10-17 05:10:26 EDT
I notice the status was set to "needinfo". What further information would you like?
Comment 3 Lukáš Petrovický 2012-10-17 05:57:01 EDT
(In reply to comment #2)
> I notice the status was set to "needinfo". What further information would
> you like?

See comment 1 - the issue had been reported against BRMS 5.1, which is now over 2 years old. Can we reproduce it on a recent release, such as 5.3?

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