Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319745

Summary: Filter mappings dialog enhancement for spec compliance
Product: [WebTools] WTP Java EE Tools Reporter: Carl Anderson <ccc>
Component: jst.j2eeAssignee: Carl Anderson <ccc>
Status: NEW --- QA Contact: Chuck Bridgham <cbridgha>
Severity: enhancement    
Priority: P3 CC: dimitar.giormov, kaloyan
Version: 3.0   
Target Milestone: Future   
Hardware: PC   
OS: Windows XP   
Whiteboard: JavaEE6

Description Carl Anderson CLA 2010-07-13 11:46:31 EDT 
One big change between the Servlet 2.4 specification and the Servlet 2.5 specification was the set up of the filter-mapping element.  Our UI has not kept up to date with those changes.  Additionally, in the Servlet 3.0 specification, a new DispatcherType of ASYNC was added.  That new type is not surfaced in our UI.

In Servlet 2.4, each filter mapping consists of:
A name
Either a URL pattern or a Servlet name
0 to 4 of the available DispatcherTypes

In Servlet 2.5, each filter mapping consists of:
A name
As many URL patterns and/or Servlet names as desired
0 to 4 of the available DispatcherTypes

In Servlet 3.0, each filter mapping consists of:
A name
As many URL patterns and/or Servlet names as desired
0 to 5 of the available DispatcherTypes (which now includes ASYNC)

Currently, this is all handled through AddEditFilterMappingDialog, which handles the Servlet 2.4 filter mappings exactly as it should.  We need to do something to handle Servlet 2.5 and Servlet 3.0 properly.