Spring-WS has this really nice facility for handling this, making use of the Apache XML Commons project.
Spring-WS has this really nice facility for handling this, making use of the Apache XML Commons project: /DataContract/person. Xsd /DataContract/sub-person. Xsd The inline property is the key - it reads in each schema file, and whenever it finds an import or include reference from one to the other, it replaces the reference with the content of the referenced file.
The effect of this is that the output of the WSDL-generation controller is a single file with all schema information inlined within it, while still keeping the various schema files separate on the server. You then don't have to worry about if the client can chase the references and resolve them properly, since there are no references.
Thanks that solved the issue. I had left out the 'inline' property from the schemaCollection, I am just not sure whether it would be a good idea to have one bulky wsdl file. – saky Mar 4 '10 at 17:17 @saky: Inlining the schema files can make quite a difference to performance – skaffman Mar 4 '10 at 17:27.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.