[ https://issues.apache.org/jira/browse/TAMAYA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anatole Tresch resolved TAMAYA-127. ----------------------------------- Resolution: Fixed Removed any escape features, since they always fail with multipler filter evaluation. $keys are just forwarded and not further interpreted. > NoSuchElementException when using resolver and property values containing an > incomplete token > --------------------------------------------------------------------------------------------- > > Key: TAMAYA-127 > URL: https://issues.apache.org/jira/browse/TAMAYA-127 > Project: Tamaya > Issue Type: Bug > Components: Modules > Affects Versions: 0.1-incubating > Reporter: Lars-Fredrik Smedberg > Assignee: Anatole Tresch > Fix For: 0.2-incubating > > > On a Windows machine I have environment variables for shares and other > things. These property values contain $ but no { } etc... This results in a > NoSuchElementException in the DefaultExpressionEvaluator when calling > tokenizer.nextToken(). > {noformat} > java.util.NoSuchElementException > at java.util.StringTokenizer.nextToken(Unknown Source) > at > org.apache.tamaya.resolver.internal.DefaultExpressionEvaluator.evaluateExpression(DefaultExpressionEvaluator.java:150) > at > org.apache.tamaya.resolver.internal.ExpressionResolutionFilter.filterProperty(ExpressionResolutionFilter.java:81) > at > org.apache.tamaya.core.internal.DefaultConfiguration.applyFilters(DefaultConfiguration.java:177) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)