Created attachment 33038 [details]
screen shot of the problem

Created attachment 33039 [details]
schema file having problem

Note also there some UI issue like:
(a) Missing type information for “arrayOfString[1…1]”, expected

“arrayOfString[1…1] instanceof SOAP-ENC:arrayType" for the node.

(b) Note preview is showing type=””, expected type=”SOAP-ENC:arrayType”

see attached doc soapencoding_xsd_UI_problems.

Created attachment 33040 [details]
UI problems

Was the retriever used to reference this file locally or were you expecting this
to work from a remote location?

This should work from remote location. User should not be forced to make changes
to some existing xsd which imports an external xsd.

Use case is that someone sends me an xsd with import to a remote xsd. I just 
copy it to my bpel project and it should work. User should not have to worry 
about changing imports extra or using retriever unless he wants to.

Basically we should always support connected mode. 

I fixed this bug in the following way in the retriever module...

When ever resolver does not find an entry in the catalog for an absolute http(s)
URL, retriever API will be called automatically in a background thread and the
schema/wsdl referenced by that URL will be retrieved and cached locally. The
location of the cache is actually determined by the CacheDirectoryProvider of
the project. CacheDirectoryProvider.getCacheDirectory()+"/retriever" is the
cache folder. A separate catalog will also be created for this cached resources
@ CacheDirectoryProvider.getCacheDirectory()+"/retriever/catalog.xml". This
cache catalog file will actually be linked (by a relative path NOT absolute -
hence unique for a project and not system dependent) to the project wide catalog
by "nextCatalog" element of OASIS catalog. This way, cache catalog will also be
indirectly used for all the resolutions going forward. 

Since, the files are stored in the cache dir of the project, they are not
versionable and hence will not be checked in along with the project. Each
developer using this project will get his own copy of the retrieved files in his
cache folder.

This automatic retrieval will be called only for IDE use case. For all the unit
test cases, this logic is omitted intentionally. 

In the schema view, the visible change user would notice is, there will be a
noticiable delay/freez when the retriever actually fetches the files from
internet. This could be tested by opening up below schema and trying to add new
element that is based on the included external UBL schema (that has a closure of
19 other files). This is un-avoidable mostly. We are going to work with HIE to
have a better user experience (Jiri?)


<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            targetNamespace="urn:oasis:names:specification:ubl:schema:xsd:Order-1.0"
            xmlns:tns="http://xml.netbeans.org/schema/newXMLSchema"
            elementFormDefault="qualified">
<xsd:include
schemaLocation="http://docs.oasis-open.org/ubl/cd-UBL-1.0/xsd/maindoc/UBL-Order-1.0.xsd"/>
</xsd:schema>

Created attachment 39284 [details]
capture of fix verification

Fix VERIFIED build 070307_11 see screenshot.