I'm not sure that inlining the schemas is the best solution. I'll hold my comments on trying to mimic what .NET is doing as a good thing Please keep in mind, my solution focuses on statically defined wsdl, not dynamically generated wsdl. In general, static wsdl doesn't seem to be supported nearly as well in spring-ws as is the dynamically generated approach. This is very true when the static wsdl imports schemas and those schemas import other schemas. This is considered a best practice by many in the SOA community as it promotes reuse of types.
I think that spring-ws will be more successful if it supports static wsdl as well as it does dynamic wsdl. Even though spring-ws doesn't necessarily need the static wsdl in order to function, it should still provide standard ways to access it (via ?wsdl query parm on the url) and standard ways to resolve all location specific elements and attributes embedded within.
My thoughts are that the static wsdl and associated schema files are essential parts of defining the Web services contract and that they should be preserved in the form that they were created with as few modifications as possible. In our case, we tried to follow best practices by defining types in separate schema files and then import those schemas into the statically defined wsdl and other schemas. This leads to better reusability of types. The only modification to the wsdl and xsd my solution provided was to resolve the location specific aspects, mostly URL's. Inlining creates one big huge unreadable, unmaintainable wsdl in our case. If I were to look at that from an outsiders point of view, I would come to the conclusion that the wsdl designer didn't know what he was doing. Popular tools like SoapUI can easily pull in all of the schemas using my solution, it just walks through the wsdl and gathers all of the nested schemas (and schemas that import other schemas), pretty standard stuff.
So while inlining the schemas is functionally equivalent to importing them, it's not very good at all from a design standpoint. You're obviously free to do what you want since spring-ws is your framework but for now we are going to have to keep our modifications in place in order to use spring-ws in a way that is more natural to us (and most likely others). I would like to see these modificiations be included in spring-ws so that others may benefit but that's kind of up to you. FWIW, Weblogic provides similiar functionality in regards to static wsdl and nested schemas.
The other thing I'd like to point out is that most projects of any size will most likely have separate .jars for their XMLBeans (or equivalent XML to Java binding) classes. In our case, we did not want to have to drop the .xsd into both the XMLBeans maven project AND the .war project. Instead, it was fairly easy to simply make a classpath reference in the spring config for the schemas.