February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-665) Plain DSL based text editor

by Michael Neale (JIRA)

Plain DSL based text editor --------------------------- Key: JBRULES-665 URL: http://jira.jboss.com/jira/browse/JBRULES-665 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 2 months

1
1
0 / 0

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

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-261?page=comments#action_12352810 ] Michael Neale commented on JBRULES-261: --------------------------------------- defaintely automatic. We don't want to be as rigid with types as java is. Of course, if there is any "loss" of data resolution, that is a problem, but if there is not, then automatic is good. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-955) Restore ability to insert and remove child nodes with only a read lock on the parent

by Brian Stansberry (JIRA)

Restore ability to insert and remove child nodes with only a read lock on the parent ------------------------------------------------------------------------------------ Key: JBCACHE-955 URL: http://jira.jboss.com/jira/browse/JBCACHE-955 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.1.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Critical Fix For: 2.0.0.BETA1, 1.4.1.SP1 In 1.4.1.GA JBC introduced tighter locking semantics wherein the insertion or removal of a node required a write lock on the parent. In recent previous versions (and maybe always) only a read lock was required. The 1.4.1.GA behavior provides greater correctness, but at a cost of lesser concurrency. Some applications written assuming the old behavior will not function properly with the new behavior. Speaking in db isolation terms, let's say a non-repeatable-read means a tx reads a node's *data map* twice and gets different results. A phantom read means a tx reads a node's *child map* twice and gets different results. Conceptually, a JBC node represents both a "row" (data map) and a query result set (children map -- set of rows that share a common characteristic that the parent represents). (I know this analogy is inexact, but, ...). In 1.4.0.SP1, REPEATABLE_READ meant you wouldn't get non-repeatable-reads, but could get phantom reads. With 1.4.1, you also don't get phantom reads (at least with respect to a node's immediate children). But, in many cases this behavior is unneeded and undesirable, and JBC no longer offers the old behavior. This JIRA will restore the old behavior for the pessimistic locking use case. A new cache configuration flag LockParentForChildInsertRemove will be added. If set to false, the 1.4.0.SP1 behavior of only requiring the RL will be restored. The default value of the flag will be true. -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Commented: (JBBUILD-339) Enable viewing of long file names in directory lists on http://repository.jboss.com/maven2/

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-339?page=comments#action_12352806 ] Ryan Campbell commented on JBBUILD-339: --------------------------------------- Paul is the new build developer. > Enable viewing of long file names in directory lists on http://repository.jboss.com/maven2/ > ------------------------------------------------------------------------------------------- > > Key: JBBUILD-339 > URL: http://jira.jboss.com/jira/browse/JBBUILD-339 > Project: JBoss Build System > Issue Type: Task > Reporter: Charles Crouch > Assigned To: Paul Gier > > Looking at http://repository.jboss.com/maven2/jboss/jboss-logging-spi/2.0.3.GA/ its impossible to tell what files are actually there without mousing over them and seeing where the link goes, e.g. > [DIR] Parent Directory - > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 8.2K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 115 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 7.5K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 107 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 2.2K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 107 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > It should be possible to fix this following instructions similar to those discussed here: > http://www.networkworld.com/columnists/2006/051506internet.html -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBBUILD-339) Enable viewing of long file names in directory lists on http://repository.jboss.com/maven2/

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-339?page=all ] Ryan Campbell reassigned JBBUILD-339: ------------------------------------- Assignee: Paul Gier > Enable viewing of long file names in directory lists on http://repository.jboss.com/maven2/ > ------------------------------------------------------------------------------------------- > > Key: JBBUILD-339 > URL: http://jira.jboss.com/jira/browse/JBBUILD-339 > Project: JBoss Build System > Issue Type: Task > Reporter: Charles Crouch > Assigned To: Paul Gier > > Looking at http://repository.jboss.com/maven2/jboss/jboss-logging-spi/2.0.3.GA/ its impossible to tell what files are actually there without mousing over them and seeing where the link goes, e.g. > [DIR] Parent Directory - > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 8.2K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 115 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 7.5K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 107 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 2.2K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 107 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > It should be possible to fix this following instructions similar to those discussed here: > http://www.networkworld.com/columnists/2006/051506internet.html -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBBUILD-339) Enable viewing of long file names in directory lists on http://repository.jboss.com/maven2/

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-339?page=all ] Ryan Campbell moved JBQA-678 to JBBUILD-339: -------------------------------------------- Project: JBoss Build System (was: JBoss QA) Key: JBBUILD-339 (was: JBQA-678) > Enable viewing of long file names in directory lists on http://repository.jboss.com/maven2/ > ------------------------------------------------------------------------------------------- > > Key: JBBUILD-339 > URL: http://jira.jboss.com/jira/browse/JBBUILD-339 > Project: JBoss Build System > Issue Type: Task > Reporter: Charles Crouch > > Looking at http://repository.jboss.com/maven2/jboss/jboss-logging-spi/2.0.3.GA/ its impossible to tell what files are actually there without mousing over them and seeing where the link goes, e.g. > [DIR] Parent Directory - > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 8.2K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 115 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 7.5K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 107 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 2.2K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 107 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > It should be possible to fix this following instructions similar to those discussed here: > http://www.networkworld.com/columnists/2006/051506internet.html -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-825) Transactions corrupted because sybase truncates trailing zeros

by Tim Fox (JIRA)

Transactions corrupted because sybase truncates trailing zeros -------------------------------------------------------------- Key: JBMESSAGING-825 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-825 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta2 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.CR1 Sybase has the wonderful characteristic of truncating trailing zeros in VARBINARY columns. So If I set a byte array with values: 1, 2, 3, 4, 5, 0, 0, 0 Then I get back a byte array with values: 1, 2, 3, 4, 5 Xid global txids and branch qualifiers can have trailing zeros since they can become corrupt after storing and retrieving in the database. Solution is to introduce a flag "usingTrailingByte" on the pm config. If true then a non zero byte will always be appended to the byte[] before storing and removed on retrieval. This flag should be true for sybase config and false for others. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4056) Web Console causes an error when navigating to EJB statistics page (MBeanProxyCreationException)

by dudlo (JIRA)

Web Console causes an error when navigating to EJB statistics page (MBeanProxyCreationException) ------------------------------------------------------------------------------------------------ Key: JBAS-4056 URL: http://jira.jboss.com/jira/browse/JBAS-4056 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 Reporter: dudlo Assigned To: Darran Lofthouse Web Console incorretly parses and passes JMX name to the JSP that displays EJB statistics. As a result, MBeanProxyCreationException is thrown from the JSP. The bug and steps to reproduce it is described at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010247#4010247 The bug affects customers that rely on web-console feature that displays usage statistics (EJB methods called and overall time spent in them) -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-664) The 4.0.5.GA jnlp installer smoke test fails

by Ovidiu Feodorov (JIRA)

The 4.0.5.GA jnlp installer smoke test fails -------------------------------------------- Key: JBMESSAGING-664 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-664 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Affects Versions: 1.0.1.GA Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.2.CR1 Authentication failure on JMX invocations. Not directly caused by messaging, but must be fixed nonetheless. -- 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, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-824) queue smoke test fails

by Ovidiu Feodorov (JIRA)

queue smoke test fails ---------------------- Key: JBMESSAGING-824 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-824 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.0.1.SP4 javax.jms.JMSSecurityException: User: null is not authorized to write to destination SmokeTestQueue -- 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, 2 months

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