Adobe TV has published a video I did recently about connecting Flex to a SOAP Webservice. Check it out and let me know what you think.
Video – Connecting Flex to a SOAP Webservice
This entry was posted in Flex, SOAP. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.
9 Comments
Hi James
thanks for your great presentation but what’s happened if I want to use Service oriented architecture of j2ee without LiveCycle data services or Blaze DS and use benefits of AMF channel?
can you give me an explanation How this is possible?
Hi Hamidreza,
If you want to use AMF then you have to have an AMF serializer on the server-side. BlazeDS and LCDS are two of the many ways to do this.
-James
so I have to use BlazeDS or LCDS behind my SOAP solution
anyway thanks for your help
Best
Hi James,
a little different problem. I already have a J2EE app running
in my server. Now I want to create a flex app that will monitor
the changes in that J2EE app. I do understand that I need to
write some server side Java code that will call the J2EE API
and gather the needed data and then pass that data to the
Flex application using Blazeds. Now my question is how do
I integrate Blazeds with an existing J2EE app? Itried to copy
the BDS’s web-inf/lib files to the J2EE’s lib directory and then copy
the web-inf/flex folder, which contains mainly those xml file
and also merged the web.xml of blazeds and web.xml of the
J2EE app. But without any success. Can you please suggest
me an solution? Regards….
By the way James – “unshaved” you really look like
a cow buy – Clint Eastwood. To To To To To … Tay Tay Tay… (the tune from
Clint Eastwood’s movies). :-))))
Hi Vivian,
What you described should work. Are you getting error messages? Also you might want to check out my BlazeDS Intro article:
http://www.infoq.com/articles/blazeds-intro
I hope that helps.
-James
Hello James. I post this comment with the hope of a good advice.
We have a middle-sized application with a Flex Client and a J2EE App Server (over 70.000 lines of J2EE+Flex) . We use Axis (SOAP) Web Services. Both in the server side (WSDL2Java) and the client side (Flex Builder 3.0) we generate code using the WSDL. The problem arises when the server sends a 300Kb message to the client. Flex spends 10 seconds in deserializing this message. This is an unaceptable delay and a “rude awakenig”. The best choice should be use remote objetcs but we prefer in this moment not to migrate. Out best choice is to slightly modify certain SOAP messages in the WSDL to simplify the deserialization.
I need a good advice.
Thaks
Hi Nacho,
SOAP and XML should really never be used when you control both sides of the app. Use AMF instead via BlazeDS, LCDS, or one of the many other options out there. You can see a performance comparison of the various options at:
http://www.jamesward.com/census
AMF avoids unnecessary serialization / deserialization and from what you explained there really doesn’t seem to be any reason not to use it. It will make your life a lot easier.
-James
Hi David,u
Very good your post! But I really need to solve a huge problem in my project. I need to consume an Oracle Webservice. The problems are:
1- The webservice is SOAP 1.2: The wizard is not ready for it. Can I “code” the consume of the WS?
2- The WS has (login and pass) is it possible to call?
Thanks and Flex!
One Trackback
[...] Visit Tutorial [...]