November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBRULES-232) if variable is bound to multiple columns, that should mean an implicit join on identity

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-232?page=comments#action_12347664 ] Michael Neale commented on JBRULES-232: --------------------------------------- best not to count on that always working, as it maybe/will be deprecated. the implicit joining is a legacy from Jess, where it makes sense in the lisp style syntax. The other way it can work is by not removing same id combinations, in which case all combos are tried (even joining with itself). That would be like Jess and JRules. > if variable is bound to multiple columns, that should mean an implicit join on identity > --------------------------------------------------------------------------------------- > > Key: JBRULES-232 > URL: http://jira.jboss.com/jira/browse/JBRULES-232 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Affects Versions: 3.0-rc2 > Reporter: Michael Neale > Assigned To: Mark Proctor > Fix For: 3.1-m3 > > > This is based on some discussions on the mailling list. > So: > m : Message(foo == "bar") > m : Message(foo != "42") > should be the same as > m : Message(foo == "bar", foo != 42) > this works as the same variable is "bound" each time. At the moment it rebinds. > The "new" behaviour should be consistent with Jess, and it does indeed make things simpler from a users point of view, and DSLs much more powerful. > Obviously if nothing it bound, then it is just as normal. > It *may* be possible to do this entirely in the parser, not sure at this stage... further investigation required. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-645) Testing: JBMessaging XARecovery integration with JBossAS and JBossTS

by Juha Lindfors (JIRA)

Testing: JBMessaging XARecovery integration with JBossAS and JBossTS -------------------------------------------------------------------- Key: JBMESSAGING-645 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-645 Project: JBoss Messaging Issue Type: Sub-task Components: AS Integration Reporter: Juha Lindfors Assigned To: Juha Lindfors Fix For: 1.0.2.CR1 Test messaging XARecovery thru integration with JBossAS where both JBMessaging and JBTransactions are deployed as services to AS. This should utilize the existing JMSProviderXAResourceRecovery implementation. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBRULES-232) if variable is bound to multiple columns, that should mean an implicit join on identity

by John Cocktolstoy (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-232?page=comments#action_12347661 ] John Cocktolstoy commented on JBRULES-232: ------------------------------------------ Hi, I am constructing rules directly using API instead of DRL files. Actually I am using feature described here - I am binding many columns to the same variable and it works fine. Hence it is *very likely* that it may be done enirely in the parser. regards John C. > if variable is bound to multiple columns, that should mean an implicit join on identity > --------------------------------------------------------------------------------------- > > Key: JBRULES-232 > URL: http://jira.jboss.com/jira/browse/JBRULES-232 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Affects Versions: 3.0-rc2 > Reporter: Michael Neale > Assigned To: Mark Proctor > Fix For: 3.1-m3 > > > This is based on some discussions on the mailling list. > So: > m : Message(foo == "bar") > m : Message(foo != "42") > should be the same as > m : Message(foo == "bar", foo != 42) > this works as the same variable is "bound" each time. At the moment it rebinds. > The "new" behaviour should be consistent with Jess, and it does indeed make things simpler from a users point of view, and DSLs much more powerful. > Obviously if nothing it bound, then it is just as normal. > It *may* be possible to do this entirely in the parser, not sure at this stage... further investigation required. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-566) Not-Constraint is not working properly

by Michael Frandsen (JIRA)

Not-Constraint is not working properly -------------------------------------- Key: JBRULES-566 URL: http://jira.jboss.com/jira/browse/JBRULES-566 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.4 Environment: WinXP, eclipse 3.2.0, JBoss Rules IDE 3.0.4 Reporter: Michael Frandsen Assigned To: Mark Proctor Attachments: Element.java "Not"-Constraints are not evaluated like expected. See following example: rule "Not is not correct working rule" when Element ( $a : a, $b : b, $c : c ) not( Element (a == $a) ) then System.out.println( "rule fired" ); end Asserted Facts: workingMemory.assertObject( new Element(1,1,2) ); //a,b,c workingMemory.assertObject( new Element(2,2,3) ); //a,b,c The second element is not having the same a, so rule should fire two times, but it is not. -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-145) Addd session passivation docs

by Hany Mesha (JIRA)

Addd session passivation docs ----------------------------- Key: JBCLUSTER-145 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-145 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: Q3Y6 Reporter: Hany Mesha Assigned To: Hany Mesha Fix For: Q3Y6 Add session passivation docs to the AS Guide. The docs will include introduction to session passivation for http session replication and how to enable session passivation. Conditions and limition on the cache configuration with session passivation such as cache loader store should always be non-sharable among cluster nodes. Also a wiki page to explain session passivation for http session replication and FAQs -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBPM-165) process instance versioning

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-165?page=all ] Tom Baeyens updated JBPM-165: ----------------------------- Fix Version/s: jBPM 3.2 i'll try to get it in for 3.2 but it might move to 3.3. so don't get your hopes up too high yet :-) > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: http://jira.jboss.com/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM 3.2 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3881) Extend the EmailAlertListener to be a real Notification listener

