Bug 150158

Required: 
support for importing and defining variables on xsd schema with no namespace defined

Details:
BPEL 2.0 defines that we can import xsd schemas that do not have a namespace defined. ie there can be an <import> tag
with no namespace attribute(it is optional). 
What this essentially means is that artifacts (elements, types) defined in the document, belongs to no namespace. 
no namespace, can be considered essentially has a sink where schema artifacts that don't belong to any qualified
namespace reside. 

Enhancement. 
1. bpel editor should allow the user to import an xsd document that does not have a namespace document. 
2. for such imports it will define an <import> tag with no namespace attribute.
3. when the editor imports such a schema document it should explicitly qualify all qualified artifacts in the bpel
document with a valid qualified name. (ex: bpel artifacts should be explicitly qualified by the bpel namespace). 
4. the <process> tag should not have any default namespace (ex xmlns="...") definition. 

Attachment: 
attached is a project zip of an example of a bpel process that imports such a no namespace xsd document and defines a
variable on an type defined in this document. It highlights all the points that are described above.