I'm not sure, perhaps it was designed that way so the sub-WSDL could be reusable with other "outer" WSDLs? Or might only need to be cached once for multiple outer WSDLs, perhaps.
Glen Am Mittwoch, den 08.08.2007, 11:53 -0700 schrieb Jason Rosenberg: > Hi, > > I just converted a simple app from XFire to CXF....It's a code-first > app....The generated WSDL is now a bit different, in that it is in 2 parts, > the main WSDL uses an import to point to a sub-WSDL....The sub-WSDL contains > these parts: > > wsdl:types > wsdl:message > wsdl:portType > > And the main wsdl contains these parts: > > wsdl:import (importing the sub-wsdl) > wsdl:binding > wsdl:service > > Is there any reason for this, is it expected? I can't decide if I should be > concerned or not with it, one thing I can think of is if I want to cache the > WSDL locally, it is a bit problematic to also cache the sub-WSDL pointed to > via a URL (and not also a local file).... > > Thanks for any insight, > > Jason > >
