The container first locates the filters with a matching URL in the order the filters are declared in the Deployment Descriptor. Next the container does the same with a matching servlet-name.
I feel 1 is correct. Because there is NO unavailable exception defined by filter's init method. ONLY servletException is defined.
3. Filters associated with a servlet are applied in the order in they appear in the DD.
This might change if there is a <url-pattern> which matches the servlet you requested.
Otherwise (a JavaBeans object), coerce value-b to String
f value-b is a readable property of value-a, as per the JavaBeans specification:
� If getter throws an exception: error
� Otherwise: return result of getter call
so my question still remains