Copy link to clipboard
Copied
When I go into Connect to Data/Service, I select WSDL and paste in the WSDL URI which I got from Admin Console. And then it just sits there introspecting. I have tried using a crossdomain.xml file since the SQL server is on a separate domain but still get the same problem. I have tested the Web Service via SoapUI 3.6.1 and have written Servlets which access the data fine. But when trying via FB4, I am running into this problem.
Copy link to clipboard
Copied
I just noticed in SOAPUI that my ports are 1.1.
Copy link to clipboard
Copied
Changed the hosts file for 0.0.0.0 to point to the www.w3.org
and my system didnt like that, probably conflict with office
network settings or security settings. Had to remove it.
Copy link to clipboard
Copied
When it's introspecking the service does it close out after awhile of running or do you close it yourself. It's it's a issue with w3 then let it sit there for a few hours and see if it finishes on it's own.
Trying using TCPView to see what it's connecting to.
Copy link to clipboard
Copied
I have never let it keep going. I think the longest I have let it go is an hour. I am wondering if there is a way around this issue since apparently my company is using this address.
Copy link to clipboard
Copied
Yes, let it run for a few hours (mine closes out before one hour). Check out the following thread and bug
request.
Copy link to clipboard
Copied
Started Introspecting at 10:20....
Copy link to clipboard
Copied
Oh, thanks for the thread link. It shead some new light on that issue. Will try again.
Copy link to clipboard
Copied
Great, let me know if it works out for you.
Copy link to clipboard
Copied
Got called away for actual work. Made the changes to hosts and restarted introspecting at 11:35. Doesnt look like it solved my problem. Going to lunch and see if it completes when I get back.
Copy link to clipboard
Copied
one hour into it and its still Introspecting. I downloaded TCPView as suggested in the thread I was told about and I never saw any reference to www.W3.org so I am guessing its past that part.
Copy link to clipboard
Copied
Don't stop now, let it keep going.
Copy link to clipboard
Copied
2 hours and still at it
Copy link to clipboard
Copied
Wow, 2 hours and there it is. Interesting.
Copy link to clipboard
Copied
Wow, there is the data. So its working but 2 hours is really out there. Also, when I run the TestDrive app, it runs it as a file in the browser, why didnt it associate it as a web page like Servlets do? Do I create a servlet which adds this to it?
Copy link to clipboard
Copied
At first I tried the w3.org work around but it didnt fix it.
If you read the thread for the bug fix on FB-28592. Someone suggests to hibernate your computer and then immediately take it out of hibernation and it works. Well, I did that and sure enough, it worked. So at least there is a work around until this bug is fixed.
How do we know when the bug is fixed? Will you send us an email?
Copy link to clipboard
Copied
Found a better work around. Disable your Local Area Connection and then re-enable it and its much faster.
Copy link to clipboard
Copied
Pardon me for double-posting this but since this seems to be a common problem I wanted to share my solution:
The problem is that when running the introspection, repeated calls to www.w3.org are taking a lot of time, so it appears the progress dialog has "frozen" when it fact it is working, only very slowly. This can be circumvented by using Fiddler, the web debugging proxy, instead of disabling network interfaces or hibernating the computer. Fiddler has an autoresponder that can be used to respond instantly. Here's how you do it:
/TR/xhtml1/DTD/xhtml-special.ent
/TR/xhtml1/DTD/xhtml-symbol.ent
/TR/xhtml1/DTD/xhtml1-transitional.dtd
/TR/xhtml1/DTD/xhtml-lat1.ent
IMPORTANT 1: Do it in that order! "Unmatched..." first, "Enable..." second. Otherwise you might lose a few responses.
IMPORTANT 2: Do not check the box "Enable latency", because that's what we're trying to avoid here.
Hope this helps.
/Michael