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
