Actually, services.xml is not required AFAIK. I use annotations and Spring's XFireExporter without services.xml and all works fine. I think services.xml will allow more granular config options if needed. Using another approach besides the XFireExporter it might be needed though, I'm not sure.
----- Original Message ---- From: Mike Miller <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, September 10, 2007 10:23:04 AM Subject: RE: [xfire-user] XFire + JSR-181 .hmmessage P { margin:0px;padding:0px;} body.hmmessage { FONT-SIZE:10pt;FONT-FAMILY:Tahoma;} Someone can correct me if I am wrong, but using the annotations does not relieve you of defining your services.xml. The annotations are read during the client/server stub generation in wsgen. They also allow you to provide provide parameter names in your wsdl rather than getting names like in0, in1, etc. The XFireServlet uses the services.xml to determine which services to expose. Hope this helps... Date: Mon, 10 Sep 2007 14:12:46 -0300 From: [EMAIL PROTECTED] To: [email protected] Subject: [xfire-user] XFire + JSR-181 Hey guys, I'm trying to use XFire with JSR 181 annotations and I'm found this article in XFire wiki http://xfire.codehaus.org/JSR+181+Annotations. Btw, I think that annotations is exactly to avoid xml configurations (and in the sample code, you still having to code in xml). Is there another way to do that? Tks, -- http://plentz.org/ "Provide options, don't make lame excuses." More photos; more messages; more whatever – Get MORE with Windows Live™ Hotmail®. NOW with 5GB storage. Get more! ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/
