WSDL is renedered without resolving dynamic attributes managed using a PropertyPlaceHolderConfigurer object [SWS-430]

[gregturn]

Angel opened SWS-430 and commented

If I define my WSDL publiching bean like this:

 <bean id="stdWebServiceDefinitionFile" class="org.springframework.ws.wsdl.wsdl11.DefaultWsdl11Definition">
	<property name="schemaCollection" ref="stdSchemaCollection"/>
    <property name="portTypeName" value="sendStateTerritoryData"/>
    <property name="locationUri" value="${public.app.url}/shipwreck/sendStateTerritoryDataService/"/>
    <property name="targetNamespace" value="http://environment.gov.au/shipwreck/std/definitions"/>
</bean>

it won't resolve the property ${public.app.url} when rendering the wsdl file and will render it wrongly, but the service works perfectly.

---

Affects: 1.5.4

Attachments:

• stdWebServiceDefinitionFile.wsdl (60.31 kB)

Issue Links:

• Spring WS authentication doesn't work when using a PropertyPlaceHolderConfigurer object [SWS-429] #574 Spring WS authentication doesn't work when using a PropertyPlaceHolderConfigurer object

[gregturn]

Arjen Poutsma commented

Could you please attach the generated wsdl?

[gregturn]

Angel commented

Sure!

There you can find the line #631:
<soap:address location="${public.app.url}/shipwreck/sendStateTerritoryDataService/"/>

As I told you the problem is just when I render the wsdl file, because internally the service is working with the property value resolved. Maybe this unexpected behavior is also related to the issue #574 that I have lodged.

Thanks.

[gregturn]

Arjen Poutsma commented

I just tested this, and afraid that I can't reproduce it. Are you sure you have a

<context:property-placeholder location="classpath:wsdl.properties"/>

in the same application context as the DefaultWsdl11Definition whose properties you're replacing? Since the PropertyPlaceHolderConfigurer is a BeanPostProcessor, it only acts on the app context is defined in. So if you have a child web app context (containing endpoints, mappings etc) with a parent context (containing services, dao's), putting the configurer in the parent context is not going to change properties in the child context.

[gregturn]

Arjen Poutsma commented

Closing old issues