August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1061) jsr94 constants wrong package builder config constant, same name as rulebase config constant

by Juergen none (JIRA)

jsr94 constants wrong package builder config constant, same name as rulebase config constant -------------------------------------------------------------------------------------------- Key: JBRULES-1061 URL: http://jira.jboss.com/jira/browse/JBRULES-1061 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSR94 Affects Versions: 4.0.0.GA Reporter: Juergen none Assigned To: Mark Proctor Priority: Minor org.drools.jsr94.rules.Constants, line 49f: /** <code>RuleExecutionSet</code> rulebase config constant. */ public static final String RES_RULEBASE_CONFIG = "javax.rules.admin.RuleExecutionSet.ruleBaseConfiguration"; /** <code>RuleExecutionSet</code> package builder config constant. */ public static final String RES_PACKAGEBUILDER_CONFIG = "javax.rules.admin.RuleExecutionSet.ruleBaseConfiguration"; Packagebuilder config constant is same as rulebase config constant. yields classcast exception if a rulebase config is set: Caused by: java.lang.ClassCastException: org.drools.RuleBaseConfiguration at org.drools.jsr94.rules.admin.LocalRuleExecutionSetProviderImpl.createRuleExecutionSet(LocalRuleExecutionSetProviderImpl.java:124) at org.drools.jsr94.rules.admin.LocalRuleExecutionSetProviderImpl.createRuleExecutionSet(LocalRuleExecutionSetProviderImpl.java:93) -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1067) Allow RuleAgent to take a RuleBaseConfiguration to configure the RuleBase it creates

by Shahad Ahmed (JIRA)

Allow RuleAgent to take a RuleBaseConfiguration to configure the RuleBase it creates ------------------------------------------------------------------------------------ Key: JBRULES-1067 URL: http://jira.jboss.com/jira/browse/JBRULES-1067 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.0.GA Environment: Windows XP, Sun JRE 1.5_09 Reporter: Shahad Ahmed Assigned To: Mark Proctor Extend the API to allow a RuleAgent to use a RuleBaseConfiguration object to configure the RuleBase it creates. For example, this will allow a user to specfiy options like Sequental mode etc when creating a RuleBase using a RuleAgent. I know that you can set RuleBase options for all RuleBases by setting the appropriate System properties when calling the java VM, but it would be nice to be able to set these individually via the API for each RuleBase created using a RuleAgent. I guess this could be done fairly easily by adding an extra constructor(s) to RuleAgent that takes a RuleBaseConfiguration object -- rbConfig, say -- and in RuleAgent when it creates a new RuleBase instead of just using RulebaseFactory.newRuleBase() use RulebaseFactory.newRuleBase(rbConfig) instead. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-992) Give wiki pages a facelift

by Tim Fox (JIRA)

Give wiki pages a facelift -------------------------- Key: JBMESSAGING-992 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-992 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.4.0.CR1 The current wiki pages - both user and development contain outdated information. We should update info, and add new content as necessary. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Resolved: (BPEL-175) reintroduce assignment to/from variable/part/query

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-175?page=all ] Alejandro Guizar resolved BPEL-175. ----------------------------------- Fix Version/s: jBPM BPEL 1.1 GA (was: jBPM BPEL 1.1 beta 1) Resolution: Done AssignReader now parses the BPEL 2 syntax. > reintroduce assignment to/from variable/part/query > -------------------------------------------------- > > Key: BPEL-175 > URL: http://jira.jboss.com/jira/browse/BPEL-175 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Environment: dom, trax > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 GA > > > Item 103 of the BPEL issues list (http://www.choreology.com/external/WS_BPEL_issues_list.html) proposed a new syntax to access process variables within XPath expressions. The original proposal eliminated the variable/part/query variant of from-spec and to-spec, so it was removed from the product. > After quite some discussion this variant remained valid. Therefore, the variant must be reintroduced. In fact this is a positive thing because it simplifies upgrading documents written against version 1.1 to version 2. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (BPEL-151) export the reference of the published endpoint

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-151?page=all ] Alejandro Guizar resolved BPEL-151. ----------------------------------- Resolution: Done > export the reference of the published endpoint > ---------------------------------------------- > > Key: BPEL-151 > URL: http://jira.jboss.com/jira/browse/BPEL-151 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 GA > > > Provide the endpoint reference of the process with respect to partner links. Implement its use as the source of assignment, as described in section 9.4 of the spec. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4597) CacheInvalidator.areInvalid doesn't lock partitions

by Alexey Loubyansky (JIRA)

CacheInvalidator.areInvalid doesn't lock partitions --------------------------------------------------- Key: JBAS-4597 URL: http://jira.jboss.com/jira/browse/JBAS-4597 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA, JBossAS-4.4.0.CR1 org.jboss.ejb.plugins.cmp.jdbc2.schema.CacheInvalidator.areInvalid(Serializable[] keys) uses cache.lock() before removing an instance. The lock() implementation in PartitionedTableCache is empty. It should either lock all the partitions or CacheInvalidator should lock the partition the key belongs to before the key is removed. -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1035) CLONE -deploy a process archive documentation incorrect

by liz ch (JIRA)

CLONE -deploy a process archive documentation incorrect ------------------------------------------------------- Key: JBPM-1035 URL: http://jira.jboss.com/jira/browse/JBPM-1035 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM 3.0.2 Reporter: liz ch Assigned To: Tom Baeyens Under section 13.1.1 - Deploying a proceses archive: The code sample for target name="deploy.par" is incorrect: The task definition rg.jbpm.jpdl.par.ProcessArchiveDeployerTask should be org.jbpm.ant.DeployParTask -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBPM-675) Able to kill and suspend a process or token that has ended

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-675?page=all ] Ronald van Kuijk updated JBPM-675: ---------------------------------- Affects Version/s: jBPM 3.1.1 > Able to kill and suspend a process or token that has ended > ---------------------------------------------------------- > > Key: JBPM-675 > URL: http://jira.jboss.com/jira/browse/JBPM-675 > Project: JBoss jBPM > Issue Type: Patch > Components: Core Engine > Affects Versions: jBPM 3.1.1 > Environment: Mac OS X 10.4.6 Java 1.4.2_09 > Reporter: michaelklem > Assigned To: Tom Baeyens > Priority: Trivial > Fix For: jBPM 3.1.5 > > > When a process instance or token has ended, I can still call the suspend, resume and kill APIs on that process instance or token without an exception being thrown. IMO an exception should be thrown to indicate that these APIs are used in an illegal state. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-675) Able to kill and suspend a process or token that has ended

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-675?page=all ] Ronald van Kuijk updated JBPM-675: ---------------------------------- Fix Version/s: jBPM 3.1.5 Affects Version/s: (was: jBPM 3.1.1) > Able to kill and suspend a process or token that has ended > ---------------------------------------------------------- > > Key: JBPM-675 > URL: http://jira.jboss.com/jira/browse/JBPM-675 > Project: JBoss jBPM > Issue Type: Patch > Components: Core Engine > Environment: Mac OS X 10.4.6 Java 1.4.2_09 > Reporter: michaelklem > Assigned To: Tom Baeyens > Priority: Trivial > Fix For: jBPM 3.1.5 > > > When a process instance or token has ended, I can still call the suspend, resume and kill APIs on that process instance or token without an exception being thrown. IMO an exception should be thrown to indicate that these APIs are used in an illegal state. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-675) Able to kill and suspend a process or token that has ended

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-675?page=comments#action_12371509 ] Ronald van Kuijk commented on JBPM-675: --------------------------------------- works on 3.2, should this still be fixed in 3.1? I assign it to 3.1.5, and see what happens > Able to kill and suspend a process or token that has ended > ---------------------------------------------------------- > > Key: JBPM-675 > URL: http://jira.jboss.com/jira/browse/JBPM-675 > Project: JBoss jBPM > Issue Type: Patch > Components: Core Engine > Environment: Mac OS X 10.4.6 Java 1.4.2_09 > Reporter: michaelklem > Assigned To: Tom Baeyens > Priority: Trivial > Fix For: jBPM 3.1.5 > > > When a process instance or token has ended, I can still call the suspend, resume and kill APIs on that process instance or token without an exception being thrown. IMO an exception should be thrown to indicate that these APIs are used in an illegal state. -- 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, 11 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 August 2007