Incorporated feedback received on the expert's alias.

Author: spericas

spec/chapters/applications.tex

@@ -27,8 +27,8 @@ \section{\mvc\ Applications}
 The path in the application's URL space in which \mvc\ controllers live must
 be specified either using the \ApplicationPath\ annotation on the application
 subclass or in the web.xml as part of the \code{url-pattern} element. \mvc\
-applications MUST use a non-empty path or pattern: i.e., {\em "/"} or {\em "/*"} are 
-invalid in \mvc\ applications \assertref{application-path}. 
+applications SHOULD use a non-empty path or pattern: i.e., {\em "/"} or {\em "/*"} 
+should be avoided whenever possible. 
 
 The reason for this is that \mvc\ implementations
 often forward requests to the Servlet container, and the use of these

spec/chapters/assertions.tex

@@ -14,7 +14,6 @@ \chapter{Summary of Assertions}
 \code{ValidationResult} field or property is defined. 
 \assert{event-firing} All events in \code{javax.mvc.event} must be fired. See Javadoc for more
 information on each event in that package.
-\assert{application-path} The application's path must be non-empty.
 \assert{builtin-engines} Implementations must provide support for JSPs and Facelets.
 \assert{extension-engines} CDI beans that implement \code{javax.mvc.engine.ViewEngine} provide
 an extension mechanism for view engines.

spec/chapters/controllers.tex

@@ -9,7 +9,7 @@ \section{Controllers}
 
 An {\em MVC controller} is a \jaxrs\ \cite{jaxrs} resource method decorated by 
 an \Controller\ annotation \assertref{controller}. 
-If this annotation is applied to a class, then all methods in it are regarded as controllers
+If this annotation is applied to a class, then all resource methods in it are regarded as controllers
 \assertref{all-controllers}. 
 Using the \Controller\ annotation on a subset of methods defines a hybrid class in which 
 certain methods are controllers and others are traditional \jaxrs\ resource methods.
@@ -75,6 +75,9 @@ \section{Controllers}
 }
 \end{listing}
 
+The \View\ annotation only applies to a method that returns void and
+it is ignored in all the other cases.
+
 Note that, even though controller methods return types are restricted as 
 explained above, \mvc\ does not impose any restrictions on parameter
 types available to controller methods: i.e., all parameter types injectable

spec/chapters/intro.tex

@@ -13,7 +13,7 @@ \chapter{Introduction}
 the majority of the controller logic is provided by the framework instead of the application.
 
 The API defined by this specification falls into the action-based 
-category and is, therefore, not intended to be a replacement for component-based framworks such as
+category and is, therefore, not intended to be a replacement for component-based frameworks such as
 JavaServer Faces (JSF) \cite{jsf}, but simply a different approach to building Web applications on the 
 Java EE platform.
 
@@ -46,7 +46,7 @@ \section{Non-Goals}
 
 It is worth noting that, even though a standalone implementation of \mvc\ that runs outside
 of Java EE is a non-goal, this specification shall not intentionally prevent implementations
-to run in other environments, provided that those environments include support all the 
+to run in other environments, provided that those environments include support for all the 
 EE technologies required by \mvc.
 
 \section{Additional Information}
@@ -81,8 +81,8 @@ \section{Terminology}
 \label{terminology}
 
 Most of the terminology used in this specification is borrowed from other specifications 
-such as \jaxrs\ and CDI. We use the terms {\em per-request} and {\em request scoped} as
-well as {\em per-application} and {\em application scoped} interchangeably.
+such as \jaxrs\ and CDI. We use the terms {\em per-request} and {\em request-scoped} as
+well as {\em per-application} and {\em application-scoped} interchangeably.
 
 \section{Conventions}
 

spec/chapters/validation.tex

@@ -41,8 +41,8 @@ \section{Exception Mappers}
 An application can handle the exception by including an exception mapper as follows:
 
 \begin{listing}{1}
-class FormViolationMapper implements 
-                          ExceptionMapper<ConstraintViolationException> {
+public class FormViolationMapper 
+             implements ExceptionMapper<ConstraintViolationException> {
 
     @Inject
     private ErrorDataBean error;