This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 227083 - Local schema registration is broken for Java EE 7 schemas
Summary: Local schema registration is broken for Java EE 7 schemas
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: DD Editor (show other bugs)
Version: 7.3.1
Hardware: All All
: P3 normal (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-06 08:44 UTC by Petr Jiricka
Modified: 2015-09-17 13:09 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2013-03-06 08:44:09 UTC 
From an e-mail conversation between Reza Rahman and Svata Dedic:

---- REZA ----
I'm trying to use the Java EE 7 schemas that are not public yet
locally. I tried to define a NB schema locally, but NB still seems
to be struggling. Is there a trick I am missing?

I am trying the following schema:

<web-app version="3.1"
         xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_3_1.xsd">

---- SVATA ----
org.netbeans.modules.j2ee.dd.impl.web.WebParseUtils forces its DDResolver as EntityResolver for parsing. The DDResolver contains hardcoded systemIDs, but does not delegate to Lookup.getDefault().lookup(EntityResolver.class) to also process other registrations. JAXP will then attempt to retrive the schema resource from the specified schemaLocation (which fails).
Comment 1 Petr Jiricka 2013-04-10 10:30:30 UTC 
The schema mentioned in this bug is no longer valid, because it refers to the old java.sun.com domain - the correct latest version refers to jcp.org. 
The other thing is that web-app_3_1 schema is now registered by the IDE by default (no need to register a local version manually), so this issue does not apply to this particular schema.

David, do you know what would be another way to simulate this problem in the latest build? Is it still really a problem?
Comment 2 David Konecny 2013-04-10 21:35:21 UTC 
I think this issue has been resolved now. On the other hand WebParseUtils.DDResolver looks like it should be deleted and replaced with a resolver which is using global IDE catalogue. Like the one defined in org.netbeans.modules.j2ee.ddloaders.catalog.EnterpriseCatalog.
Comment 3 Martin Balin 2015-09-17 13:09:49 UTC 
Report from old NetBeans version. Due to code changes since it was reported likely not reproducible now. Feel free to reopen if happens in 8.0.2 or 8.1.