Kyle, This won't solve your problem, but just an advice if you are using Spring: try using the new XFireClientFactoryBean. This should allow you to set up a client real easily in a Spring application context. It also allows very easy setup of username and password for the client. Unfortunately it is not yet available in 1.0...
Fried P.S. I would expect the accountServiceURL in your code does not actually contain the "?wsdl" part, since that is the wsdlURL not the URL for the service. > -----Original Message----- > From: Kyle Mallory [mailto:[EMAIL PROTECTED] > Sent: donderdag 11 mei 2006 18:14 > To: [email protected] > Subject: [xfire-user] New to XFire: Dynamic Client works, but result in > unpopulated > > I just starting using X-Fire as an alternative to Axis with Spring. > I am trying to write an Acegi authenticationDao that uses XFire to > query a remote centralized auth service. But all that's not really > important. :-) > > I have the following, very simple client code: > > String accountServiceURL = "http://remotehost/account- > v1/services/ > accountManager?wsdl"; > XFire xFire = XFireFactory.newInstance().getXFire(); > XFireProxyFactory xFireFactory = new XFireProxyFactory(xFire); > > Service accountManagerService = new > ObjectServiceFactory().create > (AccountManager.class); > Account Manager accountManagerProxy = (AccountManager) > xFireFactory.create(accountManagerService, accountServiceUrl); > > Account account = > accountManagerProxy.getAccountByUsername(this.user); > > if (this.password.equals(account.getPassword())) > return true; > > This code executes without any errors or exceptions. However the > resulting Account object is valid, but all of the object fields are > uninitialized (strings are null, booleans are false, vectors are > created but empty, dates are created but invalid). > > I have stepped through the XFire code, and looked at the XML stream > response, and all the data is there, it just doesn't populate into > the result object. > > I suspect that this is because the bindings are not being setup > properly, despite having the wsdl in the service url. > > Any ideas? > > > Also, I read on the Client API pages that in order to do http > authentication on the service, you have to call XFireProxy.getClient > (). However, I this method doesn't exist in the 1.0 codebase? > > Is there another, correct way to do this? > > Thanks, > > Kyle
