search

chkal / mvc-spec-migration-test

0 stars 0 forks source link

Should a range of priorities for MVC-related provides be defined? #52

Open chkal opened 9 years ago

chkal commented 9 years ago

Original issue MVC_SPEC-56 created by Santiago Pericas-Geertsen:

MVC implementations may use JAX-RS providers such as filters and interceptors to implement the required semantics. These providers may "clash" with application-defined providers if not set to execute at the correct time (order). Perhaps MVC should defined a range of priorities for all implementations to use and avoid this potential problem.

chkal commented 9 years ago

Comment by Christian Kaltepoth:

+1 for this.

IMO it is very important that SPIs like ContainerResponseFilter have a well defined behavior in MVC environments. Especially it should be possible to implement ContainerResponseFilters that process both the raw result of the controller method invocation AND the Viewable created by the MVC implementation. This should be easy if we define a range of priorities.

chkal commented 8 years ago

Comment by gerhard_petracek:

+1 (at least based on @javax.annotation.Priority)

otherwise projects like apache deltaspike can't extend this spec. in a portable manner.

chkal commented 8 years ago

Comment by Santiago Pericas-Geertsen:

Understood, thanks for the feedback.