When struts encounters a URI that matches multiple wildcard mappings it
chooses the most recent match (ie. "the last one wins" ).  As a result,  I
should define less-specific patterns before the more specific  patterns.
This is simple enough when using XML-based config, but I'm not sure how it
works with an annotation-based config. Does struts process these mappings
in a consistent/predictable manner?

For example, I have two @Action's defined in separate classes (both use
wildcard mappings).  When struts services a request it appears to match the
less-specific pattern *last*.  Can I influence the ordering of these
definitions?   Unfortunately choosing different url patterns is not an
option available to us.

Many thanks,
Jim deVos

Reply via email to