Jeff, I can answer some of your questions with the caveat that all my work is based on POJOs (plain old java objects) as Web services.
The <operations> element just lists the services. There are things you can do on a per-operation basis and that is given in the XML schema at http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/resources/services.xsd?view=markup (note the schema may not be complete but it is close). You can exclude public methods by using <excludeOperations> element. Nadir K. Amra [EMAIL PROTECTED] wrote on 11/08/2007 02:59:09 PM: > 1. How are <operations> in services.xml associated with methods of > the service implementation class? > > 2. Suppose a RawXMLInOutMessageReceiver is used for the service, and > the service impl class exposes just one public method with the > appropriate OMElement methodName(OMElement) signature. Will all > requests dispatched to the service invoke the single exposed public > method, or only ones that somehow map to that method's name based on > the payload element name or soap action uri? > > 3. Is there reference documentation or an XML schema for the full > configuration language used in services.xml? > > Jeff > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
