February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-197) Multiple recovery timeouts in property file

by Mark Little (JIRA)

Multiple recovery timeouts in property file ------------------------------------------- Key: JBTM-197 URL: http://jira.jboss.com/jira/browse/JBTM-197 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.2 Reporter: Mark Little Assigned To: Kevin Conner Fix For: 4.2.3 The following properties appear multiple times in the jbossjta-properties.xml file (there may be other duplicates I haven't noticed): <property name="com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod" value="120"/>  <property name="com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod" value="10"/>  -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-184) Change default context propagation behaviour to always propagate when in JBossAS

by Mark Little (JIRA)

Change default context propagation behaviour to always propagate when in JBossAS -------------------------------------------------------------------------------- Key: JBTM-184 URL: http://jira.jboss.com/jira/browse/JBTM-184 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, JTA Implementation, JTS Implementation Affects Versions: 4.2.2 Reporter: Mark Little Assigned To: Kevin Conner Fix For: 4.2.3 -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-196) TransactionManagerService exposed attributes should be RW

by Dimitris Andreadis (JIRA)

TransactionManagerService exposed attributes should be RW --------------------------------------------------------- Key: JBTM-196 URL: http://jira.jboss.com/jira/browse/JBTM-196 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Reporter: Dimitris Andreadis Assigned To: Kevin Conner Fix For: 4.2.3 The following attributes on the jbossTS transaction manager should really be readable, too: TransactionTimeout RunInVMRecoveryManager ObjectStoreDir com.arjuna.ats.jbossatx.jta.TransactionManagerService -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-186) Allow configuration of ObjectStoreDir location through the jboss integration layer

by Dimitris Andreadis (JIRA)

Allow configuration of ObjectStoreDir location through the jboss integration layer ---------------------------------------------------------------------------------- Key: JBTM-186 URL: http://jira.jboss.com/jira/browse/JBTM-186 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Assigned To: Mark Little Priority: Critical Fix For: 4.2.3 Need to be able to configure the location of the ObjectStore dir, through JBoss config files. Normally it should be something like: ${jboss.server.data.dir}/tx-object-store If this could be done in the separate integration library without releasing a new jbossts version, that would be great, because we would really need this feature for the first jbossAS 4.2.0.CR1 release. We just can't write to the /bin directory. -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Commented: (JBRULES-261) Mismatched types in field constraints

by Mark Proctor (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-261?page=comments#action_12352622 ] Mark Proctor commented on JBRULES-261: -------------------------------------- automatic conversion, where appropriate would be good. i.e string/char long/int/float etc. > Mismatched types in field constraints > ------------------------------------- > > Key: JBRULES-261 > URL: http://jira.jboss.com/jira/browse/JBRULES-261 > Project: JBoss Rules > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rule Assemply/SPI > Affects Versions: 3.0.1 > Reporter: Michael Neale > Assigned To: Mark Proctor > Priority: Minor > Fix For: 3.1-m2 > > > Problem: If a rule compares two fields and one of them is a char and the > other one is a String, the match is always negative. No type-mismatch error > or warning is displayed. This can be quite confusing. The attached Eclipse > project illustrates this problem. > Suggested Solution: If all information is available at compile-time an error > should be generated on type mismatches. Otherwise there should be a warning > during run-time and maybe a type conversion attempt. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-498) Optimised HashMap implementations

by Mark Proctor (JIRA)

Optimised HashMap implementations --------------------------------- Key: JBRULES-498 URL: http://jira.jboss.com/jira/browse/JBRULES-498 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 Create a HashMap implementation that is optimised for holding ReteTuples and also for indexing FactHandles by field index and value, -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-531) move LEAPS to its own module

by Mark Proctor (JIRA)

move LEAPS to its own module ----------------------------- Key: JBRULES-531 URL: http://jira.jboss.com/jira/browse/JBRULES-531 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Leaps Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 We can't rely on leaps being maintained regularly, so we need to move it to its own module. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-645) Providing xml schema or dtd for configuration validation

by Galder Zamarreno (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-645?page=all ] Galder Zamarreno resolved JBCACHE-645. -------------------------------------- Resolution: Deferred > Providing xml schema or dtd for configuration validation > -------------------------------------------------------- > > Key: JBCACHE-645 > URL: http://jira.jboss.com/jira/browse/JBCACHE-645 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.SP2 > Reporter: Galder Zamarreno > Assigned To: Galder Zamarreno > Fix For: 2.1.0.GA > > > It'd be nice if JBossCache could distribute an XML schema or dtd > that would allow for configuration to be validated before JBossCache > was actually deployed or started. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-526) Implement a CompositeIndex for Facts

by Mark Proctor (JIRA)

Implement a CompositeIndex for Facts -------------------------------------- Key: JBRULES-526 URL: http://jira.jboss.com/jira/browse/JBRULES-526 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 Manners works faster with a composite index, so create a lightweight indexing solution. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-496) Sequential Accessor for the Action Language.

by Mark Proctor (JIRA)

Sequential Accessor for the Action Language. -------------------------------------------- Key: JBRULES-496 URL: http://jira.jboss.com/jira/browse/JBRULES-496 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 -- 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, 3 months

1
1
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 February 2007