the optionality comes from the fact that the service instance can be specified using its class name in this serviceClass attribute or using a bean instance either in the serviceBean attribute or in the element. I don't if there is a defined behavior if the service is redundantly or inconsistently specified there, though.
for the client side, not specifying the service nor the wsdl at all is also a valid option when using a generic dispatch client. 2015-02-13 13:49 GMT+01:00 Kalpa Welivitigoda <[email protected]>: > Hi, > > I have a questions about Jax-WS services and how CXF handles the > configurations. > > In general we define the serviceClass in the cxf-servlet.xml, but as > per the jaxws.xsd [1] the serviceClass attribute in the Server element > is not mandatory. In such a case where the serviceClass is not > specified in the cxf-servlet.xml, how does cxf find the serviceClass > in the service? Does it scan through all the classes and look for > Jax-WS annotations? > > [1] http://cxf.apache.org/schemas/jaxws.xsd > > -- > Best Regards, > > Kalpa Welivitigoda > +94776509215 > http://about.me/callkalpa
