I must be missing something obvious -
Using an httpService proxy to the backend server like so in my
proxy-config:
destination id=backEnd
properties
urlhttp://myServer:8080/myApp/url
/properties
/destination
Executing a simple test, I monitor the traffic
Your blazeds http transport is going fine, otherwise you wouldn't see
anything in message, faultcode, etc. The problem is either in the proxy
server itself, or the server you're trying to talk to.
-Josh
On Tue, Jul 29, 2008 at 3:33 PM, ron_mori [EMAIL PROTECTED] wrote:
I must be missing
That should be taken care of automatically when using BlazeDS as a proxy.
-Josh
On Mon, Jul 28, 2008 at 3:43 PM, ron_mori [EMAIL PROTECTED] wrote:
The fault handler is being call. (server 500 status) The good news
is that my research points me towards the BlazeDS proxy server which I
have
Josh,
Thanks for the reply - the mystery is how to access the server
response body content for a faultEvent. My proxy server does a great
job of forwarding requests and responses but my client still can not
access the response xml body content for an 'error' (status 500)
server response.
I'm
IIRC: The way it works in BlazeDS is not that it acts as an actual http
proxy where you make fully qualified requests over http, but you send
requests down a flash-remoting socket connection, and it makes requests and
pipes back the result. The end result is that the browser doesn't get to
The fault handler is being call. (server 500 status) The good news
is that my research points me towards the BlazeDS proxy server which I
have successfully set up to make my remote server calls.
Now the trick is to get the proxy to grab the remote error msg and
return a status 200 good msg back
6 matches
Mail list logo
