[
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