[ 
https://issues.apache.org/jira/browse/CXF-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

RANADEEP SHARMA updated CXF-7463:
---------------------------------
    Description: 
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.

  was:

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.


> 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
>         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