April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-1888) Incorrect variable expansion in org.jboss.util.propertyeditor.PropertiesEditor

by Eelco de Lang (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1888?page=comments#action_12360373 ] Eelco de Lang commented on JBAS-1888: ------------------------------------- My code had the same bug. It can be easily fixed by replacing anything like: matcher.appendReplacement(result, replacement); with: // Don't use appendReplacement(result, replacement)! // It will remove all slashes. matcher.appendReplacement(result, ""); result.append(replacement); > Incorrect variable expansion in org.jboss.util.propertyeditor.PropertiesEditor > ------------------------------------------------------------------------------ > > Key: JBAS-1888 > URL: http://jira.jboss.com/jira/browse/JBAS-1888 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployment services > Reporter: Bela Ban > Assigned To: Scott Marlow > Priority: Minor > Fix For: JBossAS-5.0.0.Beta3 > > > When I use the ${jboss.server.data.dir} variable in the example below, it is correctly expanded: > <attribute name="bla">${jboss.server.data.dir}</attribute> > However, when I use it in a Properties attribute, the expansion removes backslashes on Windows, e.g. in the example below: > <attribute name="CacheLoaderConfig"> > location = ${jboss.server.data.dir}/myCache > </attribute> > , I get c:JBoss3.2.7serverdefaultdata/myCache. > Scott Stark's reply: > The org.jboss.util.propertyeditor.PropertiesEditor which is what should be used for an attribute of type java.util.Properties does replace ${x} property references in values. The problem is that calling setProperty with the replacement value is not using an escaped string and so the win32 backslash is seen as a char escape sequence. Create a jira issue for this. -- 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: (JBWEB-79) Support Tomcat

by sun hua (JIRA)

Support Tomcat -------------- Key: JBWEB-79 URL: http://jira.jboss.com/jira/browse/JBWEB-79 Project: JBoss Web Issue Type: Task Security Level: Public (Everyone can see) Environment: win2000 server Reporter: sun hua Assigned To: Mladen Turk Don't support Tomcat5.5 very well! Example: <%=***%> not support -- 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: (JBAS-4359) Fix the org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase

by Dimitris Andreadis (JIRA)

Fix the org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase ------------------------------------------------------------------------ Key: JBAS-4359 URL: http://jira.jboss.com/jira/browse/JBAS-4359 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Priority: Blocker Fix For: JBossAS-4.2.0.GA Brian, did the initial analysis for the failure: "The classloader leak test timing out is basically due to a failure; different tests in the class are all encountering the same leak and taking time trying to force a release, so it times out. The failure is on a remote ejb2 sfsb invocation. Not sure, but think it's related to the Remoting upgrade. I've attached a JBoss Profiler report showing refs to the leaked classloader. This one's long and complicated, but I think the relevant stuff is right at the start. The MarshalledInvocation seems to be leaking to the input stream and from there into a thread pool. I switched my build back to Remoting 2.0.0 and the test passed." -- 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
18
0 / 0

[JBoss JIRA] Created: (JBRULES-814) Seperate the interfaces into Stateless and Stateful

by Mark Proctor (JIRA)

Seperate the interfaces into Stateless and Stateful --------------------------------------------------- Key: JBRULES-814 URL: http://jira.jboss.com/jira/browse/JBRULES-814 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-m2 RuleBase now returns two sessions, StatelessSession and StatefulSession. -- 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-815) Refactor getObjects getHandles()

by Mark Proctor (JIRA)

Refactor getObjects getHandles() -------------------------------- Key: JBRULES-815 URL: http://jira.jboss.com/jira/browse/JBRULES-815 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo, Rule Assemply/SPI Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m2 Refactor the why that the user gets access to the handles and objects, so its thread safe and supports ObjectFilters, probably only allow iteration. -- 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: (JBAS-4365) Remove commons http-client and codec from jbossall-client.jar

by Dimitris Andreadis (JIRA)

Remove commons http-client and codec from jbossall-client.jar ------------------------------------------------------------- Key: JBAS-4365 URL: http://jira.jboss.com/jira/browse/JBAS-4365 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Affects Versions: JBossAS-4.2.0.CR2, JBossAS-5.0.0.Beta2 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3 -- 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: (JBMESSAGING-918) MSSQL PM config using reserved word for column name

by Tim Fox (JIRA)

MSSQL PM config using reserved word for column name --------------------------------------------------- Key: JBMESSAGING-918 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-918 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.GA Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1.CR1 The MSQL persistence manager config uses the name "CLUSTERED" as a column name. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1359) JSF security editor does not work

by Julien Viet (JIRA)

JSF security editor does not work --------------------------------- Key: JBPORTAL-1359 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1359 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.CR1 Reporter: Julien Viet Assigned To: Julien Viet Fix For: 2.6.CR2 -- 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: (JBAS-4364) JAVAC_JAR could be removed from run.sh/run.bat

by Jesper Pedersen (JIRA)

JAVAC_JAR could be removed from run.sh/run.bat ---------------------------------------------- Key: JBAS-4364 URL: http://jira.jboss.com/jira/browse/JBAS-4364 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-4.2.0.CR2 Environment: Branch_4.2 + JDK-1.5.0_11 Reporter: Jesper Pedersen Assigned To: Dimitris Andreadis Priority: Optional Since 4.2 and 5.0 is based on JBossWeb (jasper-jdt) the environment variable JAVAC_JAR in run.sh/run.bat can be removed. The following patches does that. -- 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: (JGRP-485) UNICAST doesn't allow for concurrent sending and receiving

by Bela Ban (JIRA)

UNICAST doesn't allow for concurrent sending and receiving ---------------------------------------------------------- Key: JGRP-485 URL: http://jira.jboss.com/jira/browse/JGRP-485 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.4.1 SP3, 2.5 In UNICAST, down() and up() block on the same entry (Entry instance), however, they should be concurrent. As an optimization, we now block on the receiver window when receiving a message, rather than on the entry. This way, down() doesn't have to block on entry which is held until a message has been consumed ! A quick Unicast run with 2 nodes shows that the message rate goes from 4000 msgs/sec to 8000 msgs/sec ! -- 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 April 2007