Hi,
we managed to supress some methods declaring the exclusion in the xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
"
http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
<import resource="classpath:org/codehaus/xfire/spring/xfire.xml"/>
...
<bean name="web.service.configurationService"
class="org.codehaus.xfire.spring.ServiceBean">
<property name="serviceBean" ref="service.configurationService"/>
<property name="name" value="ConfigurationService"/>
<property name="methods">
<list>
<bean class="org.codehaus.xfire.spring.config.MethodBean">
<property name="name" value="setConfigurationBusiness" />
<property name="exclude" value="true" />
</bean>
</list>
</property>
</bean>
...
Hope this give you an idea. By the way, I'm not using any kind of annotation.
Bye.
2008/1/8 tcs <
tahura@...>:
>
> I'm using XFire (with default Aegis Binding) to expose my Web Service. My
> web service impl. class extends other classes. Not only are the methods in
> my web service impl. class exposed in the WSDL generated using XFire, but
> methods from the parent class are also exposed.
>
> I found the XFIRE bug:
>
http://jira.codehaus.org/browse/XFIRE-546>
> However the workaround mentioned in the bug to use @WebMethod(exclude=true)
> does not work with Aegis Binding.
>
> Is there a way to control which methods are exposed in XFire using the
> default Aegis Binding.
>
> thanks
>
>
> --
> View this message in context:
http://www.nabble.com/All-methods-in-web-service-class-are-visible-in-WSDL-tp14696392p14696392.html> Sent from the XFire - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
