Home/ Questions/Q 7919049
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T15:43:33+00:00

I’m tring to extend the example in chapter 5 of the Spring WS guide.

  • 0

I’m tring to extend the example in chapter 5 of the Spring WS guide. I’m using Spring WS 1.5.9 .

I’ve added … 

<import namespace="http://myco.com/schemas/promotion/v1_2"
    schemaLocation="http://localhost:8080/ordersService/Promotion_1_2.xsd" /> ...

But spring doesn’t appear to be transforming the location of the import like it does for the port. So on my company website it still shows “localhost:8080”

I have the WSDL generation defined as such

<bean id="orders" class="org.springframework.ws.wsdl.wsdl11.DefaultWsdl11Definition">
    <property name="schema" ref="schema" />
    <property name="portTypeName" value="Orders" />
    <property name="locationUri" value="http://localhost:8080/ordersService/" />

Does/Can Spring Framework transform the imports some way ???

UPDATE: Some more background….

We use the same XSD with the maven JaxB2 plugin to build our response schema objects. That all works great, and we use the Catalog resolver to actually find the addional business domain XSDs in an included JAR file. We have 100’s of XSDs that describe our business domain.

SO i’m trying not to break that.

What I would like to see is a more detailed example. An example where JaxB2 is used and XSD -> WSDL functionality.

Should I refactor the XSDs ?
Should I use a WSDL and not an XSD
How do I properly idenitfy the XSDs to spring ?
Do I use “classpath:My_file.xsd” ? Will I have to list possibly 100’s of XSDs to schemaCollection ?

The spring Docs are great but I would like a practical example that matches.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I want to add detail on the solution we ended up with. We have been moving to Spring WS 2x. Here’s an updated link…

    http://static.springsource.org/spring-ws/site/reference/html/server.html#server-automatic-wsdl-exposure

    The trick / key was in that section it says… “If you want to use multiple schemas, either by includes or imports, you will want to put Commons XMLSchema”

    So that was the final answer to add that to our project.

    <dependency>
     <groupId>org.apache.ws.commons.schema</groupId>
     <artifactId>XmlSchema</artifactId>
     <version>1.4.7</version>
</dependency>

    Now spring enables additional functionality to allow classpath resolution to work.

    • 0