[JBoss JIRA] Created: (JBRULES-593) Rule names must be globally unique, even if they come from different packages
by Jeff Lansing (JIRA)
Rule names must be globally unique, even if they come from different packages
-----------------------------------------------------------------------------
Key: JBRULES-593
URL: http://jira.jboss.com/jira/browse/JBRULES-593
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.0.5
Environment: NA
Reporter: Jeff Lansing
Assigned To: Mark Proctor
When 2 DRL rule files with different package names (the name following the 'package' keyword) each have a rule with the same name (the name being the quoted string that follows the 'rule' keyword), then the following exception occurs:
org.drools.rule.InvalidRulePackage: Rule Compilation error The type Rule_Incident__Vehicle_0 is already defined
at org.drools.rule.Package.checkValidity(Unknown Source)
at org.drools.common.AbstractRuleBase.addPackage(Unknown Source)
at driver.RulesTest.readRule(RulesTest.java:256)
This occurs when using a single org.drools.rule.Package object, as in:
private void test(Reader source1, Reader source2) throws Exception {
PackageBuilder builder = new PackageBuilder();
builder.addPackageFromDrl( source1 );
builder.addPackageFromDrl( source2 );
Package pkg = builder.getPackage();
RuleBase ruleBase = RuleBaseFactory.newRuleBase();
ruleBase.addPackage( pkg );
}
If, on the other hand two org.drools.rule.Package objects are used, as in:
private void test2(Reader source1, Reader source2) throws Exception {
PackageBuilder builder1 = new PackageBuilder();
PackageBuilder builder2 = new PackageBuilder();
builder1.addPackageFromDrl( source1 );
builder2.addPackageFromDrl( source2 );
Package pkg1 = builder1.getPackage();
Package pkg2 = builder2.getPackage();
RuleBase ruleBase = RuleBaseFactory.newRuleBase();
ruleBase.addPackage( pkg1 );
ruleBase.addPackage( pkg2 );
}
then one of the identically named rules is simply ignored.
In either case, rule names must be globally unique.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (EJBTHREE-827) creating timers inside start() creates duplicate timers.
by David Owens (JIRA)
creating timers inside start() creates duplicate timers.
--------------------------------------------------------
Key: EJBTHREE-827
URL: http://jira.jboss.com/jira/browse/EJBTHREE-827
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Environment: Windows 2000, JBoss 4.0.5 (jems installer), Java 1.5
Reporter: David Owens
Calling ctx.getTimerService().createTimer(...) within the start() method of a managed service bean creates duplicate timers. In other words, I have a bean which is both @Management and @Service which has a method which is @Timeout. In the start method of the bean (when the bean is deployed) I create a new timer. But then the method marked @Timeout is called twice. When I investigate the timers in by calling ctx.getTimerService().getTimers(), I find there are actually 2 timers with different ids, but with the exact same info.
I have attached an example. You will see the start() method getting called once when the bean is deployed, but then the timeout method getting called twice.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBMICROCONT-109) Support direct registration of beans without a StandardMBean wrapper
by Brian Stansberry (JIRA)
Support direct registration of beans without a StandardMBean wrapper
--------------------------------------------------------------------
Key: JBMICROCONT-109
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-109
Project: JBoss MicroContainer
Issue Type: Sub-task
Components: General
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossMC_2_0_0 Beta
If a bean is already a valid MBean, it should be possible to directly register it in JMX without wrapping it in a StandardMBean. Otherwise beans that implement things like MBeanRegistration, NotificationBroadcaster, NotificationEmitter will not expose that API to the mbean server.
To support this, @JMX will add an attribute:
boolean registerDirectly() default false;
JMXIntroduction will check the attribute; if true the target bean will be registered directly; otherwise a StandardMBean will be created and registered.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months