Skip to main content
S
sjpdallas
Participant
February 2, 2009
Question

BlazeDS as a simple proxy for Flex app using Imported Web Services

  • February 2, 2009
  • 1 reply
  • 1788 views
After posting to the BlazeDS group, it was recommended that I repost here.

I have been developing a flex application that consumes a 3rd party WSDL. I imported that WSDL using the built in flex WSDL data utilities available under the (Flex 3) Data menu. Things were progressing.

Being new to the whole thing, it took me awhile to determine why I was unable to get the SOAP error codes. After learning that error codes in 500 range are not returned, and that using a proxy such as BlazeDS will allow me to see the SOAP errors, I decided to try to make this work.

Enter BlazeDS.

After scouring the web, reading a lot, looking at the examples, etc., I can now create new projects and, using webservices directly, get results using the BlazeDS proxy.

However, try as I might, I have been unable to create a project that imports the WSDL using the flex data tools, and then have the project work against BlazeDS. The automatically generated webservice class supports instantiation with a destination and proxy address. But any time I use either an AMF or HTTP endpoint, I immediately get decoding errors on the first webservice call.

I'm sure that I'm missing something highly obvious.

Any thoughts would be appreciated.

- Steve
This topic has been closed for replies.

1 reply

matt_chotin
matt_chotin
Inspiring
February 2, 2009
Have you added the necessary passthrough information in BlazeDS? I'm not sure anyone here will really be able to help as this is for development of the SDK itself. The better list is actually flexcoders on Yahoo groups (or you can try the forums on the regular adobe.com).<br /><br />Matt<br /><br /><br />On 2/2/09 10:18 AM, "netmass" <member@adobeforums.com> wrote:<br /><br />A new discussion was started by netmass in<br /><br />Developers --<br /> BlazeDS as a simple proxy for Flex app using Imported Web Services<br /><br />After posting to the BlazeDS group, it was recommended that I repost here.<br /><br />I have been developing a flex application that consumes a 3rd party WSDL. I imported that WSDL using the built in flex WSDL data utilities available under the (Flex 3) Data menu. Things were progressing.<br /><br />Being new to the whole thing, it took me awhile to determine why I was unable to get the SOAP error codes. After learning that error codes in 500 range are not returned, and that using a proxy such as BlazeDS will allow me to see the SOAP errors, I decided to try to make this work.<br /><br />Enter BlazeDS.<br /><br />After scouring the web, reading a lot, looking at the examples, etc., I can now create new projects and, using webservices directly, get results using the BlazeDS proxy.<br /><br />However, try as I might, I have been unable to create a project that imports the WSDL using the flex data tools, and then have the project work against BlazeDS. The automatically generated webservic! e class supports instantiation with a destination and proxy address. But any time I use either an AMF or HTTP endpoint, I immediately get decoding errors on the first webservice call.<br /><br />I'm sure that I'm missing something highly obvious.<br /><br />Any thoughts would be appreciated.<br /><br />- Steve<br /><br />________________________________<br />View/reply at BlazeDS as a simple proxy for Flex app using Imported Web Services <a href=http://www.adobeforums.com/webx?13@@.59b7c238><br />Replies by email are OK.<br />Use the unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b7c238!folder=.3c060fa3> form to cancel your email subscription.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices