Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.1.10, 3.1.12
-
None
-
1) Apache Tomcat 7.0.54
2) JDK 1.7.0_80
3) Exception trace captured during invocation of the SOAP service attached.
-
Unknown
Description
The reported issue was observed when Spring framework 4.3.x was used.
However, SPEL evaluation of the mentioned JaxWs client config work's fine with older Spring version 4.1.6.
Following is the config that's no longer evaluating the SPEL expression. I have also tried with '$' prefix instead of '#', but same issue.
<jaxws:client id="setItPullServiceClient"
serviceClass="xyz.app.ws.stubs.setit.pull.PullDataImpl"
address="#
" />
And for enabling value substitution for SPEL expressions from properties file, we have the following.
<context:property-placeholder location="file:${refApp.prop.location:.}/${refApp.app.id}.properties , file:${refApp.prop.location:.}/${refApp.app.id}-secure.properties"
system-properties-mode="OVERRIDE"
ignore-unresolvable="true"
ignore-resource-not-found="true"
order="1"/>
I am not able to get a clue on what's preventing the evaluation of the expression.