Vedha Vijayan wrote:
2. How do we inform the WSDL generator to not map (filter out) certain
"public" methods to WSDL operations?
I'm using Axis2 with Spring, and created an interface with the methods I
want to expose, and an implementation bean which has some "public"
methods that should not be available to the webservice, like this (in
services.xml):
<service name="FooService">
<description>Web service</description>
<parameter name="ServiceObjectSupplier"
locked="false">org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier</parameter>
<parameter name="SpringBeanName"
locked="false">fooWebServiceBean</parameter>
<parameter
name="ServiceClass">nl.topicus.foo.webservice.FooWebService</parameter>
<messageReceivers>
<messageReceiver
mep="http://www.w3.org/2004/08/wsdl/in-only";
class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
<messageReceiver
mep="http://www.w3.org/2004/08/wsdl/in-out";
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
</messageReceivers>
</service>
(where fooWebServiceBean refers to a bean of the FooWebServiceImpl
class, which in turn implements
nl.topicus.foo.webservice.FooWebService). Does that appear to make sense?
Notice also that compared to http://ws.apache.org/axis2/1_1/spring.html
I took out the SpringAwareService class and am referencing the
implementing bean directly. Is this a bad idea?
I'm pretty new to Axis2, so I'm interested to hear what approaches are
better than others (and why).
Arnout
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
