Thank you everyone for sticking with me on this. As you can tell
I'm not much of a web services person and the vendor that created it
isn't around but will be coming back to the office in the next few
weeks so I'm trying to fully understand what is going on here.
Since it seems the changes
If you can do it without revealing any business secrets, build a soapUI
project based on your web service, and a 20 line application that calls it
and replicates your problem, then I'll probably be able to have a quick look
at over the weekend.
-Josh
On Thu, Jun 19, 2008 at 10:05 PM, Mark [EMAIL
Mark,
Do you have a service/support contract with Adobe? It is difficult to tell
you exactly what buttons to push - as you say. With the tech articles that
we've sent so far. and your knowledge of the system - this is really the
first and best path to find a solution. My second recommendation
So I downloaded Charles 3.2.1 to see what I'm getting. Running the
code from 2.0.1 all is fine. But with 3.0 here's what I'm getting.
soap:Envelope
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Looks to me like there's a problem with your namespaces in the bad request.
I don't know much about soap headers, but where's that radarXML namespace
coming from?
The SOAP code in Flex 3 is stricter than Flex 2's, so besides a couple of
bugs it behaves better than Flex 2's SOAP code, but often
RadarXML is the WebService
Response Code = 500 Internal Server Error
SOAP/faultcode = soap:Server
SOAP/faultstring = Server was unable to process request. --gt;
Object reference not set to an instance of an object.
You may be right, it could be a server or webservice issues.
-M
--- In
Mark -
If you have useProxy = true . then you would be using Flash Proxy/BlazeDS.
Just flipping the bit isn't going to do anything for you. As per your
example. What you see is the effect of the changes in the RPC bits in the
frameworks (2.0.1 vs. 3.0). So. again - what you see is what I would
Josh - remember that one of the big issues with SOAP is that Flex doesn't
understand anything beyond a 200 response.
Rick Winscot
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Josh McDonald
Sent: Wednesday, June 18, 2008 10:19 AM
To: flexcoders@yahoogroups.com
Hence me plugging Charles like I wrote the thing :)
On Thu, Jun 19, 2008 at 8:03 AM, Rick Winscot [EMAIL PROTECTED]
wrote:
Josh – remember that one of the big issues with SOAP is that Flex doesn't
understand anything beyond a 200 response.
Rick Winscot
*From:*
ROWR! I LVE Charles.
Rick Winscot
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Josh McDonald
Sent: Wednesday, June 18, 2008 8:41 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: My Web Service with soap headers code no
longer work with Flex 3
HI,
I guess what I'm not understanding is the fact that when I run this
code from Flex Builder 2 it works, but when I run it out of FB 3 it
doesn't. The Flash Player version would make sence to me but not
working in one and not the other. I'm using 9.0.124.0 Debug.
HERE'S MY ERROR IN FB3:
What are you seeing over http? I mean with Charles or something similar?
On Tue, Jun 17, 2008 at 11:34 PM, Mark [EMAIL PROTECTED] wrote:
HI,
I guess what I'm not understanding is the fact that when I run this
code from Flex Builder 2 it works, but when I run it out of FB 3 it
doesn't. The
I don't have Charles or anything like that so I can't see. I work
for a company that doensn't really allow that kind of thing without
a fight first. :(
--- In flexcoders@yahoogroups.com, Josh McDonald [EMAIL PROTECTED]
wrote:
What are you seeing over http? I mean with Charles or
I work for the same kind of company - It is a real headache to get any
kind of new software.
I finally had to bite the bullet and pay for Charles personally. This
piece of software is just too useful to do without.
--- In flexcoders@yahoogroups.com, Mark [EMAIL PROTECTED] wrote:
I don't have
Is there perhaps some confusion between a web proxy used for local
development versus as network packet sniffer?
Think of it logically. What is the impact of you writing 30 lines of
Java code to listen on a localhost'd server socket for your own
development activity and write the bytes
You can set up a TraceTarget and tell it to listen to mx.rpc.* and
mx.messaging.* and you'll get some of that information, but it's nowhere
near as good as using Charles, as you won't get to see anything that the
flash player doesn't get to see (redirects, 500 responses, etc).
See here:
Tracy - actually, you are right on the money. The Authorization header was
blocked and then re-instated in 9.0.124. You can still work around the issue
if you compile in Flex 2.0.1 since the RPC bits are still intact there.
however - in 3.0 they have changed.
From the 3.0.x Flex SDK -
Josh, I think you are right, the OP was not adding headers to the HTTP request
after all, and his header was not Authorization, which as you point out, is
again allowed.
Probably best to ignore me on this one!
Tracy
From: flexcoders@yahoogroups.com
Any ideas on this? I'm having a real hard time here.
Mark
--- In flexcoders@yahoogroups.com, Mark [EMAIL PROTECTED]
wrote:
In Flex 2 this works like a charm but not in 3, I can't seem to
find
any info on the changes in the Help. Can someone lend a hand?
?xml version=1.0
I don't know much about funky soap headers, but what kind of error are you
getting? Or is it just dropping the headers?
On Thu, Jun 12, 2008 at 11:02 PM, Mark [EMAIL PROTECTED] wrote:
Any ideas on this? I'm having a real hard time here.
Mark
--- In flexcoders@yahoogroups.com
There were some security changes in the Flash Player that can affect
webservice access.
Search for my post: FYI: WebService, FP version 9.0.124.0, Security
error accessing URL crossdomain.xml fix
Tracy
From: flexcoders@yahoogroups.com [mailto:[EMAIL
I see that your header is an authorization header. That is not good news for
you, and your problem cannot be fixed by the crossdomain file.
You can no longer set Authorization headers. Below is copied from an earlier
post to flexcoders. I think you will find more info if yo search.
I was under the impression Auth headers were allowed again?
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403030sliceId=1
But, being a SOAP header I think it's part of the POST request and the flash
HTTP header blocking stuff wouldn't apply anyway?
-Josh
On Fri, Jun 13, 2008 at
23 matches
Mail list logo
