I think this is a misunderstanding. The Drools MBeans do not show imported packages... they show packages created by the engine when compiling rules.

Using the provided DRL as an example:

=====
package org.jboss.qa.brms.jmx

import org.jboss.qa.brms.jmx.pkg1.SomeFact
import org.jboss.qa.brms.jmx.pkg1.SomeOtherFact

import org.jboss.qa.brms.jmx.pkg2.*

declare SomeFact
	@role(event)
end

declare EmptyFact
	@role(event)
end

<rules>
=====

Because the file was declared as part of package "org.jboss.qa.brms.jmx", the engine will create a package object with that name to store all the rules, as well, as any additional data necessary (like type declarations for new facts in that package, etc).

If you take any existing class from a different package and declare metadata for it (in the above example, org.jboss.qa.brms.jmx.pk1.SomeFact and org.jboss.qa.brms.jmx.pkg2.EmptyFact are declared with @role(event)), then the engine creates the corresponding package objects to store that metadata.

Now, if one imports and use classes from package a.b.c, but does not declare any metadata for those classes, and drools does not need to store any compilation data for them, there is no reason for drools to create package objects for them, and so drools won't do it.

The actual import statements are just compile time information for the engine to find referenced classes, but they don't generate any visible entity by themselves.

Let me know if this clarifies the issue or if I am missing something.

Thanks

Please verify the issue on 5.3 ER4.

Yes, this clarifies it. The "issue" is verified.

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.