[ 
https://issues.apache.org/jira/browse/CXF-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117001#comment-16117001
 ] 

RANADEEP SHARMA edited comment on CXF-7463 at 8/7/17 6:33 PM:
--------------------------------------------------------------

Hi Daniel,

Thanks for the reply.

My test case is simple. The Spring Expression is supposed to parse the 
<jaxws:client ...> above and replace the token 
+${setit.pull.service.uri:http://enter.valid.setit.pull.service.uri/}+ or 
*${setit.pull.service.uri}* with the following value set from the properties 
file.

*setit.pull.service.uri*=http://isetit.intg.apptoapp.net/isetit/iws/ws/Pull

It use to work in the older version, that way. But, not anymore. I have read in 
the latest Spring documentation that there's no change in their SPEL expression 
syntax.

Please let me know if you need more details. if so, please let me know what are 
those.

Regards,
Ranadeep.


was (Author: [email protected]):
Hi Daniel,

Thanks for the reply.

My test case is simple. The Spring Expression is supposed to parse the 
<jaxws:client ...> above and replace the token 
*${setit.pull.service.uri:http://enter.valid.setit.pull.service.uri/}* or 
*${setit.pull.service.uri}* with the following value set from the properties 
file.

*setit.pull.service.uri*=http://isetit.intg.apptoapp.net/isetit/iws/ws/Pull

It use to work in the older version, that way. But, not anymore. I have read in 
the latest Spring documentation that there's no change in their SPEL expression 
syntax.

Please let me know if you need more details. if so, please let me know what are 
those.

Regards,
Ranadeep.

> No evaluation for spring expression as value for 'address' attribute in 
> <jaxws:client />
> ----------------------------------------------------------------------------------------
>
>                 Key: CXF-7463
>                 URL: https://issues.apache.org/jira/browse/CXF-7463
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 3.1.10, 3.1.12
>         Environment: 1) Apache Tomcat 7.0.54
> 2) JDK 1.7.0_80
> 3) Exception trace captured during invocation of the SOAP service attached.
>            Reporter: RANADEEP SHARMA
>             Fix For: NeedMoreInfo
>
>         Attachments: CXF_JaxWS_exception_trace.txt
>
>
> The reported issue was observed when Spring framework 
> {color:red}*4.3.x*{color} was used. 
> However, SPEL evaluation of the mentioned JaxWs client config work's fine 
> with older Spring version {color:red}*4.1.6*{color}.
> 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="#{setit.pull.service.uri:http://enter.valid.setit.pull.service.uri/}";
>  />
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to