Transforming XSD Import for WSDL in Spring WS -


I'm trying to expand the example in Chapter 5 of the Spring WS Guide. I'm using SpringWS 1.5.9.

I have added ... 

  import namespace = "http://myco.com/schemas/promotions/ v1_2" schema location = "http: // localhost : 8080 / Order Service / Promotion_1_2.xsd "/> ...   
 But for the harbor it does not change the location of the spring import, so on my company's website it still shows "localhost: 8080"  
 I have a WSDL generation, such as  
   & Lt; Property Name = "PortTipName" Value = "Order" /> & Lt; Property name = "location" value = "http: // localhost: 8080 / order service /" />   
  
 What does the CAN / Spring Framework change in some way ???  
 UPDATE: A few more backgrounds ....  
 To make our feedback schema objects we use the same XSD with the Maven Jacob2 plugin. All this works very well, and we use Catalog Resolver to find assembly business domains XSDs actually in any included JAR file. We have 100 SSDD that describe our business domain.  
 So I am not trying to break it.  
 What I want to see is a more detailed example. An example where JaxB2 is used and XSD - & gt; WSDL functionality.  
 Should I restart XSD? Should I use WSDL and not XSD How do I properly identify XSDs for spring? Do I use "classpath: my_file.xsd"? Do I have to list 100 SSDS for schema collection?  
 Spring Docks are great, but I would like a practical example that matches.   
 
 
 I want to add detail on the solution that we had terminated. We are going to Spring WS 2x here is an updated link ...  
  
 The trick / key was in that section, it says ... "If you have multiple schemas If you want to use, either it is included in or imported, then you want "Commons XMLSchema"  
 then it was the last answer to add our project.  
  & lt; Dependency & gt; & Lt; Group & gt; Org.apache.ws.commons.schema & lt; / Group & gt; & Lt; ArtifactId & gt; XmlSchema & lt; / ArtifactId> & Lt; Version & gt; 1.4.7 & lt; / Edition & gt; & Lt; / Dependencies & gt;   
 Now allows additional functionality to allow Spring Classpath resolutions to work.

Comments

Post a Comment