I could be wrong, but I don't believe XFire is designed to work in this way. You should be able to do what you would normally do (creating objects, etc.) then use your poison of choice to marshall to XML (jaxb, xmlbeans, etc.) and get the XML to send to the service. There's a little bit more setup/configuration/coding that you'll need (mostly related to marshalling), but the marshaller will still handle the heavy lifting (you don't have to construct the XML manually). You may even be able to use stubs generated by XFire, get the input object(s) marshalled to XML, then invoke the service.
It may have less to do with the client than it has to do with the service, though ... message binding typically needs to be specified on the remote side, so the SOAP binding style is set correctly. Hope some of this helps! Cheers, Brice -----Original Message----- From: Chad La Joie [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 20, 2006 1:41 PM To: [email protected] Subject: Re: [xfire-user] Client access to response StAX Just so I'm clear, if I used the MessageBinding binding I'd need to use StAX to write out the requests that the client sends, correct? I'm really looking for a way to have XFire do everything it normally does when sending a request (which as I understand, with the Aegis binding is to use things like XMLBeans, JDOM, etc) but to do nothing to the response except give me the StAX stream. The client I'm using was generated from a WSDL, if that makes a difference. Matthew Good wrote: > look at: > > http://xfire.codehaus.org/Message+Binding > > > > ----- Original Message ---- > From: Chad La Joie <[EMAIL PROTECTED]> > To: [email protected] > Sent: Wednesday, December 20, 2006 9:01:00 AM > Subject: [xfire-user] Client access to response StAX > > I've a client that is accessing a service that may return a very large > result document. As such I'd prefer gain direct access to the StAX > stream reader instead of having XFire try to bind the incoming message > to a set of objects. What's the best way to do this? Currently I'm > thinking I'll need to define a new BindingProvider that would extend the > Aegis provider and override the readParameter and provides access to > provided reader. Does this make sense? Is there a better approach? > > Thanks for the help. -- Chad La Joie 2052-C Harris Bldg OIS-Middleware 202.687.0124 --------------------------------------------------------------------- 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
