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 149879 - valid input is rejected in web.xml (design) editor
Summary: valid input is rejected in web.xml (design) editor
Status: RESOLVED DUPLICATE of bug 163396
Alias: None
Product: javaee
Classification: Unclassified
Component: DD Editor (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on: 152452
Blocks:
  Show dependency tree
 
Reported: 2008-10-12 02:12 UTC by phygons
Modified: 2009-09-18 05:41 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 phygons 2008-10-12 02:12:06 UTC 
Multiple <url-pattern> inside <filter-mapping>, which is okay per Servlet 2.5 schema, is not allowed by the editor in
NetBeans 6.5 Beta.
It looks fine in NetBeans 6.0.1 (I haven't tested this in NetBeans 6.1).

For example,
    <filter-mapping>
        <filter-name>LoginFilter</filter-name>
        <url-pattern>/admin/*</url-pattern>
        <url-pattern>/admin2/*</url-pattern>
        <dispatcher>FORWARD</dispatcher>
        <dispatcher>REQUEST</dispatcher>
        <dispatcher>INCLUDE</dispatcher>
    </filter-mapping>
will cause error when trying to open any GUI editor for web.xml.
Comment 1 Petr Hejl 2008-10-12 18:40:05 UTC 
The issue seems to be valid as far as I can tell. Look like improperly (?) created bean mapping. I didn't functionality
in 6.1.
Comment 2 Petr Hejl 2008-10-12 18:44:41 UTC 
XML schema is not org.netbeans.modules.j2ee.dd.api.web aligned with the allowed one:

<!-- TODO: fix this in DD API
   <xsd:choice minOccurs="1" maxOccurs="unbounded">
-->

Workaround is splitting the filter mapping to multiple elements.
Comment 3 Erno Mononen 2008-10-14 12:52:09 UTC 
The root cause is issue 76060. Unfortunately I'm not sure whether this can be fixed for 6.5, I will investigate. Please 
use the mentioned workaround for now.
Comment 4 Erno Mononen 2008-10-15 12:50:25 UTC 
The issue is valid, but the fix for this would require changes in several areas and it would therefore be rather risky 
to fix this for 6.5 at this point. I think this is not a show stopper for 6.5, so setting TM => 7.0.
Comment 5 Trey Spiva 2008-12-01 16:16:38 UTC 
I am lowering the priority because there is a work around.
Comment 6 Petr Jiricka 2009-09-17 21:37:24 UTC 
Hi Denis, is this a duplicate of issue 163396? Thanks.
Comment 7 Denis Anisimov 2009-09-18 05:41:14 UTC 
That's right.
It is duplicate.

*** This issue has been marked as a duplicate of 163396 ***