Thinking to light the fireplace tonight ?

Check this first:

Comments

Post a Comment

Popular posts from this blog

Changing the version of JDK used by JDeveloper

I have recently learned a quick and lazy way to change the version of the JDK used to run JDeveloper 10g R3. I am sure there is an option somewhere in the configuration screen to do the same, which I couldn't find... While JDeveloper is not running, locate the embedded JDK on disk and rename (or delete) that directory. For me, it was C:\opt\jdev\jdk. Once it's done, restart and you will by asked to locate the version of the JDK you want to use. It's another step to get going with JAVA on Vista. -ecco
Read more

Connection reset from a WCF Web Service

Here is an error message you may see, when calling WCF Web Services from java: IOException retrieving the response: java.net.SocketException: Connection reset As it may not be obvious the first time you see it, this may save you some time. One reason for this behaviour is when the WCF endpint is expecting to see wsa:Action SOAP header in the request. To find out if you are facing this case, you have to look inside the WSDL, and search for the policy that describes the contract for your endpoint. <wsp:Policy wsu:Id="CustomBinding_Echo1_policy">   <wsp:ExactlyOne>     <wsp:All>       <wsaw:UsingAddressing/>     </wsp:All>   </wsp:ExactlyOne> </wsp:Policy> To make this a concrete example, here is a sample WSDL . To find the policy, you will need to follow the import as the policy are not always advertized in the top-level document. Here is how the import looks:   <ws...
Read more

java.net.ConnectException: Connection refused

Image
As I am still getting question related to this error, when using JDeveloper, I'll describe my troubleshooting tips here, so that it can be indexed by Google (and other search engines). If you can access the web resource from IE or Mozilla, but can't get the WSDL to work with JDeveloper, you are most likely facing a common issue. Your HTTP proxy setup may be incorrect. Here is the screenshoot of the configuration from JDeveloper 10.1.3.1. Last time I used JDeveloper, I was using the HTTP Analyzer feature and I forgot to turn it off before to exit the application. When I re-started JDeveloper the next day, the proxy was still setup for port 8099. Here is a sample of the output you may get when you face this configuration error: Buildfile: /Users/eric/devroot/build.xml analyze: Failed to read wsdl file at: "http://www.rajkovic.org/ws/wsdl/bads/annotatedBank.wsdl", caused by: java.net.ConnectException. : Connection refused Remember to stop HTTP Analyzer before to ex...
Read more