I have the same problem...I am using JSR 181 with Java 1.4.2 to declare my service...The method is still being exposed even when i obmit "webmethod, webparam" declaration. This exposed method will have in0,in1...as parameter names Anyreason why? Lana Dam
________________________________ From: Adam Kramer [mailto:[EMAIL PROTECTED] Sent: Wed 4/5/2006 11:34 AM To: [email protected] Subject: Re: [xfire-user] Ignoring methods If you are looking for a way to do JSR181 without Java 5, then use commons attributes. Instructions on its use are on the same page near the bottom, http://xfire.codehaus.org/JSR+181+Annotations <http://xfire.codehaus.org/JSR+181+Annotations> Adam Vinicius Carvalho wrote: > Dan, thanks for your reply. unfortunatelly we can not use java 5.0 > (we're using the crappy horrible I hate it Oracle AS) :( > Is there a way to ease the generation of those mapping files? maybe an > eclipse plugin/ant task/xdoclet? > > Regards > > On 4/5/06, *Dan Diephouse* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Dan Diephouse wrote: > > Vinicius Carvalho wrote: > >> Hello! How can I instruct XFire which methods should it include on > >> WSDL? It's generating a monster WSDL that includes type definitions > >> for event the Class, Package and ClassLoader classes :O > >> > >> Regards > >> > >> > > Hi Vinicius, > > > > See the section on "ignoring properties" here: > > > > http://xfire.codehaus.org/Aegis+Binding > <http://xfire.codehaus.org/Aegis+Binding> > > > > XFire does ignore everything on the Object & Exception classes so it > > shouldn't really pull those in unless you have them as some property > > on your beans. Hope that helps! > > > > - Dan > > > Also if this is for your service class you can use the JSR 181 > stuff to > control your service interface mapping: > > http://xfire.codehaus.org/JSR+181+Annotations > <http://xfire.codehaus.org/JSR+181+Annotations> > > - Dan > > -- > Dan Diephouse > Envoi Solutions > http://envoisolutions.com > http://netzooid.com/blog > > This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
