[JBoss JIRA] Created: (JBRULES-445) behavior of globals?
by G£bor Lipt£k (JIRA)
behavior of globals?
--------------------
Key: JBRULES-445
URL: http://jira.jboss.com/jira/browse/JBRULES-445
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.0.4
Reporter: G£bor Lipt£k
Assigned To: Mark Proctor
Priority: Minor
It seems that the value of DRL globals without external env backup is removed between rules:
package globaltest
import Policy;
global java.lang.String text;
rule "Foo"
salience 999
when
Policy()
then
text="foo";
System.out.println("foo+"+text);
end
rule "Bar"
salience 998
when
Policy()
then
System.out.println("bar+"+text);
text="bar";
System.out.println("bar+"+text);
end
results in:
foo+foo
bar+null
bar+bar
The documentation does not seem to provide details if this is the expected behavior.
Please comment. Thanks
--
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
19 years
[JBoss JIRA] Created: (JBRULES-520) How to refer one rule in another
by Sridhar Ramaswamy (JIRA)
How to refer one rule in another
--------------------------------
Key: JBRULES-520
URL: http://jira.jboss.com/jira/browse/JBRULES-520
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.4
Environment: WSAD
Reporter: Sridhar Ramaswamy
Assigned To: Mark Proctor
I have the following three rules created in a drl:
rule "Sales"
when
abc: abcData( $abcName : abcName,
$value: value > 20)
then
abc.setFlagColor("RED");
end
rule "Count"
when
bcd: bcdData( $bcdName : bcdName,
$count: count < 120)
then
abc.setFlagColor("RED");
end
How to create a new rule which will use these rules, for instance
rule "sales & count"
when
either rule "sales" is true or "count" is true
and
aaa: aaaData($aaaName: aaaName, $amount: amount < 1000)
then
aaa.setFlag("Critical");
end
I am not able to call a rule into another rule to check that is also true.
Thanks/Sri.
--
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
19 years
[JBoss JIRA] Created: (JBBUILD-332) Anonymous implementation of abstract methods in enums causes Weaver to barf
by Manik Surtani (JIRA)
Anonymous implementation of abstract methods in enums causes Weaver to barf
---------------------------------------------------------------------------
Key: JBBUILD-332
URL: http://jira.jboss.com/jira/browse/JBBUILD-332
Project: JBoss Build System
Issue Type: Bug
Components: JBossRetro
Affects Versions: JBossRetro-1.0.4.GA
Environment: Tested with JBoss Retro snapshot (10 Jan 2007) as well as 1.0.4.GA
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode, sharing)
Linux hobbes 2.6.18-1.2869.fc6xen #1 SMP Wed Dec 20 15:28:06 EST 2006 i686 i686 i386 GNU/Linux
Reporter: Manik Surtani
For example, see
http://fisheye.jboss.com/browse/~raw,r=1.7/JBoss/JBossCache/src/org/jboss...
When attempting to retroweave this enum, we see an NPE trying to get a hold of the enums in the class.
[retro] Attempting to retroweave class org.jboss.cache.lock.IsolationLevel$1
[retro] Exception in thread "main" java.lang.NullPointerException
[retro] at org.jboss.ant.tasks.retro.Weaver.rewriteEnum(Weaver.java:581)
[retro] at org.jboss.ant.tasks.retro.Weaver.doWeave(Weaver.java:463)
[retro] at org.jboss.ant.tasks.retro.Weaver.compileFile(Weaver.java:415)
[retro] at org.jboss.ant.tasks.retro.Weaver.weave(Weaver.java:328)
[retro] at org.jboss.ant.tasks.retro.Weaver.main(Weaver.java:110)
(I added the sys out in my local copy of Weaver.java to spit out the name of the offending class)
--
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
19 years
[JBoss JIRA] Created: (EJBTHREE-657) StatefulBean passivation is broken (ClassCastException in org.jboss.ejb3.stateful.NestedStatefulBeanContext)
by Carlo de Wolf (JIRA)
StatefulBean passivation is broken (ClassCastException in org.jboss.ejb3.stateful.NestedStatefulBeanContext)
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-657
URL: http://jira.jboss.com/jira/browse/EJBTHREE-657
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC8 - FD
Reporter: Carlo de Wolf
Priority: Critical
StatefulBean passivation is broken, because there is a conflict between what gets serialized (attribute contains) and what gets unserialized (attribute beanMO).
11:41:37,109 ERROR [STDERR] Caused by: java.lang.ClassCastException: java.util.ArrayList
11:41:37,109 ERROR [STDERR] at org.jboss.ejb3.stateful.NestedStatefulBeanContext.readExternal(Neste
dStatefulBeanContext.java:60)
11:41:37,109 ERROR [STDERR] at org.jboss.serial.persister.ExternalizePersister.readData(Externalize
Persister.java:72)
11:41:37,109 ERROR [STDERR] at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectD
escriptionFromStreaming(ObjectDescriptorFactory.java:411)
11:41:37,109 ERROR [STDERR] at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromD
escription(ObjectDescriptorFactory.java:81)
11:41:37,109 ERROR [STDERR] at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectIn
put.readObject(DataContainer.java:639)
11:41:37,109 ERROR [STDERR] at org.jboss.serial.persister.ObjectInputStreamProxy.readObjectOverride
(ObjectInputStreamProxy.java:68)
11:41:37,109 ERROR [STDERR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:333)
11:41:37,109 ERROR [STDERR] at java.util.ArrayList.readObject(ArrayList.java:592)
11:41:37,109 ERROR [STDERR] ... 74 more
--
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
19 years
[JBoss JIRA] Created: (JBMESSAGING-511) JDBC and Transaction close/cleanup operations should be bullet-proofed JDBCChannelMapper and elsewhere.
by Joel Lindheimer (JIRA)
JDBC and Transaction close/cleanup operations should be bullet-proofed JDBCChannelMapper and elsewhere.
-------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-511
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-511
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.0.1.CR4
Environment: Windows
Reporter: Joel Lindheimer
Assigned To: Ovidiu Feodorov
I am concerned with object close and wrap.end() methods in JDBCChannelMapper possibly being bypassed if an exception is thrown in the rs.close(), ps.close() blocks (code below is an example of what is currently in the JDBCChannelMapper).
JDBCChannelMapper :
public DurableSubscription getDurableSubscription(String clientID, String subscriptionName, MessageStore ms, PersistenceManager pm, MemoryManager mm) throws Exception {
// Look in memory first
DurableSubscription sub = getDurableSubscription(clientID, subscriptionName);
if (sub != null) {
return sub;
}
//Now look in the db
Connection conn = null;
PreparedStatement ps = null;
ResultSet rs = null;
TransactionWrapper wrap = new TransactionWrapper();
try {
conn = ds.getConnection();
ps = conn.prepareStatement(selectDurableSub);
(do stuff here... )
return sub;
} finally {
if (rs != null) { // JL what if it blose up here?
rs.close();
}
if (ps != null) { // JL or here?
ps.close();
}
if (conn != null) { // or here?
conn.close();
}
wrap.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
19 years, 1 month