So, if I have a class MyServiceBean that extends ServiceBean and improves one of its methods (as outlined below), how do I change services.xml to use MyServiceBean instead of ServiceBean? Must I rewrite everything in Spring notation?
I know little about Spring, and nothing about XBean. - John Kristian -----Original Message----- From: Dan Diephouse [mailto:[EMAIL PROTECTED] Sent: Thursday, March 30, 2006 2:15 PM To: [email protected] Subject: Re: [xfire-user] Dumb Question with Services.xml Syntax Tyler Nelson wrote: > For now I copied ServiceBean and I had copy and paste that class > into the project for now, unfortunately a good number of properties > and methods cannot be accessed by child classes either :( All i > really need to was in override afterPropertiesSet Try this as your afterPropertiesSet: public void afterPropertiesSet() throws Exception { super.afterPropertiesSet(); getXFireService().setWSDLWriter (new ResourceWSDL(getClass().getResource ("/com/acme/foo.wsdl").toURL())); } > On 3/30/06, *Dan Diephouse* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Tyler Nelson wrote: > > Hi Dan, > > I'm trying to use the Services.xml syntax with a simple web service > > with Xfire 1.0 . I want to include a wsdl with the wsdlUrl element , > > however it looks like that is not valid element any longer. How > > would you recomend me injecting the wsdl without going back to the > > Spring only syntax. It seems the only way to do it would be extends > > ServiceBean and have it call another method in a ServiceFactory. > > > > Thanks, > > Tyler > Hmm, it would appear that property is completely missing! Maybe the > subject should be "dump developers create dumb services.xml > syntax" :-) > > I will get it added it in for the 1.1beta release I am trying to cut > right now. In the meantime you can add a bean post processor which > grabs the service bean and does: > > serviceBean.setWSDLWriter(new ResourceWSDL(urlToWSDL)); > - Dan