by Dimitris Andreadis (JIRA)

Extend the EmailAlertListener to be a real Notification listener ---------------------------------------------------------------- Key: JBAS-3881 URL: http://jira.jboss.com/jira/browse/JBAS-3881 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management services Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis The EmailAlertListener is a bit missleading, it doesn't listen for Notification, rather it waits for Notification to be pushed to it in order to email them. Also it accepts a particular type of notification. A nice feature would be to make it a real listener, so it can subscribe to the MemoryMonitor, for example, and be able to email any type of notification. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-562) Disable cache loader when no cacheloader class is specified

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-562?page=comments#action_12347643 ] Brian Stansberry commented on JBCACHE-562: ------------------------------------------ Not quite as simple with the pojo-based configuration in 2.0, since the cacheloader class is an inherent property of the typed config object. The config object should probably have an "enabled" property. The "empty class" idea could still work for parsing 1.x-style configs, though. If class is empty, parser doesn't create the config pojo, and thus no cacheloader is created. > Disable cache loader when no cacheloader class is specified > ----------------------------------------------------------- > > Key: JBCACHE-562 > URL: http://jira.jboss.com/jira/browse/JBCACHE-562 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.0.0.GA > > > In 1.3, we support a new form of cacheloader config. However, it is incovenient to disable the cache loader (previously all we need is to specify cacheloaderclass to empty). We should also support this kind of semantics so we can disable it easily. I propose when do createcacheloader, we also check whether the class name is there or not to decide whether to go ahead. If not, we simply log an info message. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-562) Disable cache loader when no cacheloader class is specified

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-562?page=all ] Brian Stansberry updated JBCACHE-562: ------------------------------------- Summary: Disable cache loader when no cacheloader class is specified (was: Disable cache loader when no classloader class is specified) Description: In 1.3, we support a new form of cacheloader config. However, it is incovenient to disable the cache loader (previously all we need is to specify cacheloaderclass to empty). We should also support this kind of semantics so we can disable it easily. I propose when do createcacheloader, we also check whether the class name is there or not to decide whether to go ahead. If not, we simply log an info message. (was: In 1.3, we support a new form of classloader config. However, it is incovenient to disable the cache loader (previously all we need is to specify cacheloaderclass to empty). We should also support this kind of semantics so we can disable it easily. I propose when do createcacheloader, we also check whether the class name is there or not to decide whether to go ahead. If not, we simply log an info message.) > Disable cache loader when no cacheloader class is specified > ----------------------------------------------------------- > > Key: JBCACHE-562 > URL: http://jira.jboss.com/jira/browse/JBCACHE-562 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.0.0.GA > > > In 1.3, we support a new form of cacheloader config. However, it is incovenient to disable the cache loader (previously all we need is to specify cacheloaderclass to empty). We should also support this kind of semantics so we can disable it easily. I propose when do createcacheloader, we also check whether the class name is there or not to decide whether to go ahead. If not, we simply log an info message. -- 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, 8 months

1
0
0 / 0

Government Funding Available

by cbookshop1＠mail.com

Press Release The American Grants and Loans Book is now available. This publication contains valuable information with more than 1500 financial programs, subsidies, scholarships, grants and loans offered by the United States federal government. It also includes over 700 financing programs put forth by various Foundations and Associations across the United States. Businesses, students, individuals, municipalities, government departments, institutions, foundations and associations will find a wealth of information that will help them with their new ventures or existing projects. What you get: -Description of Grant available -Url to government website -Full mailing address -Phone and fax number The Canadian Subsidy Directory is also available for Canada. CD version: $69.95 Printed version: $149.95 To order please call: 819-322-7533 If you do not wish to receive communication from us in the future please write "agl" in the subject line to: rem(a)call.org %%*ADVERTISEMENT%%* Canada Books 833 Boise de la Riviere Prevost, Qc Canada

19 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006