Jdeveloper hangs on wsil connection creation

In JDeveloper 11g if we try to create of test the WSIL connection with wrong detail of URL, username or password, JDeveloper hangs.

Make sure that to provide the correct details of URL, username and password while creating the WSIL connection

To verify the URL, access the same URL in a browser. Provide username and password when it prompts. If you see the response then the URL works fine.

You can see the result like this:

WSIL result when you browse

Note: The URL http://localhost:7001/inspection.wsil is a path that works for the Oracle
SOA Suite 11g environment

JDeveloper will not start and hungs

One of the best solution for this to get resolved..
When you have problem with JDeveloper like not starting or crashing
Delete JDeveloper's system directory from JDeveloper home directory

The default location for JDeveloper home directory will be:
 XP; C:\Documents and Settings\username\Application Data\JDeveloper\
 Windows 7: C:\Users\<username>\AppData\Roaming\JDeveloper\

 Under the JDeveloper home directory you can see a directory named as systemxx.x.x.xx...
Ex : system11.1.1.7.40.64.93 (for JDeveloper 11.1.1.7.0)

First close the JDeveloper and delete the system directory. then after start JDeveloper again, JDeveloper will recreate a new fresh one.
Note: All your JDeveloper settings will be lost on deleting the system directory !!!!

System directory contains the JDeveloper custom settings, if you delete this directory it wont impact your work folder (projects). 

Object scopes in Fusion page file cycle

At runtime, there are six types of scopes in a Fusion web application

• Application scope
• Session scope
• Page flow scope
• View scope
• Request scope
• Backing  bean scope

Application scope: The object is available for the duration of the application.

Session scope: The object is available for the duration of the session.

Page flow scope: The object is available for the duration of a bounded task flow.

Request scope: The object is available from the time an HTTP request is made until a response is sent back to the client.

Backing bean scope: Used for managed beans for page fragments and declarative components only, the object is available from the time an HTTP request is made until a response is sent back to the client. This scope is needed for fragments and declarative components because there may be more than one page fragment or declarative component on a page, and to prevent collisions, any values must be kept in separate scope instances. Therefore, any managed bean for a page fragment or declarative component must use backing bean scope.

View scope: The object is available until the view ID for the current view activity changes. This scope can be used to hold values for a given page. However, unlike request scope, which can be used to store a value needed from one page to the next, anything stored in view scope will be lost once the view ID changes.