[JBoss JIRA] Created: (JBRULES-589) WokingMemoryLogger and generics: ClassCastException
by Francesco Dandrea (JIRA)
WokingMemoryLogger and generics: ClassCastException
---------------------------------------------------
Key: JBRULES-589
URL: http://jira.jboss.com/jira/browse/JBRULES-589
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.5
Environment: Java 1.5.0_9
Reporter: Francesco Dandrea
Assigned To: Mark Proctor
Attachments: BacoJBossRules.zip
I'm using Jboss Rules 3.0.5 and Java 1.5.0_09.
I'm using generics, but I see that I can't have the character < in a Fact in te drl. This is not a problem, I derived my generic class, and the new derived one is not a Generic class...
(public class MyClassCiccio extends Ciccio<MyClass>{})
Now, when I execute the application without log it works. But when I instantiate a WorkingMemoryLogger I have a ClassCastException:
Exception in thread "main" java.lang.ClassCastException: it.telecomitalia.netbox.MeasureAlarm
at org.drools.base.it.telecomitalia.netbox.TfAlarm$getReferencedElement.getValue(Unknown Source)
at org.drools.base.ClassFieldExtractor.getValue(Unknown Source)
at org.drools.rule.Declaration.getValue(Unknown Source)
at org.drools.audit.WorkingMemoryLogger.extractDeclarations(Unknown Source)
at org.drools.audit.WorkingMemoryLogger.activationCreated(Unknown Source)
at org.drools.event.AgendaEventSupport.fireActivationCreated(Unknown Source)
at org.drools.reteoo.TerminalNode.assertTuple(Unknown Source)
at org.drools.reteoo.TerminalNode.assertTuple(Unknown Source)
at org.drools.reteoo.TupleSource.propagateAssertTuple(Unknown Source)
at org.drools.reteoo.NotNode.assertTuple(Unknown Source)
at org.drools.reteoo.LeftInputAdapterNode.createAndAssertTuple(Unknown Source)
at org.drools.reteoo.LeftInputAdapterNode.assertObject(Unknown Source)
at org.drools.reteoo.ObjectSource.propagateAssertObject(Unknown Source)
at org.drools.reteoo.ObjectTypeNode.assertObject(Unknown Source)
at org.drools.reteoo.Rete.assertObject(Unknown Source)
at org.drools.reteoo.ReteooRuleBase.assertObject(Unknown Source)
at org.drools.reteoo.ReteooWorkingMemory.doAssertObject(Unknown Source)
at org.drools.common.AbstractWorkingMemory.assertObject(Unknown Source)
at org.drools.common.AbstractWorkingMemory.assertObject(Unknown Source)
at it.telecomitalia.netbox.Main.main(Main.java:34)
I have an example (sent to the mailing list) that gives the exception, but
--
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: (JBMESSAGING-761) Consider clean ways of taking a node out of the cluster for maintenance
by Tim Fox (JIRA)
Consider clean ways of taking a node out of the cluster for maintenance
-----------------------------------------------------------------------
Key: JBMESSAGING-761
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-761
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Fix For: 1.2.1
We should consider how the system administrator can take a node out of the cluster for maintenance without clients losing messages.
If a node is just shut down then any clients connected to that node will failover to another node, potentially losing any non persistent messages - this may not be acceptable.
We should also consider functionality on the jmx console where a server cen block the creation of any new connections, and the information such as client machine name, client id, ip address can be displayed for existing connetions. This would allow the sysadmin to contact the clients and shut them down cleanly before bringing the server down.
--
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-140) Configurator should check that fields/methods exist before trying to use them
by Adrian Brock (JIRA)
Configurator should check that fields/methods exist before trying to use them
-----------------------------------------------------------------------------
Key: JBMICROCONT-140
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-140
Project: JBoss MicroContainer
Issue Type: Bug
Components: Configurator
Affects Versions: JBossMC_2_0_0 Beta
Reporter: Adrian Brock
Assigned To: Ales Justin
Fix For: JBossMC_2_0_0_CR1
Make sure the configurator is throwing reasonable error messages (not NPE)
when things are null.
e.g. the following method needs to check for null method info meaning there is no getter
public static TargettedJoinpoint getPropertyGetterJoinPoint(boolean trace, PropertyInfo info) throws Throwable
{
if (trace)
log.trace("Get property setter join point info=" + info);
if (info == null)
throw new IllegalArgumentException("Null property info");
JoinpointFactory jpf = info.getBeanInfo().getJoinpointFactory();
MethodInfo minfo = info.getGetter();
+ if (minfo == null)
+ throw new IllegalArgumentException("Property is write only");
return getMethodJoinpoint(null, jpf, minfo.getName(), null, null);
}
--
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: (JBRULES-699) syntactically correct rule files are marked with errors
by Dr. Gernot Starke (JIRA)
syntactically correct rule files are marked with errors
-------------------------------------------------------
Key: JBRULES-699
URL: http://jira.jboss.com/jira/browse/JBRULES-699
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Affects Versions: 3.0.5, 3.0.4
Environment: Eclipse 3.2, both on Mac OS X and Windows XP
Reporter: Dr. Gernot Starke
Assigned To: Mark Proctor
Although rule-files are syntactically correct (tutorial example), parser within Eclipse plugin marks them as erroneous. Deleting the rule, re-typing it in editor resolves the problem. Example (displays error in eclipse package explorer):
#created on: 14.02.2007
package com.sample.business
#list any import classes here.
import com.sample.Person;
import java.util.ArrayList;
#declare any global variables here
global ArrayList zorglist;
rule "erwachsene Person bekommt Kredit"
when
person: Person( age >= 18 )
then
System.out.println("Erwachsener in Sicht: " + person.getName());
zorglist.add( person.getName());
end
rule "no credit"
when
Person( personName : name, age < 18)
then
System.out.println( "denied for " + personName );
end
--
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