The problem is that when I display the WSDL (ie. [URL_SERVICE]?wsdl), it is the generated one, not the original one.
dkulp wrote: > > On Sat January 2 2010 9:58:51 am greg_le_bonniec wrote: >> Hello, >> >> Is there someone who could explain me what is the role of wsdllocation in >> the WebService annotation ? >> >> is it only a validation role at the service deployment ? > > It serves a bunch of purposes: > > 1) If wsdlLocation is specified (either on the WebService annotation or in > the > jaxws:endpoint element in the config), we don't have to generate a wsdl at > runtime. We use the specified wsdl directly (just modifying the > soap:address > as needed) > > 2) If schema validation is turned on, we need the actual schemas from the > wsdl > to validate against. Without the wsdl, we use the schema that JAXB will > generate, but that is "lossy" as not all schema constructs are recorded in > the > JAXB annotations. > > 3) Some things like policies (particularly things like WS-SecurityPolicy) > are > primarily stored and used from the WSDL. There are ways to configure > them in > config, but the normal use case is that they are part of the wsdl > contract. > > 4) Some bindings (particularly the CORBA binding) require extra > information > from the wsdl. The CORBA binding, for example, requires the CORBA type > mapping element from the wsdl to map the XML types into the IDL type codes > that need to go on the IIOP wire. > > There's probably more. Those are the "off the top of my head" things. > :-) > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog > > -- View this message in context: http://old.nabble.com/wsdllocation-tp26993693p27026650.html Sent from the cxf-user mailing list archive at Nabble.com.
