April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-546) Please implement "collect( ... ) from" functionality

by Dirk Bergstrom (JIRA)

Please implement "collect( ... ) from" functionality ---------------------------------------------------- Key: JBRULES-546 URL: http://jira.jboss.com/jira/browse/JBRULES-546 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dirk Bergstrom Assigned To: Mark Proctor I need to count the number of sub-objects that meet various criteria. As an example, suppose I have several hundred Town objects, each of which has a list of perhaps a few hundred Person objects. I need to write rules like: "Find all the towns that have more than three disabled people with incomes over $100K." "For each town with more than 1000 residents that has more than 50 poor children under the age of 8, add a teacher for every 25 children." I'm shaky on JBR syntax, but I think those would translate to something like: rule "disabled" when ArrayList(size > 50) from collect( Person( disabled == "yes", income > 100000 ) from town.getPersons() ) then //do stuff end rule "teachers" when town : Town( population > 1000 ) count : Arraylist from collect( Person( disabled == "yes", income > 100000 ) from town.getPersons() ) count( size > 50 ) then town.addTeachers(count.size() / 25) end (I'm not really working with towns and people, but it makes for easily understood examples) -- 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

5
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-1022) All notifications should go thru the Notifier and Notification Interceptor

by Manik Surtani (JIRA)

All notifications should go thru the Notifier and Notification Interceptor -------------------------------------------------------------------------- Key: JBCACHE-1022 URL: http://jira.jboss.com/jira/browse/JBCACHE-1022 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-955) jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes)

by Arjan van Bentem (JIRA)

jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes) ---------------------------------------------------------------------------------- Key: JBPM-955 URL: http://jira.jboss.com/jira/browse/JBPM-955 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM jPDL 3.2 Environment: All Reporter: Arjan van Bentem Assigned To: Tom Baeyens Priority: Minor Currently, an Actor or Swimlane is assigned within the task definition. When using sub-processes it would be very convenient to make the assignments in the parent process, such as in the parent <process-state>, or maybe even in the outermost <process-definition>. For example: both a helpdesk employee and the customer would need to fill in the same questionnaire at different points in the main process. The steps to fill in the questionnaire would be a generic sub-process, in which (at design time) one would not know the Swimlane nor Actor. This would require a way to set the swimlane in the parent's process-state:  <process-state name="Customer survey" swimlane="client"> <sub-process name="survey" /> </process-state> : : <process-state name="Employee survey" swimlane="employer"> <sub-process name="survey" /> </process-state> ... or <process-state name="Employee survey"> <assignment actor-id="..."/> <sub-process name="survey" /> </process-state> ... or maybe even at an even higher level, where jBPM would iterate up into the chain, possibly though nested sub-processes, until some assignment is found? -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBRULES-543) Jboss rules doesnt seem to have a command to halt rule execution from within a rules RHS

by Sridhar Chandrasekharan (JIRA)

Jboss rules doesnt seem to have a command to halt rule execution from within a rules RHS ---------------------------------------------------------------------------------------- Key: JBRULES-543 URL: http://jira.jboss.com/jira/browse/JBRULES-543 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sridhar Chandrasekharan Assigned To: Mark Proctor Jboss rules doesnt seem to have a command to halt rule execution from within a rules RHS. Jess has a (halt) command which allows a rule to specify that rule execution should be stopped. I could find no such command in JBoss rules. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-492) Benchmark against JBento ATL cluster

by Bela Ban (JIRA)

Benchmark against JBento ATL cluster ------------------------------------ Key: JGRP-492 URL: http://jira.jboss.com/jira/browse/JGRP-492 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Run the same session replication benchmarks as for 2.4.1 SP3 against 2.5 -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4032) Restore jboss.partition.name property replacement in clustering beans.xml files

by Brian Stansberry (JIRA)

Restore jboss.partition.name property replacement in clustering beans.xml files ------------------------------------------------------------------------------- Key: JBAS-4032 URL: http://jira.jboss.com/jira/browse/JBAS-4032 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta2 Pending completion of JBMICRONTAINER-143, I removed syntax from like the following from the clustering -beans.xml files: <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=HASingletonDeploymentScanner,partitionName=${jboss.partition.name:DefaultPartition}", exposedInterface=org.jboss.ha.singleton.HASingletonDeploymentScannerMBean.class, registerDirectly= true)</annotation> This task is a reminder to restore it once the microcontainer issue is resolved. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-692) Create extended RunAs roles for additional mapped principals

by Bill Burke (JIRA)

Create extended RunAs roles for additional mapped principals ------------------------------------------------------------ Key: EJBTHREE-692 URL: http://jira.jboss.com/jira/browse/EJBTHREE-692 Project: EJB 3.0 Issue Type: Task Reporter: Bill Burke Fix For: EJB 3.0 RC10 - FD See the TODO in RunAsSecurityInterceptorFactory -- 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

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-702) Quartz Timer Service in E-EJB3 hangs process, exception on shutdown

by Bill Burke (JIRA)

Quartz Timer Service in E-EJB3 hangs process, exception on shutdown ------------------------------------------------------------------- Key: EJBTHREE-702 URL: http://jira.jboss.com/jira/browse/EJBTHREE-702 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Bill Burke Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC10 - FD to test this out: build embedded.dist go run one of the tutorials. You will see that the applicatoin will never exit. I'm guessing this is becuase a Quartz thread is a non-daemon thread and holding up the exit of the process. Also there is a NullPointerException on shutdown. I have disabled the Quartz Timer Service in embedded-jboss-beans.xml for now. -- 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

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-780) dlqmaxresent parameter is not taken from main jboss config

by Ramil Israfilov (JIRA)

dlqmaxresent parameter is not taken from main jboss config ---------------------------------------------------------- Key: EJBTHREE-780 URL: http://jira.jboss.com/jira/browse/EJBTHREE-780 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Ramil Israfilov Fix For: EJB 3.0 RC10 - FD During tests recovered JMS message goes immediatelly to DQL queue, in standardjboss.xml file dlqmaxresent parameter is set to 10, but it is not used. If I put this property in MDB as annotation it works, but I don't want to put it there as it is a parameter which can be set on jboss config. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-920) Be sure Hibernate EntityManager works with JBoss AS 4.2

by Emmanuel Bernard (JIRA)

Be sure Hibernate EntityManager works with JBoss AS 4.2 ------------------------------------------------------- Key: EJBTHREE-920 URL: http://jira.jboss.com/jira/browse/EJBTHREE-920 Project: EJB 3.0 Issue Type: Task Reporter: Emmanuel Bernard Assigned To: Emmanuel Bernard Fix For: AS 4.2.0 CR2 When you're close to release please ping me :-) -- 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

2
4
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 April 2007