June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-876) Single line comments are capturing and removing newline chars in rules consequence

by Michael Neale (JIRA)

Single line comments are capturing and removing newline chars in rules consequence ---------------------------------------------------------------------------------- Key: JBRULES-876 URL: http://jira.jboss.com/jira/browse/JBRULES-876 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.MR2 Reporter: Michael Neale Assigned To: Edson Tirelli Priority: Minor Using the // and # style single line comments strips out the newline character in the RHS of a rule in the DRL.g parser. This can be a problem for tooling, and confusing with line numbering inside the consequence. It also mucks up MVEL with optional ";" as newlines can also delimit an expression. -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1094) Emit JMX Notifications for PojoCacheListener events

by Brian Stansberry (JIRA)

Emit JMX Notifications for PojoCacheListener events --------------------------------------------------- Key: JBCACHE-1094 URL: http://jira.jboss.com/jira/browse/JBCACHE-1094 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Reporter: Brian Stansberry Assigned To: Jason T. Greene Priority: Minor The CacheJmxWrapper for plain Cache adds a CacheListener that converts the listener events into JMX notifications. Consider doing the same for PojoCache. (Note that this isn't important to me personally or to the AS as a PojoCache user; it's just a small hole in the feature set that I noticed as I did all the JMX stuff.) -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-659) Create stress test for open closing sessions etc

by Tim Fox (JIRA)

Create stress test for open closing sessions etc ------------------------------------------------ Key: JBMESSAGING-659 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-659 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.CR1 We should create a stress test that rapidly opens and closes session / connections/ consumers etc, concurrently with sending / receiving / committing / rolling back. -- 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, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-982) Exceptions when openening / closing sessions fast when sending / consuming messages

by Tim Fox (JIRA)

Exceptions when openening / closing sessions fast when sending / consuming messages ----------------------------------------------------------------------------------- Key: JBMESSAGING-982 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-982 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.3.0.GA Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR1 Several exceptions have been supported when opening / closing sessions very fast and concurrently sending / receiving messages. Including "Cannot find delivery to acknowledge...." and "Cannot remove all messages when deliveries are in progress". This is due to a race condition in client side MessageCallbackHandler closing which could cause acknowledgements to be sent *after* the consumer is closed. The problem only manifests when closing consumers. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1052) Add a JMX chapter to the docs

by Brian Stansberry (JIRA)

Add a JMX chapter to the docs ----------------------------- Key: JBCACHE-1052 URL: http://jira.jboss.com/jira/browse/JBCACHE-1052 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.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

18 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-376) Add code point support to JBossRetro

by David Lloyd (JIRA)

Add code point support to JBossRetro ------------------------------------ Key: JBBUILD-376 URL: http://jira.jboss.com/jira/browse/JBBUILD-376 Project: JBoss Build System Issue Type: Feature Request Components: JBossRetro Affects Versions: JBossRetro-1.0.5.GA Reporter: David Lloyd Assigned To: David Lloyd Fix For: JBossRetro-1.1.0.GA Add support for code points to JBossRetro. Since Java 1.4 assumed that the unicode code point space ends at 0xffff, just extend that assumption to the code point methods. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-982) Hibernate logs warning for PersistenceUnitInfo.newTempClassLoader() == null, which it always is in EJB3

by William DeCoste (JIRA)

Hibernate logs warning for PersistenceUnitInfo.newTempClassLoader() == null, which it always is in EJB3 ------------------------------------------------------------------------------------------------------- Key: EJBTHREE-982 URL: http://jira.jboss.com/jira/browse/EJBTHREE-982 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste WARN [Ejb3Configuration] Persistence provider caller does not implements the EJB3 spec correctly. PersistenceUnitInfo.getN ewTempClassLoader() is null. Coming from org.hibernate.ejb.Ejb3Configuration private void addXMLEntities(List<String> xmlFiles, PersistenceUnitInfo info, List<String> entities) { //TODO handle inputstream related hbm files ClassLoader newTempClassLoader = info.getNewTempClassLoader(); if (newTempClassLoader == null) { log.warn( "Persistence provider caller does not implements the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null." ); return; } However, implementation of org.jboss.ejb3.entity.PersistenceUnitInfoImpl has: public ClassLoader getNewTempClassLoader() { return null; } -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1081) The docs/faq/en/master.xml file has been through a shredder

by Brian Stansberry (JIRA)

The docs/faq/en/master.xml file has been through a shredder ----------------------------------------------------------- Key: JBCACHE-1081 URL: http://jira.jboss.com/jira/browse/JBCACHE-1081 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.0.0.GA Beginning at line 254 it's all messed up; basically parts of each line are missing. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1093) ClusteredCacheLoader attempts to propagate remove()s

by Manik Surtani (JIRA)

ClusteredCacheLoader attempts to propagate remove()s ---------------------------------------------------- Key: JBCACHE-1093 URL: http://jira.jboss.com/jira/browse/JBCACHE-1093 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.1.GA, 1.4.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.CR3, 2.0.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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-412) Please use build.properties for jboss.home in examples and the auto-install script

by Sergey Koshcheyev (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-412?page=all ] Sergey Koshcheyev reassigned JBMESSAGING-412: --------------------------------------------- Assignee: Sergey Koshcheyev > Please use build.properties for jboss.home in examples and the auto-install script > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-412 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-412 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Build System > Reporter: Michael Yuan > Assigned To: Sergey Koshcheyev > Priority: Minor > Fix For: 1.4.0.CR1 > > > Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in the distribution. -- 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, 7 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 June 2007