You have two options here.
1.) Specify unwanted method names as excludeOperations in service.xml file.
<excludeOperations>
<operation>getUser</operation>
<operation>setUser</operation>
</excludeOperations>
2.) Specify business interface as the "ServiceClass" in addition to
"SpringBeanName" parameter in service.xml.
<parameter name="SpringBeanName">BusinessServiceImplBean</parameter>
<parameter name="ServiceClass" >BusinessService</parameter>
2nd option is much preferable for Spring application specially if you have
a plan to use Spring SOP related features.
Thanks !
On Tue, Jan 31, 2012 at 10:09 PM, <[email protected]> wrote:
> Hello,****
>
> ** **
>
> I have a web service using Spring which I deploy as packaged in .aar
> archive. The business method of the service are defined in an interface.
> I’m also using Spring and the implementation class has additional methods
> for dependency injection. When the service is deployed in Tomcat and I
> bring up the http://localhost:8080/axis2/service/listServices is see all
> the getter methods, not just the business methods. How can I prevent
> listing of the methods used for the dependency injection? TIA,****
>
> ** **
>
> -a ****
>
> ** **
>
> *Aaron Stromas, Practice Consultant | **RSA** ** The Security Division
> of EMC | Identity & Fraud Protection Practice | +1 240 271 6458*****
>
> ** **
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara
