Bug 190087

Environment
===========

OS:         Fedora Linux 2.6.34.6-47.fc13.i686
JDK:        1.6.0_21 (32 bit)
NetBeans:   6.8, 6.9.1
Subversion: 1.6.9

Project
=======

Plugin:     Portal Pack 3.0.4
Maven:      2.2.1 (locally installed)
Archetype:  jetspeed 2.2.1

Use Case
========

Jetspeed contains a number of Jetspeed - specific XML files along with
their corresponding XSD Schema files. These XML files are complex, and
it would be advantageous to leverage NetBeans XML completion and
validation tools.

1. Make use of locally installed XSD Schema
2. Code completion for complex XML files based on XSD Schema
3. Validation for complex XML files based on XSD Schema

Scenario 1
===========
Attempt to register a locally available XSD catalog in a shared area:

Steps
-----
1. Place XSD Schema in a public place on the platform:
   (/usr/share/sgml/jetspeed-2)
2. Add the schemas to the User catalog via the following:
   a. Tools->DTDs and Schemas->User catalog [read-write]
   b. Select Add Local DTD or Schema
   c. Use System ID of http://portals.apache.org/jetspeed
   d. Browse to /usr/share/sgml/jetspeed-2/jetspeed-portlet.xsd
   e. Add to catalog (shows up as a new entry)
3. Attempt to create a new XML file
   a. File->New->XML Document
   b. Location [project-artifact]/WEB-INF/jetspeed-portlet.xml
   c. Document type XML Schema-Constrained Document
   d. Browse by Namespace

Expected
--------
1. Namespace to be present as http://portals.apache.org/jetspeed
2. XSD jetspeed-portlet.xsd to be available

Actual
------
1. No namespaces available for import

Scenario 1a
===========

Modifications
-------------
2.
   c. Use System ID of
      file:/usr/share/sgml/jetspeed-2/jetspeed-portlet.xsd

Actual
------
1. No namespaces available for import


Scenario 2
==========
Add XSD schema to project outside of the source tree area and access
them via Filename (modification of Scenario 1, Step 3.d.)

Steps
-----
1. Put XSD schemas into project tree outside of the source
   a. Make a directory [project-artifact]/xsd
   b. Copy necessary schemas to directory
2. Attempt to create a new XML file
   a. File->New->XML Document
   b. Location [project-artifact]/WEB-INF/jetspeed-portlet.xml
   c. Document type XML Schema-Constrained Document
   d. Browse by Filename

Expected
--------
1. XSD Schema to be present by file name

Actual
------
1. New directory did not show up
2. No XSD schemas available for document

Scenario 2a
===========

Modifications
-------------

2. Attempt to create a new XML file
   d. Browse by Namespace

Expected
--------
1. No namespaces available for import

Actual
------
1. Namespaces available for import (!)

File Creation
-------------
1. Complete pathname of XSD schema in XML file
   a. This will obviously break configuration management
2. Change to remote URL for namespace
   a. Fixes configuration management
   b. Access network for validation (potential validation failure)

Scenario 2b
===========

Modifications

1. Put the XSD schema inside the project tree inside the source
   a. Make the directory [artifact-id]/src/main/xsd
   b. Copy XSD schemas to this directory
2. Attempt to create a new XML file
   a. File->New->XML Document
   b. Location [project-artifact]/WEB-INF/jetspeed-portlet.xml
   c. Document type XML Schema-Constrained Document
   d. Browse by Filename / Namespace

Expected
--------

1. Filename browsing to work
2. Namespace browsing to fail
3. File reference in XML document to be relative

Actual
------

1. Filename browsing works
2. Namespace browsing works (!)
3. File reference in XML document is absolute (!)
   a. this will still be unacceptable for configuration management

Summary of Issues
=================

1. File based XSD schema outside of project directory fails to work
2. File based XSD schema inside project directory uses absolute paths
3. Addition of XSD schema based on a local web server doesn't seem to
   be possible

As an aside, I noticed that some of the XSD schemas referenced by
NetBeans points to nbres:[path], which translates to:

~/.netbeans/[version]/modules/[path-in-jar]

How could this be leveraged to solve this problem?