Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Flex&SAP Exceptions handling.

Go to solution
Former Member

‎2008 Dec 01 6:01 PM

0 Likes
439

Hello

We have deployed a Web Service application in our WAS 7.10 SP6.

Our application is a standard java 5 app with annotations (ejbs exposed as web services).

When a web service call operation returns a java exception (any kind of exception), WAS returns http 500 to the client.

http 500 cannot be interpreted by a flex client (2.0, 3.0 no matter which version) because of an interaction between browser and flex runtime issue. Flex code can only obtain an i/o error when http 500 is returned by the server.

The usual way to solve this problem is to create a filter that transforms http 500 to http 200, but we don't know how to implement a filter for web services http responses in WAS 7.1 or 7.0

Other solutions involve using Adobe proxy, but in our case we can't use it.

Is there any other solution to this matter?

1 ACCEPTED SOLUTION
Read only

Go to solution
former_member10945
Contributor

‎2008 Dec 02 2:39 PM

0 Likes
412

If you don't mind coding the SOAP handling yourself you can use the [as3httpclientlib project|http://github.com/gabriel/as3httpclient/tree/master] which is a nearly fully implemented httpclient that uses sockets to work.

The socket config can sometimes be a bit tricky to get setup but if you control the servers in question it's possible. This isn't a perfect solution but in this case Adobe is a bit behind what the browser do ( which is not pass 500s to plugins ) so they are a bit stuck in what they can provide to the player then on to the framework.

-d

Hello

We have deployed a Web Service application in our WAS 7.10 SP6.

Our application is a standard java 5 app with annotations (ejbs exposed as web services).

When a web service call operation returns a java exception (any kind of exception), WAS returns http 500 to the client.

http 500 cannot be interpreted by a flex client (2.0, 3.0 no matter which version) because of an interaction between browser and flex runtime issue. Flex code can only obtain an i/o error when http 500 is returned by the server.

The usual way to solve this problem is to create a filter that transforms http 500 to http 200, but we don't know how to implement a filter for web services http responses in WAS 7.1 or 7.0

Other solutions involve using Adobe proxy, but in our case we can't use it.

Is there any other solution to this matter?

Reply
1 REPLY 1
Read only

Go to solution
former_member10945
Contributor

‎2008 Dec 02 2:39 PM

0 Likes
413

If you don't mind coding the SOAP handling yourself you can use the [as3httpclientlib project|http://github.com/gabriel/as3httpclient/tree/master] which is a nearly fully implemented httpclient that uses sockets to work.

The socket config can sometimes be a bit tricky to get setup but if you control the servers in question it's possible. This isn't a perfect solution but in this case Adobe is a bit behind what the browser do ( which is not pass 500s to plugins ) so they are a bit stuck in what they can provide to the player then on to the framework.

-d