Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-430

WSDL is renedered without resolving dynamic attributes managed using a PropertyPlaceHolderConfigurer object

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 1.5.4
    • Fix Version/s: 1.5.6
    • Component/s: None
    • Labels:
      None
    • Environment:
      windows xp 32, JDK 1.6

      Description

      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.

        Issue Links

          Activity

          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Could you please attach the generated wsdl?

          Show
          arjen.poutsma Arjen Poutsma added a comment - Could you please attach the generated wsdl?
          Hide
          pakin Angel added a comment -

          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 SWS-429 that I have lodged.

          Thanks.

          Show
          pakin Angel added a comment - 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 SWS-429 that I have lodged. Thanks.
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          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.

          Show
          arjen.poutsma Arjen Poutsma added a comment - 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.
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Closing old issues

          Show
          arjen.poutsma Arjen Poutsma added a comment - Closing old issues

            People

            • Assignee:
              arjen.poutsma Arjen Poutsma
              Reporter:
              pakin Angel
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: